2026-10-04-the-console-is-a-flow-of-the-web-surface

Decision

One web surface. The console's thirteen screens are the flow admin, in the alphabetical slot between about and demo.

Why

The product has three front ends: an Expo app, a marketing site and a super-admin console. The style guide allows two surfaces, mobile and web. The site and the console are separate Next.js apps on separate hosts with nothing linking them.

Options weighed:

• A third surface (designs/admin/) — not allowed by the guide, and the surface toggle in the shared bar has two halves.
• One web surface, console as a flow — designs/web/admin/*.

Impact

• routes.js has one start node, Home. No site page links to the console, so the chart cannot rank the console's screens: they stack in the last column, with their own edges drawn.
• check-designs.py reads apps/website for a web surface and cannot see apps/admin. Console screens carry route: null and name their file in an app field, so the routes, app-flow and copy checks do not cover them.
• If the console grows, the honest fix is in the shared shell — more than one start node, or a third surface — not in this repo.

Status

Active

Sources

• ~/git/personal/STYLE-GUIDE.md §1, §6
• .context/designs/web/routes.js