Blueprint · careervector.blueprint-graph/v7

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, assistant actions, link/provider authority, limits, offline state, failure, and recovery stay legible across web, TUI, API, and MCP.

  • Origin and activity to Assistant actions + limits: why this happened
  • Assistant actions + limits to Offline and recovery: undo, reauthorize, or retry
why this happenedundo, reauthorize, or retry
perspectivemixed

Origin and activity

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

CareerVector UI/TUI/API/MCP
perspectivetarget

Assistant actions + limits

Intent, tool effect, undo, link scope, provider authorization, plan limits, consent, and cancellation.

CareerVector UI/TUI/API/MCP
processmixed

Offline and recovery

Event replay, realtime convergence, connector reconnect, client update/rollback, and honest failure.

CareerVector runtime
assistant activity and recoveryassistant activity becomes explanationexperience closes accountability
  1. 01 · perspective · mixed Origin and activity

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

    CareerVector UI/TUI/API/MCP
  2. 02 · perspective · target Assistant actions + limits

    Intent, tool effect, undo, link scope, provider authorization, plan limits, consent, and cancellation.

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

    Event replay, realtime convergence, connector reconnect, client update/rollback, and honest failure.

    CareerVector runtime

Flows

  • Origin and activity → Assistant actions + limits why this happened
  • Assistant actions + limits → Offline and recovery undo, reauthorize, or retry

Canonical architecture note

Open note ↗

CareerVector Experience

Generation boundary

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.

Purpose

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.

Owns

  • Workspace, radar, CV/CL, job, evaluation, application, and collaboration interactions.
  • The browser market matrix/radar/collaboration journey and the TUI's railroaded General → CV → Cover Letter → Review → Export journey.
  • The Tauri network-loaded workspace plus native fetch/render, adapter, update, and OS seams.
  • Link-based workspace access and separate device/provider authorization without conflating their authorities.
  • A persistent, collapsible, resizable right chat rail beside the active desktop workspace; on a narrow screen, a full-screen conversation that does not crush the editor.
  • Human UI, assistant tools, API, and MCP perspectives over the same canonical workspace state.
  • Native managed connectors, deterministic Typst measurement/rendering, Tauri adapter execution, and local device state that do not fork canonical career/application truth.
  • Scraping participation as a truthful, consent-based control.
  • Assistant context, streaming, cancellation, reconnect, tool activity, provenance, undo, limits, re-authorization, failure, and recovery.
  • Visual language for origin, activity, uncertainty, freshness, failure, and recovery.

Does not own

  • Canonical public role/ad evidence.
  • Scraper scheduling, connector process supervision, or tool execution authority.
  • ChatGPT plan policy, legal interpretation, or operator authority.

Current state

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.

Agent contract

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.

Completion evidence

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.

Child contract

Source: architecture/modules/careervector-experience.md