ci / check (push) Successful in 50s
- replace default Onyx surfaces with paper/ink, signal orange and Archivo - make /plan answer peak, staff-hours, cost vs flat and coverage above the fold - add the weekly shift board, shared plan helpers and a pulse line - rebuild /live as a phone-first dark board and /stage as a full-bleed projector - label the real 14-20 Nov window; remove 'next week' claims - keep Onyx components, SSR, live scenario updates and accessible states
43 lines
3.2 KiB
Markdown
43 lines
3.2 KiB
Markdown
---
|
||
version: 1
|
||
slug: "plan"
|
||
primary_target: "plan"
|
||
related_targets: ["/", "/live", "/stage"]
|
||
---
|
||
|
||
# Surface brief — decision, stage, phone
|
||
|
||
## Scope
|
||
|
||
Primary: `/plan` (Operate). Related: `/` (Persuade), `/live` and `/stage` (Experience), with supporting `/forecast`, `/simulate`, `/about`, `/control` to follow in the finish pass.
|
||
|
||
## Audience and job
|
||
|
||
A Heilbronn duty manager needs the coming week's staffing decision: who works, when, what it costs, and what the trade-off is. A hackathon audience needs the same decision at ten metres on a projector, then in their hand on a phone. The presenter needs to change one scenario and have every surface follow honestly.
|
||
|
||
## Success
|
||
|
||
- `/plan` answers what to do above the fold: peak shift, staff count, staff-hours, cost vs flat, coverage.
|
||
- `/live` answers on a 390×844 phone above the fold: shift, staff count, one-line reason, freshness.
|
||
- `/stage` is readable at 10 m without app chrome.
|
||
- `/` sets up the story in one screen with the live plan as proof.
|
||
- Measured, modelled and assumed stay visibly distinct; the real 14–20 Nov window is labelled.
|
||
|
||
## Constraints
|
||
|
||
Live API data only; no fabricated numbers. Preserve routes, API contracts, Onyx components, SSR, accessibility, reduced motion and the existing build/tests. The paper brief's 210 h / €3,360 is stale; the demo baseline is the live sunny-saturday-market plan (5 peak, 172 staff-hours, €2,752 vs €5,600 flat, 100% coverage).
|
||
|
||
## Direction contract
|
||
|
||
THESIS: A shift board, not a dashboard. The week's footfall becomes a physical timetable with an orange peak block; the category's metric-card hero and admin shell are refused.
|
||
|
||
OWN-WORLD: Cool paper `#F4EFE6`, ink `#16130F`, signal orange `#E84100` for the peak (text `#B63A00` on paper), board green `#2E6B4F` for coverage. Archivo variable: condensed 78% display, tabular numerals, heavy rules, zero radius, no shadows. `/stage` and `/live` invert to ink `#0E100E` with paper type and bright orange.
|
||
|
||
STORY: The manager reads "Five on Saturday, 10:00–14:00", sees the week board, and understands 172 staff-hours cost €2,752 against €5,600 flat with 100% coverage. They approve or export. The judge sees the same plan on stage and phone; a scenario change redraws the pulse and the blocks.
|
||
|
||
FIRST VIEWPORT: `/plan` — h1 "Five on Saturday." with shift time and a receipt of staff-hours/cost/coverage on the left, a full-width seven-day shift board with the orange peak on the right/below, and Approve/Export actions. `/` — headline "Saturday needs five." beside the live board. `/live` — giant 5, Saturday 14 Nov, 10:00–14:00, one-line peak-forecast reason, freshness. `/stage` — full-bleed dark board: 5 staff, day/time, week board, cost line, QR.
|
||
|
||
FORM: Shift board / timetable. The user pinned the world and its first-surface experience; no roll was needed. `seed: none (pinned)` — "A — Shift board. Full replacement. Paper/ink ground, signal orange for the peak, heavy timetable rules, tabular numerals, physical time blocks. /stage inverts to a dark board."
|
||
|
||
FINISH: unreviewed and undocumented is unfinished; this build ends with the finish review, the verdict, DESIGN.md, and every shipping raster carrying its provenance.
|