Core Concepts
Operational Readiness
Whether the org can run deletions confidently, not a compliance score.
Operational Readiness
What it is
Operational Readiness is an aggregate signal: can this organization start and run deletion work with confidence?
States typically include: ready · attention · blocked · unknown.
Why it exists
Starting a deletion against incomplete maps or offline workers creates false confidence. Readiness surfaces blockers before the first production case.
What it considers (product)
Signals may include (exact UI aggregates evolve with product releases):
- Systems present, enabled, and healthy enough
- Data Maps ready for map-backed Systems
- Start readiness (DELETE entities + identifiers where required)
- Worker / queue hints
- Project-level consent/receipt signals where shown
What it is not
| Not | Why |
|---|---|
| Compliance score | No legal certification |
| Guarantee of DPDP compliance | Operational only |
| Proof for unconnected systems | Only configured Systems |