Appearance
Process Overview
title: Process Overview description: Reference value stream mapping lifecycle phases to processes and SOPs.
Reference value stream — map phases to your toolchain. Pitfalls and tool alternatives live in decision guides.
Value stream
Process catalog
| ID | Process | Trigger | Primary output | SLA |
|---|---|---|---|---|
| SOP-001 | Feature intake | New epic/story | Scored backlog item + planning ticket | 2 business days to triage |
| SOP-002 | ADR lifecycle | Architectural fork | Accepted ADR in Git | ≤ 3 days to accept |
| SOP-003 | Spec approval | Feature ready to define | Approved OpenAPI + BDD | ≤ 5 days draft → approved |
| SOP-004 | Implementation | Implementation unlocked | PR-ready code + tests | Team sprint commitment |
| SOP-005 | PR review & merge | PR opened | Merged commit on main | ≤ 1 business day review |
| SOP-006 | Release & deploy | Merge to release branch | Prod deployment + smoke green | Tier-dependent |
| SOP-007 | Incident response | Alert / page | Mitigated service + ticket | T1: 15m ack |
| SOP-008 | Post-incident | Sev-1/2 resolved | Postmortem + regression PR | Postmortem ≤ 5 days |
| SOP-009 | Artifact publish | Merge ADR/spec to main | Indexed + portal updated | ≤ 15 min post-merge |
| SOP-010 | AI tool usage | Daily development | Compliant AI-assisted output | Continuous |
| SOP-011 | Engineer onboarding | New hire | Dev env + portal access | Day 1–5 |
| SOP-012 | Exception handling | Gate blocked | Documented exception | SEC: 1 day; other: 2 days |
Phase gates (summary)
| Gate | Entry criteria | Exit criteria | Human approver |
|---|---|---|---|
| G0 — Intake | Business request logged | Priority + tier assigned | PO |
| G1 — Define | G0 complete | Spec approved, ADRs accepted | ARCH + PO |
| G2 — Build | G1 complete (implementation-unlocked) | PR passes all CI checks | DEV reviewer |
| G3 — Release | G2 merged | Staging synthetics green | PO (staging), SRE (prod T1) |
| G4 — Operate | G3 complete | SLOs green 24h | Automated |
| G5 — Learn | Sev-1/2 incident | Regression merged + postmortem | SRE |
Cadence
| Ceremony | Frequency | Participants | Purpose |
|---|---|---|---|
| Backlog refinement | Weekly | PO, ARCH, DEV | Feed SOP-001 |
| Architecture review | Weekly | ARCH, SEC, SRE | ADR decisions (SOP-002) |
| Deploy review | Daily (T1) / on-demand | SRE, DEV | SOP-006 approvals |
| SLO review | Weekly | SRE, ARCH | Tune alerts, baselines |
| AI governance | Monthly | AIPO, SEC, ARCH | Prompt policy, audit sampling |
RACI quick reference
See GOVERNANCE.md for full matrix. Rule of thumb:
- PO owns what and accepts staging behavior
- ARCH owns how across services (ADRs, contracts)
- DEV owns delivery within approved bounds
- SRE owns production safety (deploy, incidents, SLOs)
- SEC owns trust (data in AI, policy exceptions)
- AIPO owns AI platform (models, MCP, audit)