Origin and activity
Human, system, agent, provider, client, freshness, and work-state signals.
CareerVector UI/TUI/API/MCPBlueprint · careervector.blueprint-graph/v7
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, assistant actions, link/provider authority, limits, offline state, failure, and recovery stay legible across web, TUI, API, and MCP.
Human, system, agent, provider, client, freshness, and work-state signals.
CareerVector UI/TUI/API/MCPIntent, tool effect, undo, link scope, provider authorization, plan limits, consent, and cancellation.
CareerVector UI/TUI/API/MCPEvent replay, realtime convergence, connector reconnect, client update/rollback, and honest failure.
CareerVector runtimeHuman, system, agent, provider, client, freshness, and work-state signals.
CareerVector UI/TUI/API/MCPIntent, tool effect, undo, link scope, provider authorization, plan limits, consent, and cancellation.
CareerVector UI/TUI/API/MCPEvent replay, realtime convergence, connector reconnect, client update/rollback, and honest failure.
CareerVector runtimeCanonical architecture note
Open note ↗V4 retains the link-access collaborative workspace and has three first-party client trees. The browser is the complete collaborative product; the imported Rust TUI is the focused terminal workflow; the Tauri app is the desktop shell around the browser UI plus native adapter and OS capabilities. The TUI's current local adapter is transitional.
Explain the complete interaction model and visual language of CareerVector. The experience spans link entry, broad web product work, focused TUI application work, persistent assistant conversation, typed actions, optional public contribution, support, and system state; it cannot be represented by the central product square alone.
The collaborative browser workspace, link access, and Linux Tauri shell are as built. The imported TUI's application workflow, local adapter, managed connector surface, bounded revision-safe edits, and native renderer/ruler are as built. Canonical TUI workspace attachment, shared vendor chat across clients, typed-action cards, reconnect, and shared undo remain target/open.
User-visible web changes require browser evidence; TUI changes require controlled terminal and render evidence. Chat follows the active route and selection as context, never as authorization. A collapsed surface does not stop a running turn; explicit cancellation does. Shared contracts are extracted only where behavior and semantics are truly shared; web, TUI, JobCache, and CareerVector are not skins over one product.
Complete responsive web and controlled-terminal journeys; accessible keyboard and screen-reader chat; desktop resize/collapse persistence; the narrow full-screen projection; TUI workflow and document rendering; stream resume and cancellation; tool preview/receipt/undo; link-scope denial; provider authorization expiry and recovery; browser/TUI/Tauri state convergence; offline/collaboration behavior; visual snapshots; consent/withdrawal; and error recovery.