Opaque shared session
Link capability owns saved work and collaboration without exposing Core identity.
JobCache App D1Blueprint · careervector.blueprint-graph/v5
Graph explorer
Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.
Cell 1.3 · product · operations · evidence
Trust, sessions, and service state
Sharing, freshness, failure, paid placement, and support remain legible instead of being hidden behind a polished result.
- Opaque shared session to Trust explanation: context
- Trust explanation to Status and support: explain or escalate
Trust explanation
Freshness, provenance, uncertainty, degraded service, and paid placement.
JobCache UI/API/MCPStatus and support
Public service truth plus scoped correction, export, and support entry points.
Status and Management01 · store · as-built Opaque shared session Link capability owns saved work and collaboration without exposing Core identity.
JobCache App D102 · perspective · target Trust explanation Freshness, provenance, uncertainty, degraded service, and paid placement.
JobCache UI/API/MCP03 · perspective · target Status and support Public service truth plus scoped correction, export, and support entry points.
Status and Management
Flows
- Opaque shared session → Trust explanation context
- Trust explanation → Status and support explain or escalate
Canonical architecture note
Open note ↗JobCache Experience
Purpose
Explain the complete JobCache product mechanism and visual language from a user's point of view. This band spans ingestion, product, and management because a coherent experience must cover discovery, evidence, saved work, freshness, support, and system state.
Owns
- Search, recommendation, evidence, and market-intelligence interaction patterns.
- Saved views, immutable snapshots, shareable sessions, and collaboration language.
- The relationship between human UI, public API, and MCP perspectives.
- Product-wide navigation, visual hierarchy, trust signals, empty states, and explanations.
- Honest presentation of freshness, provenance, degraded service, and unavailable results.
Does not own
- Acquisition scheduling or scraper execution.
- Canonical ad, role, evidence, or embedding truth.
- Operator authority, incident handling, or regulatory policy.
Current state
The JobCache UI, App API, and MCP perspectives are live. They share the public shell and collaboration foundations with CareerVector where the mechanism is genuinely the same. Most product-specific search, map, recommendation, and commercial workflows remain target work.
Agent contract
An implementation claim belongs here only when it describes what a JobCache user or API consumer experiences. Link domain behavior to JobCache, acquisition behavior to Ingestion × JobCache, and operator behavior to JobCache × Management.
Completion evidence
- Browser journeys for the complete JobCache information architecture.
- API/MCP parity tests for each exposed capability.
- Accessibility and responsive-layout evidence.
- Visual snapshots for the shared shell and JobCache-specific workflows.
- Production probes that distinguish healthy, stale, degraded, and unavailable states.