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.