Role search
Filters and ranking operate on current role projections rather than disconnected URLs.
JobCache AppBlueprint · 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.2 · product · data · evidence
Search, roles, and evidence
The product view is role-first: results remain traceable to ads, observations, freshness, and disagreement.
- Role search to Role result: ranked query
- Role result to Evidence timeline: supported by
- Evidence timeline to Saved view / snapshot: pin result
Role result
One role may aggregate several source ads while retaining disagreement.
JobCache CoreEvidence timeline
Ads, observations, validity intervals, provenance, and corrections.
JobCache AppSaved view / snapshot
Session-local immutable result references and collaboration.
JobCache App D101 · perspective · target Role search Filters and ranking operate on current role projections rather than disconnected URLs.
JobCache App02 · process · mixed Role result One role may aggregate several source ads while retaining disagreement.
JobCache Core03 · perspective · target Evidence timeline Ads, observations, validity intervals, provenance, and corrections.
JobCache App04 · store · as-built Saved view / snapshot Session-local immutable result references and collaboration.
JobCache App D1
Flows
- Role search → Role result ranked query
- Role result → Evidence timeline supported by
- Evidence timeline → Saved view / snapshot pin result
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.