AI Job Hunter — interactive architecture map · local-first Tauri 2 monorepo

critical path

external / API call

DB read/write

mount / register

fix count bug count

AI Job Hunter — architecture

Local-first Tauri 2 desktop app. The renderer talks to a Rust core only through typed IPC contracts (ports & adapters). Heavy work — scraping, document extraction, AI generation, embeddings — runs natively in-process.

Click any box for its plain-English role, real file path, and what wires into and out of it. Use the chips up top to highlight a feature or a user-flow path. Drag to pan, scroll to zoom.

Notable findings from this map

Code↔doc mismatch: the resume-job matcher is a Rust stub, though it was ✅ in the old TypeScript and the status doc still lists features as done (ARCHITECTURE_STATUS.md:47-50). Flagged red on cmd-match.
Heaviest hot path: AI generation fans through packages/prompts (resume/cover builders + context-manager truncation + ProviderProfile + validators) before a single token streams — the red spine.
Strong seam: a single-owner platform band (platform::config, net::http, error::AppError, observability::Span) plus two registries — SCRAPERS (24), ProviderId (8). Adding a board/provider is one module + one line; CI arch tests enforce ownership.
No silent fallback: ai_provider::resolve() routes strictly by ProviderId — an unknown/mismatched provider is a hard error, never a quiet switch to Ollama.
God nodes (edges intentionally not all drawn): cn() ~191, useAppClient() ~167, Button ~97. They touch nearly everything in their layer.
tauri-client is a folder module (apps/desktop/src/tauri-client/index.ts); CLAUDE.md still cites the old single-file path.

Counts

142 nodes · 128 edges · 11 clusters · 24 boards · 8 AI providers

Critical paths

Red = AI Generate (default). Click Autopilot or Scrape → Match to light up the other two flows.