CareerVector × AI

Outcome

Bring a SOTA vendor chatbot into the active CareerVector workflow without building a CareerVector account system, exporting workspace authority, or creating a second mutation path.

Three hosts, one seam

• The browser can present a persistent rail or narrow-screen conversation over the active route.
• The terminal TUI already hosts managed provider connectors beside its guided application flow.
• The Tauri desktop app projects the browser workspace and can add the same controlled native connector boundary where useful.

These are client hosts, not separate AI products. Each resolves the private workspace link and active route/job/document/selection locally, then gives the connector only the bounded context and typed tools required for the turn.

No CareerVector accounts

CareerVector has no registration, login, membership, ownership, account ID, or account recovery. The private workspace link is the workspace capability. Provider login belongs to the vendor and can be authorized, expire, or be revoked independently. Workspace IDs, provider thread IDs, operation IDs, and client/session IDs are explicit scopes; none implies a CareerVector account.

Tool and result contract

• bounded active-context read;
• evidence-backed public JobCache query;
• allowlisted, revision-checked CareerVector operation;
• idempotency, affected paths, clocks, provenance, and visible receipt;
• compensating undo that refuses to overwrite later work;
• streaming, cancellation, reconnect, conflict, limit, and authorization states.

Committed effects return through the canonical D1/Yjs operation and realtime paths. Chat cards and the affected workspace surface show the same result.

Privacy and authority invariants

• The model never sees the private workspace link or receives ambient workspace enumeration.
• Provider credentials remain in the selected connector host.
• Context is not authority; the trusted host injects scope server-side.
• Direct UI, API, MCP, browser chat, terminal chat, and desktop chat use the same mutation rules.
• Management receives content-free service/release evidence, not prompts, documents, or threads.

Current state and completion evidence

The TUI connector and bounded local field tools are as built; the browser rail, Tauri host choice, canonical workspace adapter, shared durable transcripts, and complete typed tools are target. Acceptance requires the same link-opened workspace in all three clients, independent provider authorization, cross-client result convergence, stale-write denial, idempotent retry, cancellation, reconnect, undo, credential isolation, and proof that no CareerVector account was introduced.