Only documents under current/ describe the current supported understanding of the
product. When source and prose disagree, source wins and the documentation is a defect.
- Architecture
- Data model
- Generated model inventory
- HTTP surface and trust model
- Generated route inventory
- Security and data lifecycle
- Self-hosting
- Testing
- Licensing decision
- Rights register
- FOSS-posture audit
Generated inventories are derived from the current web source. pnpm docs:check fails when the
committed inventory differs from a fresh generation.
The following material can explain how a feature arrived, but it is not an operational contract:
apps/web/docs/SPEC.md— historical build briefdocs-split-rooms-spike.md— original spikechangelog-july-25.md— early design decisionsROADMAP.md— planning and historical decisions, not a current API/schema reference
Historical documents must retain a visible historical label. They must not be linked as the current architecture, schema, API, security, or self-host contract.