🗂 Freeze Exception Register
Log and review approved exceptions to active deployment freezes. Each entry captures the approver, reason, scope, expiry, and rollback note. Export the full audit trail for compliance review.
Freeze exceptions are browser-local and read-only from this surface. Entries are written by operators who have been granted explicit T-JOSH authority to override a freeze window. This register does not modify freeze state — use Change Freeze Manager to lift or adjust an active freeze.
Log Freeze Exception All fields required · stored in browser localStorage
Exception Register
No exceptions logged yet.
Use the form above to record the first freeze exception.
Audit Guidance
Each freeze exception entry should capture sufficient context for a post-freeze compliance review. Requirements:
- Approver identity — must be a T-JOSH authority holder or delegated approver with documented authority
- Narrow scope — the exception must be scoped to the minimum set of affected surfaces; prefer Lambda-only or Frontend-only over full-stack
- Defined expiry — every exception must have an expiry timestamp; open-ended exceptions are not permitted
- Rollback readiness — operator must confirm rollback path before executing the excepted action
- Post-exception review — log outcome in Decision Journal within 24 hours of exception expiry
Reference: Change Freeze Manager · Governance Log · Decision Journal · Evidence Gap Finder