Architecture Diagram A

AI Job Radar - End-to-End Flow

BPMN-style process lanes for mobile-safe readability: secure ingress, deterministic discovery, segmented HITL tailoring, quality gates, integrity checks, and outcome feedback.

Process Flow (BPMN-style Lanes)

Same flow on all devices, no overlapping nodes, and clear handoff points between lanes.

Lane 1: Ingress + Discovery

ScannerAgent

  1. Command Ingress

    Telegram or CLI command enters the system.

  2. Security Gate

    Allowlist and rate-limit checks; policy routes non-command noise.

  3. Discovery Scan

    Adapters fetch openings, dedupe, score, and apply ghost-risk downgrade.

  4. State Persist

    `RadarJob`, `RadarTriage`, `ScanReport`, and outcomes stored in SQLite.

handoff -> Router lane

Lane 2: Routing + Tailor

Tracker/Tailor

  1. Command Router

    Deterministically routes `/probe`, `/track`, `/tailor`.

  2. /probe + /track

    Derive URLs and idempotently promote a radar item to tracked job state.

  3. Tailor Step 1 (HITL)

    Generate value hypotheses preview and wait for user edit/approval.

  4. Tailor Step 2

    On approval, generate resume and cover letter artifacts.

handoff -> Guardrails lane

Lane 3: Guardrails + Outputs

Debugger/Notifier

  1. Content Firewall

    Treat JD as untrusted input: sanitize, extract schema, ignore embedded instructions.

  2. Quality Gate

    Deterministic checks + rewrite loop with fail-closed behavior.

  3. Output Integrity

    Temp write -> atomic move with manifest checksums.

  4. Ops + Feedback

    `/status` for observability and `/outcome` labels for local learning loop.

Result: no horizontal overflow dependency, stable readability on mobile, and explicit phase transitions.

How This Diagram Is Produced

This architecture page is assembled directly in code. The lanes, nodes, spacing, and responsive behavior are defined in HTML and CSS so the structure stays versioned, reviewable, and easy to refine without a separate export step.

  1. Each lane is authored as semantic HTML sections with ordered step lists.

  2. CSS grid controls desktop/mobile layout, spacing, and readable handoff flow.

  3. Labels and glossary text are updated in-source so changes stay diffable in git.

  4. The page ships as static HTML, then publishes through GitHub Pages behind Cloudflare.

Node Glossary

Plain-language meaning of each node in the flow.

BPMN-style Process Lanes

A diagram layout that separates responsibilities into clear lanes so handoffs, ownership, and checkpoints stay readable on desktop and mobile.

Security Gate

Validates chat IDs, applies rate limits, and routes non-command noise by policy.

Discovery Scan

Collects openings from ATS/APIs/pages, then deduplicates and triages them.

Command Router

Deterministically executes `/probe`, `/track`, and `/tailor` workflows.

SQLite State

Stores jobs, triage, scans, outcomes, and task observability records.

Tailor Step 1 (HITL)

Shows hypotheses preview for human review before any full artifact generation.

Content Firewall

Sanitizes JD content and extracts structured signals from untrusted source text.

Quality Gate

Applies deterministic writing constraints and rewrites when policy fails.

Output Integrity

Publishes artifact files atomically and tracks checksums in manifest metadata.

Ops + Feedback

Provides runtime status and outcome labels for iterative local improvement.

© Hubsays Studio · hubsays.com