This page lists the documents that these standards depend on. It separates binding policies from advisory guides, links to the external standards used by the normative pages, and links to related standard pages. References also works as a site index. Each entry says what it covers, so you can choose the right document without opening them all.
Controlling policy (normative)
These documents are binding. If a standard page conflicts with one of them, the controlling policy takes priority.
| Document | Governs |
|---|---|
| S-SDLC | Four-eyes review and code review, the controlling policy behind /four-eyes and /code-ownership. |
| SDLC & Change Management Policy | Change control, approvals, and release governance behind /release-and-incidents. |
Guides and templates (informative)
These documents are advisory. They show recommended practices. They do not replace a standard page or a controlling policy.
| Document | Use for |
|---|---|
| [TEMPLATE] Design Document | Starting a design doc, see /design-docs-rfcs-adrs. |
| RFCs and ADRs | Proposing and recording architecture decisions. |
| Testing Handbook | Test strategy and coverage practice, see /testing. |
| Feature Flagging Strategy | Statsig flag lifecycle, see /feature-flags. |
| Incident Management | Incident response and postmortems, see /release-and-incidents. |
| Sentry Working Guide | Error monitoring practice, see /observability. |
Foundational standards (external)
The normative pages use these external standards. Cite the official specification instead of repeating it.
| Standard | Anchors |
|---|---|
| Conventional Commits 1.0.0 | Commit message format, /ci-cd. |
| Semantic Versioning 2.0.0 | Version-bump rules, /release-and-incidents. |
| Keep a Changelog 1.1.0 | Changelog format, /release-and-incidents. |
| The Twelve-Factor App | Config, logs, and disposability, /architecture, /ci-cd. |
| OWASP Application Security Verification Standard | Security requirements catalog, /security, /authentication. |
| OpenTelemetry documentation | Traces, metrics, and logs, /observability. |
| C4 model | Architecture diagram convention, /architecture, /design-docs-rfcs-adrs. |
Sibling standard pages
References indexes the rest of the document set. Start at /team-standards for the complete list.
| Page | Covers |
|---|---|
| /principles | Engineering principles and values. |
| /architecture | System design and boundaries. |
| /four-eyes | Review requirements. |
| /quality-gates | Merge and release gates. |
| /testing | Test strategy and coverage. |
| /ci-cd | Build, commit, and deploy pipeline. |
| /security | Security controls. |
| /authentication | Identity and access. |
| /observability | Logs, metrics, and traces. |
| /feature-flags | Statsig flag practice. |
| /release-and-incidents | Release and incident process. |
| /open-questions | Unresolved policy decisions. |
Maintaining this index
Keep every Confluence link as a page-ID URL, as shown above. A page-ID URL still works after a page rename. A title-slug URL breaks after a rename.
Source of truth: Software Engineering Standards in Confluence (space DSE). This site mirrors that page.