owner, delegation, accountable team
Ownership
Who is allowed to make this change?
Controls
Five domains, many implementations.
PED control domains give delivery systems a shared vocabulary without requiring every team to use the same workflow or toolchain.
security, architecture, compliance
Conformance
Does it match policy?
rollback, backup, feature flag
Reversibility
Can we recover?
systems, users, data, dependencies
Blast radius
What can it affect?
tests, screenshots, health checks
Evidence
What proves it works?
Ownership
Use CODEOWNERS, service catalogs, team membership, or resource tags to prove authority.
Conformance
Use policy-as-code, static analysis, scanners, or metadata checks to prove alignment.
Reversibility
Use rollback plans, down migrations, backups, feature flags, or restoration evidence.
Blast radius
Use dependency maps, environment metadata, user impact, data classification, and deployment surface.
Evidence
Use tests, screenshots, health checks, rendered docs, link checks, and runtime observations.
Review rationale
When controls cannot decide, capture the reason so repeated ambiguity can become policy.
Control status
Controls do not have to be dramatic.
Each control emits `pass`, `fail`, `needs_review`, or `not_applicable`. The power is in making those results visible and comparable across delivery workflows.