Engineering documentation

This area is for the team that builds Trovensa. It holds what the code must agree on and why it was decided that way; the platform area holds how the product is meant to be used.

• Specifications: the contract summary condenses PRODUCT-CONTRACT.md (taxonomy, 72 permissions, 117 designed routes, DTO families, ownership) and the spec schema is the five-part skeleton a specification version follows, one block per stage id.
• Design: Tokens lists every light, dark and product token with its hex, Shell describes the rail, the panel, the topbar, the breakpoints and the two cookies, and Screenshots embeds the reference frames captured from the web app.
• Decisions: the decision log lists the ten ADRs written on 2026-09-13, each with the five fixed headings.
• Roadmap: what is designed today and what the first release needs, without dates.
• Runbooks: First release summarises the operator runbook kept in the infra repository.

Every reference and specification page ends with a Source: line naming the repository files that were read while writing it; counts are recounted on publish day.