JobCache Obligations
Purpose
Collect obligations created specifically by operating JobCache as the commercial product. The shared Operating Stack still applies; this module contains only the product-specific extensions.
Each resolved item is an Operating Obligation record governed by Operating Obligation Model; this page is the product-specific source and index, not a second register.
Categories
| Category | Architectural concern |
|---|---|
| Corpus claims | What “current”, “complete”, “verified”, and “evidence-backed” are allowed to mean |
| Provenance | Source attribution, acquisition history, corrections, and contested facts |
| Customer contract | Availability, export, retention, support, and service commitments |
| Commercial model | JobCache UI is the monetized product; controls must not leak into CareerVector |
| Publication | Takedown, suppression, correction, and appeal paths for public corpus data |
| Automation | Honest disclosure of automated enrichment and its uncertainty |
Invariants
- A commercial preference cannot rewrite corpus evidence.
- Sponsored or targeted jobs must be visibly distinguishable from organic ranking inputs.
- Customer-local identity and saved state remain in JobCache App, outside JobCache Core.
- A freshness claim must be computable from retained evidence, not marketing prose alone.
Decisions still required
- Service and freshness promises by product tier.
- Corpus correction, publisher dispute, and takedown policy.
- The exact separation between relevance ranking and paid placement.
- Export, retention, and support commitments for customer state.
Completion evidence
Each obligation needs an accountable owner, a machine-readable rule where possible, an operator workflow, an audit record, and a user-visible explanation.