data-modelinglisted

# The template Kintwadi's `docs/data-model.md` is not a schema dump; it's an argued document, and its section order is the argument. Twelve top-level sections, in this order: 1. **Why a relational model** — the case for the shape, before any table appears. 2. **Design principles (applied to every table)** — the conventions every entity inherits, stated once instead of repeated per table. 3. **Entity-relationship diagram** 4. **Entity catalog** — every entity, grouped (see below), with conceptual attribute types. 5. **Design call-out: the timeline as an activity-stream spine** — one section for the one modeling decision that's load-bearing enough to deserve its own explanation. 6. **Transactions & integrity (ACID)** 7. **Role-based access control — the capability matrix** 8. **RLS in one sentence** — the whole security model, compressed to something a reader can hold in their head before the detailed policy section. 9. **Row-Level Security policy design** — the taxonomy (below). 10. **Indexing & performance (conceptual)** 11. **Why [this database] over [the alternative] *for this model*** — a comparative argument, not a feature list. 12. **Scope & forward-compatibility** — what's MVP, what's deferred, and what the shape buys you later. Use this as the spine for a new project's data-model doc, not a fixed page count — a project with no RBAC has nothing to put in section 7, and that's a correct, honest gap, not a section to pad. ## Entity grouping Section 4