Engineering
Engineering begins with the shared requirements contract in ../REQUIREMENTS.md and follows it through design, pre-release evidence, continuous delivery, and production learning.
Lifecycle
Section titled “Lifecycle”| Document | Responsibility |
|---|---|
ARCHITECTURE.md |
How domain boundaries and system components satisfy the requirements. |
TESTING.md |
How tests and CI prove the system before release. |
PUBLISHING.md |
How verified artifacts are versioned, promoted, deployed, and rolled back. |
OBSERVABILITY.md |
How production health and user outcomes are measured and fed back into discovery. |
adrs/ |
Why significant product and technical decisions were made. |
Supporting documentation
Section titled “Supporting documentation”Lifecycle detail lives in the files linked from Lifecycle above. Add focused setup guides, runbooks, or API references here only when the project needs them; none exist yet.
Decision records
Section titled “Decision records”Create the next Architecture Decision Record with:
docslime add adr <short-slug>Keep the decision log in adrs/README.md synchronized with accepted, superseded, and deprecated records.