Architecture
This section explains how the workstation is built, why it is structured that way, and where a newcomer should look in the code to connect design ideas to implementation.
The architecture pages are written for someone who wants more than a file listing but less than a line-by-line code commentary. The goal is to make the system legible:
- what the major layers are
- which project owns which responsibility
- how state flows from runtime services to the UI
- how workflow transitions, faults, recovery, and persistence fit together
This architecture pack is grounded in:
- ADR-001: Use Central App State Store
- ADR-004: Use One Operational Maturity Slice Before Specialized Modules
- SLICE-001: First Strong Vertical Slice
- SLICE-004: Operational Maturity
Reading Order
- 01. System Context
- 02. Project and Layer Map
- 03. Domain Model
- 04. Workflow and State Model
- 05. Runtime Sequences
How To Read This Pack
Each page tries to do four things:
- explain the design in practical English
- point to the code that actually carries the design
- call out trade-offs instead of only describing ideals
- end with a Draw.io-friendly diagram brief
The intention is that a newcomer can read one page, open two or three code files, and immediately see the connection between architecture and implementation.
Pair This Pack With
Use these alongside the architecture pages:
After The Architecture Pack
The strongest next pages are: