Official References: Security · Sub-agents · Best Practices
High-risk changes need governance, not just good prompts
For auth, billing, permissions, and data migration surfaces, treat delivery as governance workflow:
- explicit risk class
- explicit final owner
- explicit rollback trigger
Five governance gates
- code quality gate
- security/review gate
- operational readiness gate
- communication gate
- final go/no-go gate
Advanced release decision record
Every high-risk change should produce one decision block:
- scope
- risk class
- gate statuses
- residual risks
- rollback trigger + owner
- final decision + timestamp
Required escalation rule
If a blocking risk survives two iterations:
- mark status
blocked - escalate with evidence
- assign new owner and deadline
Unowned blockers are governance failures.
Advanced anti-patterns
Test pass treated as deploy permission
Passing tests are necessary, never sufficient.
Go/no-go without named accountable owner
Ambiguity at this step creates incident-time confusion.
Rollback exists only in theory
If rollback is not rehearsed, it is not ready.
Quick checklist
Before production:
- risk class declared
- governance gates evaluated
- final owner signed off
- rollback trigger documented and tested
- escalation path active
Advanced delivery is not faster by default. It is safer under stress.