06 — The screens
Summary
Dashboard first — the page shows what it can already say before it asks for anything, the exact inversion of v1's reading-first order. Each shipped screen with its job and its fixed wording: the chokepoint sentence, “not established either way” for untouched facts, “changes nothing in your current case” for a control that does nothing here. Five rendering rules inherited from the estate's mockup exercise: no page-level verdict, state never rides on colour alone, an absent computation renders as absent, situation copy comes from the model, wide content scrolls in its own container. The v3 screens are specified for the tabletop before they are built: the level-one landing, the three-sets dashboard, the share view, and the run gallery whose job is the working method rather than an advertisement.
Key concepts
- The order is the argument — v1 made the visitor pay before seeing the instrument work
- Strings are design — a renderer that paraphrases them in a mockup will paraphrase them in the product
- The run gallery — abandoned runs, the change made, and the run that then succeeded
Key ideas
- Wherever a summary number would go, the chokepoint sentence goes instead — a noun the visitor can act on.
- A control that closes nothing must say so, or the row reads as broken rather than honest.
- The screen this tool will never have is a score.