Client execution placement
Device-local TUI execution is selected; the web execution bridge remains an explicit product decision.
Product ownerBlueprint · 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.
Nested layer 1 · runtime · control · privacy · evidence
CareerVector assistant connector runtime
The TUI has an as-built managed device-local connector host; web placement remains open behind the same provider, event, tool, isolation, and recovery contracts.
- Client execution placement to Managed runtime store: select host boundary
- Managed runtime store to App Server · ACP: install + launch
- App Server · ACP to Provider authorization: provider lifecycle
- Provider authorization to Workspace-scoped thread: start or resume
- Workspace-scoped thread to Connector event stream: turn stream
- Workspace-scoped thread to Scoped tool transport: typed intent
- Scoped tool transport to Connector event stream: tool result
- Connector event stream to Supervision + rollback: terminal state
- Supervision + rollback to App Server · ACP: interrupt, rollback, restart, or stop
Managed runtime store
Pinned provider artifacts install into private application data, activate atomically, and retain rollback.
CareerVector TUIApp Server · ACP
Codex JSONL and native ACP connectors initialize, report capability, stream, and cancel through reviewed adapters.
CareerVector TUIProvider authorization
In-product login and provider-owned credentials remain device-local and separate from workspace access.
Provider connectorWorkspace-scoped thread
Target durable mapping and transcript resume across link-holding browser, TUI, and Tauri clients.
CareerVector D1 + connectorConnector event stream
Messages, progress, cancellation, limits, errors, and terminal state are normalized at the client boundary.
CareerVector TUIScoped tool transport
Only the approved CareerVector tool boundary receives injected workspace/connector/thread scope.
CareerVector tool serviceSupervision + rollback
Cancel, crash, reconnect, protocol mismatch, install failure, and credential revocation fail explicitly.
CareerVector TUI01 · boundary · open Client execution placement Device-local TUI execution is selected; the web execution bridge remains an explicit product decision.
Product owner02 · boundary · as-built Managed runtime store Pinned provider artifacts install into private application data, activate atomically, and retain rollback.
CareerVector TUI03 · service · as-built App Server · ACP Codex JSONL and native ACP connectors initialize, report capability, stream, and cancel through reviewed adapters.
CareerVector TUI04 · process · as-built Provider authorization In-product login and provider-owned credentials remain device-local and separate from workspace access.
Provider connector05 · store · target Workspace-scoped thread Target durable mapping and transcript resume across link-holding browser, TUI, and Tauri clients.
CareerVector D1 + connector06 · process · as-built Connector event stream Messages, progress, cancellation, limits, errors, and terminal state are normalized at the client boundary.
CareerVector TUI07 · boundary · target Scoped tool transport Only the approved CareerVector tool boundary receives injected workspace/connector/thread scope.
CareerVector tool service08 · process · as-built Supervision + rollback Cancel, crash, reconnect, protocol mismatch, install failure, and credential revocation fail explicitly.
CareerVector TUI
Flows
- Client execution placement → Managed runtime store select host boundary
- Managed runtime store → App Server · ACP install + launch
- App Server · ACP → Provider authorization provider lifecycle
- Provider authorization → Workspace-scoped thread start or resume
- Workspace-scoped thread → Connector event stream turn stream
- Workspace-scoped thread → Scoped tool transport typed intent
- Scoped tool transport → Connector event stream tool result
- Connector event stream → Supervision + rollback terminal state
- Supervision + rollback → App Server · ACP interrupt, rollback, restart, or stop
Canonical architecture note
Open note ↗CareerVector Assistant Connector Runtime
Outcome
CareerVector can connect a person's provider account, stream an assistant turn, cancel it, expose only bounded CareerVector tools, and recover honestly without treating provider login as product identity or giving a model filesystem, terminal, database, or arbitrary-network authority.
Process placement
The native TUI's device-local host is as built. It downloads checksum-pinned official connector artifacts into private application data, activates them atomically, retains a rollback target, supervises their processes, and keeps provider credentials out of application/workspace data.
The web chat rail still needs an execution bridge. That placement is intentionally open. A hosted service, a local companion, or another reviewed mechanism may be selected only if it preserves link-based workspace access, provider credential isolation, persistent thread/replay semantics, the typed tool boundary, and the no-paywall promise. The architecture no longer assumes a hosted connector gateway indexed by a CareerVector identity principal.
Stable connector boundary
- ChatGPT/Codex uses the official Codex App Server JSONL protocol and ChatGPT device login. It is not ACP.
- Gemini and GitHub Copilot use their native ACP boundaries where provider terms and protocol maturity permit.
- A provider connector owns provider login, credential storage, model/session behavior, stream, cancellation, and limits.
- CareerVector owns the connector allowlist, reviewed versions/checksums, managed installation, process sandbox, context policy, tools, visible events, and recovery.
- ACP interoperability is not provider authorization. Unsupported or legally unclear connectors stay absent.
The TUI's current field-replacement contract and local MCP stdio service are as-built evidence. Product integration replaces their filesystem adapter with the shared canonical assistant tool boundary; it does not grant additional filesystem or shell access.
Thread, event, and privacy contract
Provider runtimes may own opaque provider conversation state. CareerVector owns any workspace-scoped thread mapping, normalized durable transcript/events, tool receipts, and replay cursor needed to project the same assistant through browser, TUI, and Tauri. Route/job/document context narrows a turn but never grants authority.
No prompt, response, document, provider credential, workspace link, or tool payload enters ordinary logs or aggregate Management telemetry. Management may receive connector/runtime version, install outcome, turn duration, limit/error class, cancellation outcome, and explicit participant-supplied diagnostics.
Failure and recovery
- Provider limit or authorization expiry remains distinct from workspace access.
- Connector crash or protocol mismatch fails closed and preserves direct workspace work.
- Runtime install/update verifies provenance before activation and can return to the previous verified version.
- Cancellation, late events, reconnect, and duplicate suppression have explicit terminal rules.
- Web execution failure cannot sign a person out because CareerVector has no product login.
Implementation evidence and gaps
careervector-tui/careervector-tui/src/runtime.rs and assistant.rs are the normative as-built
device-host evidence. lib/agent-gateway remains useful supporting TypeScript evidence for
Codex initialization, normalized events, bounded dynamic tools, and transcript fixtures; it is
not proof of a deployed hosted service or a reason to reintroduce accounts.
Signed cterm/TUI distribution, web execution placement, cross-client persistent threads/events, canonical tool adapters, connector supply-chain projection into Management, and production provider consent smokes remain target/open work.
Acceptance evidence
Acceptance requires hermetic protocol fixtures, checksum/signature and rollback tests, process isolation, credential/log scanning, bounded-tool denial tests, canonical mutation parity, durable stream replay/cancellation, link/provider-authority separation, and one consented smoke for each shipping provider and client placement.