Foundation — Prototype references¶
Scope note: Foundation is system work, not feature work. Most of its tickets have no prototype because they ship plumbing (axios, interceptors, error parser, OTel, CI) that has no visible surface. The handful that do have a visual deliverable reference prototypes from ux-tests/prototypes/action-flow-prototypes/.
| Page / surface | Owner ticket (milestone) | Prototype |
|---|---|---|
| Dashboard placeholder | M2 — AppShell + Sidebar + Header | ux-tests/prototypes/action-flow-prototypes/01-home.html — chrome only; the placeholder content itself is intentionally bare |
| AppShell — sidebar, header, content area | M2 — AppShell + Sidebar + Header | ux-tests/prototypes/action-flow-prototypes/sidebar-template.txt — the authoritative spec for the fixed left sidebar, grouped non-collapsable navigation, user-card footer. Also referenced indirectly by every page prototype because they all share the chrome. |
| Forbidden screen | M2 — AppShell + Sidebar + Header | — |
Login + account screens are not foundation surfaces — they ship with identity's first ticket against the real auth contract. The pre-existing vibe-coded
login.tsxis deleted in M0.
How to read these references¶
sidebar-template.txt is a reusable CSS+HTML fragment that every page prototype pulls in. Foundation's M2 ticket implements its semantics in React + Tailwind, not literally — the visual contract (260px width, fixed left, grouped sections with uppercase headers, user card in footer) is what the implementation must preserve. The Polish copy in the template (Główne, Dane, Magazyn, Jakość) is not the canonical grouping — those names came from the pre-realignment module structure. The new grouping is by the 7 BE modules per routes.md § Route registry convention.
Tickets with no prototype¶
Everything in M0, M1 (primitives), M3 (API/data layer), M4 (forms wiring — pure plumbing, no specific page), M5 (observability, testing, CI). These tickets either implement non-visual infrastructure or build the design-system primitives that later pages compose — the relevant visual spec is ../../design-system.md, not a prototype HTML.