Plan

Outcome: Approved work ready for implementation — classified, architecturally sound, with an accepted spec and ADRs.

Goals

• Business priority and acceptance criteria are clear
• Data classification is assigned at intake
• Architecture decisions are recorded (ADR) before coding
• Spec is reviewed and Approved (not draft)

Key roles

Role	Accountable for
PO	Priority, acceptance criteria
ARCH	ADRs, API contracts
SEC / DATA	Classification, threat model (T1/T2)
Program manager	Cross-team dependencies

→ Product manager perspective · Architect perspective

Decision guides

• Planning, ADR & specs
• Data governance layers
• Knowledge indexing & portals
• Human-in-the-loop & governance

Topic deep dives

• Planning & ADR · Data governance

Reference SOPs

SOP	Procedure
SOP-001	Feature intake
SOP-002	ADR lifecycle
SOP-003	Spec approval

Gates before Build

::: decision Recommended gate No implementation (SOP-004) until: Approved spec + Accepted ADR(s) + security sign-off when tier requires it. :::

Pitfalls

Pitfall	Mitigation
AI-drafted spec merged without review	Human ARCH/PO approval (SOP-003)
Skipping ADR for "small" AI changes	ADR for any new pattern or cross-service boundary
No classification on ticket	SOP-001 checklist

---

← Lifecycle overview · Build →