Skip to content

High-Level Design (HLD) — Completion checklist

Template: TPL-03-01 ../02-Templates/HLD-Template.md | Version: 0.3
How to use: tick an item only after inspecting the completed record and its evidence. Every unticked item needs an OPEN- entry with an owner, or a written, approved disposition.

Content checks

  • [ ] 01. System context and actors — Every external system in the SRS boundary appears in the diagram.
  • [ ] 02. Deployment environments and C4 containers — Each container names its runtime, environment and source repository path.
  • [ ] 03. Components and responsibilities — Each component has one stated responsibility and an owner.
  • [ ] 04. Data stores and service boundaries — Each store has exactly one owning component.
  • [ ] 05. Integration architecture and protocol choices — Every cross-component call states sync/async and failure behavior.
  • [ ] 06. Security and trust boundaries — Each boundary has authentication and encryption stated.
  • [ ] 07. Reliability and disaster recovery approach — RPO and RTO are numbers and match SRS.
  • [ ] 08. Architecture risk decisions and review — Every significant decision links an ADR.

Record control checks

  • [x] Document ID follows KAI-<PRODUCT>-HLD-NNN and is unique in the product.
  • [x] Product, version and commit SHA match the related records.
  • [x] No placeholder rows remain; every gap names an owner and an OPEN- item.
  • [x] Every cited link, file path and ID resolves.
  • [ ] Security, privacy, AI/ML and medical-software applicability checked and routed to qualified reviewers where relevant.
  • [x] No patient identifiers, secrets or production data copied into the record.
  • [x] Nothing was taken from the worked examples as if it were evidence.
  • [ ] Named independent reviewer completed review; approval recorded with date.

Reviewer: Technical reviewer (name to be assigned — OPEN-001) | Date: Pending | Outcome: [Complete / Returned with actions]

Self-check by Claude Code, 2026-10-28, at a6b4429. Ticked items were verified mechanically in this session: sdlc.py validate 0 errors (75 records, stages 01–10); sdlc.py trace no duplicate IDs and every REQ linked to design and test; code citations resolve at a6b4429 (except files in the separate Visionary_oral_ML repository, labelled as external). Content checks are left for the named reviewer; every gap is an owned OPEN- item in the record. Reviewer and approval items are for people.