Person
Chooses and authorizes a vendor chatbot independently from either product.
PersonBlueprint · domain
08 · AI
CareerVector and JobCache integrate SOTA vendor chatbots through protocol adapters and typed tools instead of building a competing model or general-purpose agent runtime.
Cell 3.3 · product · runtime · control · privacy- Person to Vendor SOTA chatbot: choose + authorize
- Vendor SOTA chatbot to Protocol adapter: protocol events
- Protocol adapter to Typed product tools: typed intent only
Vendor SOTA chatbot
ChatGPT, Gemini, Copilot, and later vendors own model execution, conversation UX, and provider identity.
AI vendorProtocol adapter
Official app-server, ACP, MCP, or later vendor-supported protocols normalize lifecycle, streaming, cancellation, and tools.
Open layer ↘Typed product tools
The products expose explicit context and operations; the model receives no ambient database, filesystem, terminal, or Management authority.
Owning product01 · actor · mixed Person Chooses and authorizes a vendor chatbot independently from either product.
Person02 · perspective · mixed Vendor SOTA chatbot ChatGPT, Gemini, Copilot, and later vendors own model execution, conversation UX, and provider identity.
AI vendor- 03 · service · mixed Protocol adapter
Official app-server, ACP, MCP, or later vendor-supported protocols normalize lifecycle, streaming, cancellation, and tools.
Open deeper layer ↘ 04 · boundary · target Typed product tools The products expose explicit context and operations; the model receives no ambient database, filesystem, terminal, or Management authority.
Owning product
Flows
- Person → Vendor SOTA chatbot choose + authorize
- Vendor SOTA chatbot → Protocol adapter protocol events
- Protocol adapter → Typed product tools typed intent only
AI
Outcome
Use the best current vendor chatbot instead of building a CareerVector model, inference router, or general-purpose agent runtime. The person chooses and authorizes ChatGPT, Gemini, Copilot, or another supported vendor. The vendor owns model execution, provider identity, plan limits, and the general conversation surface.
Integration boundary
The AI domain normalizes only what the products need:
- provider authorization and connector lifecycle;
- official app-server, ACP, MCP, or later vendor-supported protocol negotiation;
- streaming messages, progress, cancellation, errors, and terminal state;
- typed tool discovery, invocation, results, and receipts;
- thread identifiers needed to resume a product-scoped conversation.
Protocol names are adapters, not architecture. ChatGPT currently uses the official Codex App Server path in the imported TUI; Gemini and Copilot use native ACP connectors. A future vendor may expose a different supported protocol without changing product authority.
Authority
- The vendor owns provider accounts, models, plans, and generic chat history.
- JobCache owns public corpus truth, sessions, optional JobCache accounts, capabilities, and charge targets.
- CareerVector owns link-scoped private workspace truth and has no first-party accounts.
- A trusted product/client host resolves scope and injects only bounded tool authority.
- Management owns provider policy, approved connector supply, cost/usage evidence, monitoring, audit, and recovery—not prompts, workspace content, or product mutations.
Invariants
- The model never receives ambient database, filesystem, terminal, workspace-link, or Management authority.
- Product writes use the same typed, revision-safe operations as direct UI actions.
- Provider authorization is separate from JobCache session/account authority and CareerVector workspace-link authority.
- A chatbot answer is not product truth; JobCache evidence and CareerVector receipts remain the attributable sources.
- A provider or protocol can be removed without moving canonical product state.
Current state
The imported terminal TUI has as-built managed Codex App Server and ACP connector lifecycles, streaming, cancellation, bounded field tools, and rollback. The shared cross-client connector contract, browser/Tauri hosting choice, durable thread mapping, and complete product tool suites remain target work.
Completion evidence
Run the same bounded task through two vendor protocols; prove provider authorization isolation, scope injection by the trusted host, denial of undeclared tools, cancellation, reconnect, typed receipts, product-state convergence, connector rollback, and removal of all first-party model routing assumptions.