Appearance
ADR 0008: Planned screens driven by a registry
- Status: Accepted
- Date: 2026-11-18
- Spec version: 1.0.0
Context
The initial UI must show every role's space and make the shape of the product visible before the features exist, without fake data and without a hand-written route and sidebar entry per future screen.
Decision
apps/web/src/lib/spaces.ts is a registry of spaces, sections, dashboard panels and public pages. It drives the sidebar, the space home pages, and one generic route (_app/$space/$section) that renders a planned screen: it says plainly that the feature is not built, what it will do (in the spec's words), which build step delivers it, and links to the spec chapter. Public token pages work the same way (p/$page.$token).
To build a section: add a dedicated route file (static routes beat $section), and trim its registry entry.
Consequences
- Nothing looks falsely empty or falsely working. Panels show "Not built yet", never invented numbers.
- Navigation, role visibility and spec links are reviewed in one file.
- The registry is a temporary scaffold: when every section has a route, navigation metadata (label, icon, roles) stays but
will/milestoneare deleted.
Revisit when
All sections are built, or navigation needs to be data-driven per user (permissions that differ within a role).