Readiness as policy

Replace the generic checklist with explicit release logic.

Versioned policy selects obligations from release facts, tests evidence and thresholds, records exceptions, and explains the recommendation.

Gate resultConditional go

2 blocking actions remain

Multidimensional readiness

A healthy average must never hide a critical failure.

Dimensions remain separate, and blocking controls cannot be averaged away. Policy determines which evidence is required for this specific release.

Release gateEvidence enters by dimension. Policy preserves the blockers.

94Technical88Agent100Security72Operations58People80Measure

Release facts

POLICYv1.0rules · thresholds · exceptions

Human authority

Conditional go

78overall

Blocking

Support approval

Training threshold

Recommendation ≠ decision

Technical94%

Function, integration, performance, deployment, rollback

Agent quality88%

Task success, tool use, grounding, safety, escalation

Security + data100%

Identity, access, privacy, retention, audit

Operational72%

Monitoring, support, incident handling, continuity

People58%

Role impact, communication, training, feedback

Measurement80%

Baseline, target, source, period, benefit owner

Policy-as-code

Release facts become obligations—consistently and audibly.

A visual editor can make policy accessible, while the underlying representation remains versioned, testable, and reconstructable.

when: agent.has_write_access == true
require:
  - security_review == approved
  - rollback_test == passed
  - human_escalation == validated

when: affected_users >= 500
require:
  - support_plan == accepted
  - training_plan == accepted

From fact to decision

Five distinct records preserve accountability.

The system recommendation and the human decision are deliberately separate.

01FactAgent gains write access

02ObligationRollback test required

03EvidenceTest run #882 accepted

04RecommendationConditional go

05Human decisionApproved with condition

Exceptions are not missing data.

Every exception names the unmet rule, accepting authority, reason, compensating action, scope, and expiration.

See the MVP release gate

Start with one real release

Make readiness visible before production makes gaps expensive.

See the MVP