Sheet A-02 · Section
A section
through a project
Six layers, each with an artefact and a decision point. You can stop after any layer and keep everything produced.
- L1
Survey
Interviews, review of existing systems, list of entities and owners.
- Duration
- 1–2 weeks
- Artefact
- Domain map, risk list
- L2
Drawing
Container architecture, consistency models, storage choices.
- Duration
- 1–2 weeks
- Artefact
- C4 diagrams, ADRs, estimate
- L3
Prototype
Clickable prototype plus a technical spike on the riskiest part.
- Duration
- 2–3 weeks
- Artefact
- Prototype, spike report
- L4
Build
Development with a demo after every sprint and consistency tests.
- Duration
- 2-week sprints
- Artefact
- Builds, changelog
- L5
Verification
Load, fault tolerance, accessibility, security.
- Duration
- 1–2 weeks
- Artefact
- Test protocol
- L6
Handover
Publishing, runbooks, training your team.
- Duration
- 1 week
- Artefact
- Runbook, access, keys
How we measure quality
| Dimension | Criterion | How we check |
|---|---|---|
| Consistency | No duplicates on retry | Test with simulated network drop |
| Recovery | Agreed RPO and RTO | Rehearsed restore from backup |
| Accessibility | WCAG 2.2 AA | Manual screen reader and keyboard pass |
| Performance | Agreed response time budgets | Load test with protocol |