The thinking the CRM was built from, kept beside the code so the next change can argue with it:
- Design Brief — what a CRM has to do before it gets clever: five capability areas as requirements (Samuel Glauser, 2026-08-28).
- Ideas — five ideas where building on MeshWeaver beats renting, each with its mechanism named (Samuel Glauser, 2026-08-28).
- Journey Model — the stage catalog, the status enum, the seven
rendering rules and the canonical journey data as of 19 August 2026 (Robert Salzmann). This is
the specification
Crm/Source/Journey.csimplements and the portfolio board renders.
What is decided and what is still open lives in the Crm/Guide; disagreement goes in comments on
these pages or a PR against the repository.