CRM job catalogue
Data governance
no milestone assigned — DATA_GOVERNANCE.md
8 jobs in this area. 8 not supported.
validated end to end An automated test or a checked-in example proves the whole job. This is the only status that counts as evidence.
partially supported Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
technically supported The primitives exist but no test proves the job end to end, so it is not claimed as working.
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.
JTBD-DG-01 · Record consent and lawful basis
not supported
no consent primitive
JTBD-DG-02 · Honor an opt-out across outbound paths
not supported
no outbound paths and no suppression list
JTBD-DG-03 · Export everything held about a subject
not supported
no subject-access path
JTBD-DG-04 · Anonymize or delete a subject while preserving immutable evidence
not supported
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…
JTBD-DG-05 · Apply a retention policy and evidence that it ran
not supported
retention policy and evidence-producing retention execution are not implemented; generic durable jobs and scheduled asks do not supply them
JTBD-DG-06 · Inspect what was shared with which provider
not supported
M9 records inbound provenance only
JTBD-DG-07 · Restrict sensitive fields by role
not supported
needs RBAC
JTBD-DG-08 · Prove a deletion request completed
not supported
needs DG-04
What a status here does not mean
These statuses describe this repository at this commit. None of them implies the framework is deployable: no authentication ships, so a deployment must supply the verifier before anyone but you reaches it, whatever any row says. Every claim and every limitation is on one page.