Appearance
TMS v2 — reference document
What TMS v2 is today, for talking about the whole system in one meeting. Every item says whether it is built (in code on main-v2-prototype at 3d70475a, 9 Nov 2026) or only designed (in the discovery workspace), so a design is never mistaken for working code.
New to v2, or about to write a spec? Start with the three business overview pages. The numbered files are reference: open the one the discussion needs.
| file | read it for | size |
|---|---|---|
| overview.md | the whole system on one screen: who takes part, one order's day, the records, who owns what, a spec checklist | 2 diagrams |
| foundations.md | the eight rules every feature follows, what each guarantees and what a spec must state | 8 rules |
| v1-vs-v2.md | why rewrite, what stays, every change by area with its gain and trade-off, migration | 18 areas |
| 01-feature-list.md | every feature by module, status Built / Partly built / Designed / Cut | 154 features |
| 02-system-overview.md | what the system does, component diagram, module map, build phases, where code and design disagree | 1 diagram |
| 03-schema.md | every collection: fields, types, enums, indexes, ER diagram, schema oddities | 28 collections |
| 04-states-and-flows.md | lifecycle of DO, plan, task, stop, duty, COD, job; end-to-end sequences | 14 diagrams |
| 05-conditions.md | business rules as "when … the system must …", enforced or not, rules waiting on BigC | 158 rules |
| 06-master-data.md | reference data: who creates it, who reads it, record counts, enum lists | 13 items |
| 07-integrations-and-jobs.md | Kafka topics, external APIs, schedules and jobs, log retention | 6 topics |
Where things stand
| group | built / total features | note |
|---|---|---|
| Platform | 14 / 28 | jobs engine, logs, settings, files built; auth fixes are the next build |
| Intake / DO | 4 / 18 | Kafka intake works but uses v1 status names and overwrites any DO |
| Planning | 4 / 20 | optimise works inside the request; generate tasks is a stub |
| Master data | 5 / 17 | vehicle plate not unique; role is a fixed list |
| Admin / reporting | 3 / 11 | templates, export configs, field catalog only |
| Workforce | 1 / 19 | not started |
| Execution | 0 / 28 | not started; driver app v2 not started |
| COD | 0 / 13 | not started |
Business rules: 47 enforced, 66 designed only, 28 where the code does something different, 17 still waiting on BigC.
Not in this document
- Screens and UI: left out on purpose for now.
- Why each choice was made: the decision log in the discovery workspace.
- Diagrams are Mermaid; all 16 render cleanly with Mermaid 11.4.1 (checked 11 Nov 2026).