Blueprint · careervector.blueprint-graph/v5

Graph explorer

Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.

Cell 5.3 · product · operations · evidence · privacy

Explain, collaborate, and recover

Origin, uncertainty, route choice, offline state, failure, fallback, and recovery stay legible across web, desktop, API, and MCP.

  • Origin and activity to Smart Routing explanation: why this happened
  • Smart Routing explanation to Offline and recovery: override or retry
why this happenedoverride or retry
perspectivemixed

Origin and activity

Human, system, agent, provider, freshness, and work-state signals.

CareerVector UI/API/MCP
perspectivetarget

Smart Routing explanation

Short reason, fallback, exhaustion, consent, and explicit override.

CareerVector UI/API/MCP
processmixed

Offline and recovery

Local queue, realtime convergence, server fallback, and honest failure.

CareerVector runtime
status and recoveryactivity becomes explanationexperience proves promise
  1. 01 · perspective · mixed Origin and activity

    Human, system, agent, provider, freshness, and work-state signals.

    CareerVector UI/API/MCP
  2. 02 · perspective · target Smart Routing explanation

    Short reason, fallback, exhaustion, consent, and explicit override.

    CareerVector UI/API/MCP
  3. 03 · process · mixed Offline and recovery

    Local queue, realtime convergence, server fallback, and honest failure.

    CareerVector runtime

Flows

  • Origin and activity Smart Routing explanation why this happened
  • Smart Routing explanation Offline and recovery override or retry

Canonical architecture note

Open note ↗

CareerVector Experience

Purpose

Explain the complete interaction model and visual language of CareerVector. The experience spans private product work, optional public contribution, AI execution, support, and system state; it cannot be represented by the central product square alone.

Owns

  • Workspace, radar, CV/CL, job, evaluation, application, and collaboration interactions.
  • Consistent behavior across browser and Tauri desktop delivery.
  • Human UI, API, and MCP perspectives over the same canonical workspace state.
  • Scraping and Local AI pills as truthful, consent-based participation controls.
  • “Smart Routing AI” explanations, explicit overrides, BYOK, and local/included availability.
  • Visual language for origin, activity, uncertainty, freshness, failure, and recovery.

Does not own

  • Canonical public role/ad evidence.
  • Scraper scheduling or routing mathematics.
  • Provider policy, legal interpretation, or operator authority.

Current state

The shared application shell, collaborative workspace, web and desktop participant bridge, Scraping pill, adaptive AI routing foundation, and explanation surfaces exist at different levels of completeness. The Local AI adoption experience and several product workflows remain target work.

Agent contract

User-visible changes require browser evidence. Shared UI is extracted only where behavior and semantics are truly shared; JobCache and CareerVector are not skins over one product.

Completion evidence

Complete responsive journeys in web and desktop; accessibility; offline and collaboration behavior; visual snapshots; route explanations; consent and withdrawal; and error recovery.

Source: architecture/modules/careervector-experience.md