Why This Was Blocked
Plain-language explanation for buyers, auditors, and operators reviewing a governed release decision.
trace_id: d3f7da18-6379-485f-a1c8-eeba0112aa63
Decision
Blocked before release
A governance control blocked this release.
Policy
Release rule evidence attached
This decision is tied to a specific policy snapshot, so the exact control can be traced later.
Evidence
0 signals reviewed
No signal details were attached to this decision.
Decision Summary
Release protection stopped this change before deployment.
A governance control blocked this release.
Business impact
A governance control stopped the change, preserving review discipline before release.
Recommended next step
Fix the missing control evidence, then re-run the release once the protection requirement is satisfied.
Audit Lens
Control evidence attached
- Decision hashes are present; snapshot verification should be confirmed.
- 1 linked evidence artifact available.
- Deterministic replay link is available.
- Approval freshness window was not enforced for this decision.
- Risk posture: Low.
Decision hashes are present, but snapshot verification should be confirmed before using this as audit evidence.
Snapshot Binding
These hashes identify the exact policy snapshot and decision evidence used for this outcome.
- policy_hash: 96aa02c9bca521d8346356964c905999fa4edc7b735aad1c7f1bba3ecd2508d5
- policy_resolution_hash: -
- snapshot_hash: -
- decision_hash: bf2f263c5fe2ce1e19200968f1a65dce1aeea383aa5be65cff98572cdeeaa095
- signal_bundle_hash: -
Why this was blocked
A governance control blocked this release.
Reason code: No reason code recorded.
Actor: -
Environment: -
Issue: -
Workflow: -
Transition: -
Reason code: -
Evidence & Replay
Risk posture
0.000
Low risk based on the weighted components below. This is the technical breakdown behind the decision.
| Name | Value | Weight | Notes |
|---|