Skip to content

Standard Operating Procedures (SOPs) ​


title: Standard Operating Procedures (SOPs) description: Index and guidance for Standard Operating Procedures referenced across the repository. ​

Reference playbooks only. These describe how a team might operate — customize for your org, tooling, and compliance tier. Do not implement CI labels, workflows, or automation from this repository.

Each SOP follows the same structure: purpose, RACI, steps, Definition of Done, SLA.

Before customizing: read the relevant decision guide for alternatives and pitfalls.

  1. Purpose & scope
  2. Roles (RACI)
  3. Prerequisites
  4. Procedure (numbered steps)
  5. Definition of Done
  6. SLA & escalation
  7. Related SOPs

SOP index ​

SOPTitleOwner
SOP-001Feature intake & prioritizationPO
SOP-002ADR creation, review, acceptanceARCH
SOP-003Spec authoring & approvalARCH + PO
SOP-004Spec-driven implementationDEV
SOP-005Pull request review & mergeDEV
SOP-006Release & deploymentSRE
SOP-007Incident responseSRE
SOP-008Post-incident & regression loopSRE + DEV
SOP-009ADR & spec publish/indexSRE / Platform
SOP-010AI tool usage & data handlingAIPO + SEC
SOP-011Engineer onboardingEM
SOP-012Policy & gate exceptionsSEC / EM

How SOPs relate to architecture ​

Architecture layerPrimary SOPs
Planning & knowledgeSOP-001, 002, 003, 009
Developer loopSOP-004, 010, 011
QA & guardrailsSOP-005 (CI gates embedded)
CI/CDSOP-006
ObservabilitySOP-007, 008
GovernanceSOP-012, GOVERNANCE.md

SOP change control ​

  • SOP changes require PR review by process owner + one affected role
  • Major changes (new gates, new approvers) require ARCH sign-off
  • Version noted in each SOP footer: SOP-XXX v1.0

Reference template only — no production code. Adapt in your own project.