Search docs
Docs searchValidation category
Safety Controls
Review implemented validation rules for ADR coverage, rollback planning, and staged rollout evidence around higher-risk changes.
Safety Control findings help teams prove that risky architecture or workflow changes have decision context and recovery plans.
Overview
Review implemented validation rules for ADR coverage, rollback planning, and staged rollout evidence around higher-risk changes.
Safety Control findings help teams prove that risky architecture or workflow changes have decision context and recovery plans.
Why it matters
Cloud uses this guidance to help teams interpret local validation findings in organization context without turning the docs into implementation notes.
When this domain drifts, findings become harder to triage, ownership becomes less clear, and architecture review depends too much on individual memory.
Good architectural practices
- ADR coverage for significant or risky changes.
- Rollback or recovery plans documented before rollout.
- Feature-flag or staged rollout evidence for changes that need controlled release.
Common anti-patterns
- Missing ADR coverage for risky architecture change
- Missing rollback plan for risky architecture change
- Missing feature-flag or staged rollout evidence for risky architecture change
Relationship to other architecture areas
This domain usually overlaps with neighboring validation categories. Use the related pages below to understand the adjacent architecture concerns before changing policy, suppressing a finding, or accepting risk.
Implemented rules
These are the currently implemented rules in this category. Use this table for category-level orientation, then open the Rule Catalog when you need rule-specific examples and remediation guidance.
| Rule ID | Rule title | Category | Severity | Short explanation | Example violation | Remediation guidance | Rule detail |
|---|---|---|---|---|---|---|---|
| AP-SAFE-001 | Missing ADR coverage for risky architecture change | Safety Controls | warning | Flags risky architecture changes that lack ADR evidence. | A module boundary is changed with only an inline PR comment. | Write or update an ADR. Include context, decision, consequences, and rollback notes if relevant. Link the ADR from the architecture overview or related docs. | View rule page |
| AP-SAFE-002 | Missing rollback plan for risky architecture change | Safety Controls | warning | Flags risky changes without rollback plan evidence. | A data ownership migration has no rollback or pause criteria. | Add rollback steps to the ADR, runbook, or migration notes. Name the conditions that trigger rollback. Document any irreversible steps clearly. | View rule page |
| AP-SAFE-003 | Missing feature-flag or staged rollout evidence for risky architecture change | Safety Controls | warning | Flags risky changes without staged rollout or feature-flag evidence. | All traffic moves to a new routing path with no staged rollout evidence. | Add rollout evidence to the ADR or runbook. Introduce a feature flag or staged deployment plan when appropriate. Document monitoring and completion criteria. | View rule page |
Related pages
Next steps