JTBD-DG-04 · Data governance
Anonymize or delete a subject while preserving immutable evidence
not supported. No implementation and no test. It would have to be built. This is the default status in the catalogue — a row moves out of it only when a test proves it.
What the catalogue records
the hardest design in the track: commercial evidence is deliberately immutable. Customer Data Foundation v1 does not move this row and does not claim to: it anonymizes and deletes nothing, its canonical link deletes nothing, and governing a data-quality finding records a decision while keeping the finding and its evidence. The only related fact it contributes is a narrow negative one — no raw provider payload is retained from an import — which is a smaller claim than this row asks for and is not a step toward it
Evidence
This row names no test and no document of its own, and its status does not claim one. Treat it as unbuilt: nothing here proves it, and nothing here says otherwise.
What this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Data governance
- Record consent and lawful basis — not supported
- Honor an opt-out across outbound paths — not supported
- Export everything held about a subject — not supported
- Apply a retention policy and evidence that it ran — not supported
- Inspect what was shared with which provider — not supported
- Restrict sensitive fields by role — not supported
- Prove a deletion request completed — not supported