Architecture Records
Use this collection for durable decisions that should not be reconstructed from chat history or inferred from code shape alone. This is the records shelf for architecture choices, target states, and the contract rules that shape the system.Who This Is For
- Engineers who need the reasoning behind a durable platform decision.
- Reviewers who need to understand what is accepted, what is target state, and what still needs work.
- Operators who need the architectural boundary conditions that affect runtime changes.
How To Use It
- Start with the ADR index for the canonical decision log.
- Use the Architecture Artefact Register for the workspace-wide inventory and authority classification.
- Use the Master Document Control for baseline versioning, promotion rules, and change control.
- Read ADR-0001 for the current interim repository model.
- Read ADR-0002 for the long-term platform/tenant split target.
- Read ADR-0003 for the contract-order rule that keeps types, schema, API, UI, and docs aligned.
- Use the Tremor operating wiki architecture page when you need the living architecture/schema summary in the company corpus.
Core Entry Points
- ADR index
- Architecture Artefact Register
- Master Document Control
- ADR-0001: Intentional Monorepo Interim State
- ADR-0002: Platform/Tenant Repo Target State
- ADR-0003: Canonical Schema Authority
- Architecture & Schema
- Tremor repository boundaries
- Repo strategy
- Companies spec