Corpus claims
Definitions for current, complete, verified, and evidence-backed.
Product ownerBlueprint · 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.4 · governance · operations · evidence
JobCache obligations
Commercial promises are translated into enforceable corpus, provenance, publication, and customer obligations.
- Corpus claims to Publication duties: constrains
- Customer contract to Commercial separation: separates
- Corpus claims to Customer contract: promises require proof
Publication duties
Attribution, correction, takedown, suppression, and appeal.
Product and legalCustomer contract
Availability, export, retention, support, and service commitments.
Product ownerCommercial separation
Paid placement cannot silently rewrite organic relevance or evidence.
Product owner01 · obligation · open Corpus claims Definitions for current, complete, verified, and evidence-backed.
Product owner02 · obligation · open Publication duties Attribution, correction, takedown, suppression, and appeal.
Product and legal03 · obligation · open Customer contract Availability, export, retention, support, and service commitments.
Product owner04 · boundary · open Commercial separation Paid placement cannot silently rewrite organic relevance or evidence.
Product owner
Flows
- Corpus claims → Publication duties constrains
- Customer contract → Commercial separation separates
- Corpus claims → Customer contract promises require proof
Canonical architecture note
Open note ↗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.