Blueprint · product band

Scraping participation controls

Public-corpus contribution is explicit and truthful: readiness, consent, background limits, and withdrawal stay visible.

Cell 5.1 · product · privacy · runtime
  • Scraping participation to Consent + readiness: open explanation
  • Consent + readiness to Truthful device state: observe capability
open explanationobserve capability
perspectivemixed

Scraping participation

Persistent contribution state in the product band.

CareerVector UI
policytarget

Consent + readiness

Explain public-corpus purpose, browser capability, foreground/background behavior, and withdrawal.

Workspace participant
processtarget

Truthful device state

Disabled, ready, active, limited, failed, or unavailable.

CareerVector device
participation statecapability supports work
  1. 01 · perspective · mixed Scraping participation

    Persistent contribution state in the product band.

    CareerVector UI
  2. 02 · policy · target Consent + readiness

    Explain public-corpus purpose, browser capability, foreground/background behavior, and withdrawal.

    Workspace participant
  3. 03 · process · target Truthful device state

    Disabled, ready, active, limited, failed, or unavailable.

    CareerVector device

Flows

  • Scraping participation → Consent + readiness open explanation
  • Consent + readiness → Truthful device state observe capability
as built target / open Boundary arrows open the neighbouring module; ports stay machine-only

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