Repository navigation
State each repeated rule once, in its widest template #2133
Description
Part of #2124.
The same rule appears in several templates in different words, so the redundancy audit misses it. An agent meets it several times, sometimes with differing detail.
| Rule | Stated in |
|---|---|
| Health check passes before traffic | backend/observability.md:59, infra/cicd.md:54, infra/containers.md:78, backend/microservices.md:81, backend/edge.md:34 |
No secrets in source; .env.example |
security/security.md:105-114, core/config.md:12-16, core/git.md:12-15, security/devsecops.md:35-38, infra/containers.md:21, infra/deployment.md:59 |
| Migrations versioned and reversible | backend/database.md:6-10, data/data-modeling.md:48-55, data/data-migration.md:11-30 |
| Image vulnerability scan | security/devsecops.md:64, infra/containers.md:33-36, infra/deployment.md:48 |
| Editable content in a data directory | core/quality.md:33, frontend/content.md:12 |
| No gRPC for browser clients | backend/api.md:26, backend/grpc.md:15 |
| Commit the lockfile | core/git.md:20, core/config.md:84 |
The widest template does not reach every chain that holds a copy, so removing a copy can drop the rule from a chain.
Done when
- Each rule lives in the template with the widest chain reach (ADR-028)
- Every chain that resolved a copy before still resolves the rule after, checked with
py tools/resolve_chain.py <id>per root - The other copies point to it or are removed
Activity
fix(templates): keep the irreversible-migration exception in data-mig…