Skip to content

03-Design — Stage completion gate

Version: 0.3 | Project ID: PRJ-001 | Product version / SHA: a6b4429e3165 | Gate date: Pending

Records

  • [ ] 01 High-Level Design (HLD) — checklist ../03-Checklists/HLD-Checklist.md complete, or written disposition approved.
  • [ ] 02 Data Flow Record — checklist ../03-Checklists/Data-Flow-Checklist.md complete, or written disposition approved.
  • [ ] 03 Low-Level Design (LLD) — checklist ../03-Checklists/LLD-Checklist.md complete, or written disposition approved.
  • [ ] 04 Database Schema — checklist ../03-Checklists/Database-Schema-Checklist.md complete, or written disposition approved.
  • [ ] 05 API Contract — checklist ../03-Checklists/API-Contract-Checklist.md complete, or written disposition approved.
  • [ ] 06 Threat Model — checklist ../03-Checklists/Threat-Model-Checklist.md complete, or written disposition approved.
  • [ ] 07 Architecture Decision Record (ADR) — checklist ../03-Checklists/ADR-Checklist.md complete, or written disposition approved.
  • [ ] 08 Update the Requirements Traceability Matrix with design links — checklist ../../02-Requirements/03-Checklists/Requirements-Traceability-Matrix-Checklist.md complete, or written disposition approved.

Stage exit criteria

  • [ ] Every REQ in the RTM links to at least one DES- item.
  • [ ] Every trust-boundary crossing in the data-flow record has threats assessed and mitigations owned.
  • [ ] Every API operation has a contract with auth, errors and versioning defined.
  • [ ] Database schema identifies all PHI fields with access controls and retention.
  • [ ] Significant decisions are recorded as ADRs.
  • [ ] Independent design review is recorded with actions closed or tracked.

Gate controls

  • [x] All cross-stage links (REQ, DES, API, TC, RISK, REL) used in this stage resolve.
  • [ ] No open critical safety, privacy or security blocker without an authorized written disposition.
  • [x] Product version, commit SHA and record revisions are consistent across the stage.
  • [ ] Gate decision, conditions and approver are stored in the durable system of record.
Role Name Decision Date
Independent reviewer Independent reviewer (name to be assigned — OPEN-021) Pending Pending
Gate approver Sponsor (name to be assigned — OPEN-001) Pending Pending

Gate status, 2026-10-28 (Claude Code): all 7 records drafted (Draft v0.1, a6b4429); the two gate controls ticked were verified by sdlc.py validate and sdlc.py trace. No record is reviewed or approved; open blockers are listed in COMPLETENESS-REPORT.md. The gate decision is for the gate approver.