Origin and activity
Human, system, agent, provider, freshness, and work-state signals.
CareerVector UI/API/MCPBlueprint · careervector.blueprint-graph/v5
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
Origin, uncertainty, route choice, offline state, failure, fallback, and recovery stay legible across web, desktop, API, and MCP.
Human, system, agent, provider, freshness, and work-state signals.
CareerVector UI/API/MCPShort reason, fallback, exhaustion, consent, and explicit override.
CareerVector UI/API/MCPLocal queue, realtime convergence, server fallback, and honest failure.
CareerVector runtimeHuman, system, agent, provider, freshness, and work-state signals.
CareerVector UI/API/MCPShort reason, fallback, exhaustion, consent, and explicit override.
CareerVector UI/API/MCPLocal queue, realtime convergence, server fallback, and honest failure.
CareerVector runtimeCanonical architecture note
Open note ↗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.
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.
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.
Complete responsive journeys in web and desktop; accessibility; offline and collaboration behavior; visual snapshots; route explanations; consent and withdrawal; and error recovery.