Solution Design Template
This is the per-solution template. Copy this template/ directory to solution-design/<solution-name>/, rename the heading to the solution name, and fill in the documents that fit the engagement.
The documents below are a suggested menu, not a mandated set. Delete the ones a solution does not need and add others if the engagement calls for them.
Documents
| Document | Status | Last updated | Description |
|---|---|---|---|
| Vision | 🔬 Exploring | 2026-06-25 | Why build this; the dream and the headline experience |
| Requirements | 🔬 Exploring | 2026-06-25 | What it must do — pick the flavor (BRD / PRD / SRS) |
| Exploration | 🔬 Exploring | 2026-06-25 | Spikes, domain primers, investigations, findings |
| Architecture | 🔬 Exploring | 2026-06-25 | How it is built; ADRs as decisions settle |
Keep this table current. It is the at-a-glance view of where each document stands.
Living-Doc Conventions
Every document in this set carries a status line, a last-updated date, and a note that it is a living document. When a topic stabilizes, copy the canonical version to developer-docs/, guides/, or user-docs/ — the version here stays as the living record. See the section overview and the how-to guide for the full conventions.