The whole path, at a glance.
Blueprint turns a fuzzy idea into a decided, buildable plan. Below is the entire journey as a picture — idea in, decided plan out. Every step is clickable: open the real screen, its diagram, its requirements, or its test cases.
The product page: the benefit, the audiences, and the transformation in three seconds.
Write it rough, in your own words. No spec-speak. Fail-closed on an empty idea.
A few plain questions, one at a time — the way a sharp product lead would ask.
Every open question, numbered and mostly pre-answered. Confirm by ID; one is kept honestly open.
One look at the whole plan, then lock it. You can't ratify a half-finished plan (honest gate).
Ratifying writes the plan into RoadWork as a work-tree — Idea to Task — each task traced to its decision.
The truth for what it should look like and do. If the build ever drifts, this wins.
How to read this
Start at 0 · Understand it and move left to right. Each tile opens the real, clickable screen; the small gilt Spec links jump to that step's requirements and test cases in the build packet. A person sees the whole shape first, then drills down only where they need to.
The working studio
The functional, clickable app — every screen and state, idea through store-of-record. Interactions really work.
.governance/prototypes/goal1-aiu-blueprint/mock.html Open it Prototype · landingThe product page
The marketing surface: benefit, audiences, the "mostly just confirm" differentiator, and the platform loop.
.governance/prototypes/goal1-aiu-blueprint/landing.html Open it DiagramsActivity-flow + workflow
The two required diagrams — who does what, and the states a blueprint moves through — as Mermaid source with an ASCII fallback.
…/aiu-blueprint/GOAL1-FLOWS-AND-REQUIREMENTS-2026-07-10.md § Diagrams Open the doc RequirementsThe build packet
WHAT · THE LOGIC · DATA · WHERE · PROVE IT · DONE MEANS — everything a cold builder needs, per the standard.
…/aiu-blueprint/GOAL1-FLOWS-AND-REQUIREMENTS-2026-07-10.md Open the doc Test casesHow it's graded
Numbered TC-1…TC-14, each measurable · gradeable · cheat-resistant · right-sized. No self-reported pass.
…/aiu-blueprint/GOAL1-FLOWS-AND-REQUIREMENTS-2026-07-10.md § Test cases Open the doc Test cases (Gherkin)Test cases (Gherkin) →
Runnable Gherkin scenarios traced one-to-one to the use-case register, plus the load-bearing invariants (never-invents · fail-closed ratify · lands-in-RoadWork). Verifier-run — no self-reported pass.
…/aiu-blueprint/GOAL1-FLOWS-AND-REQUIREMENTS-2026-07-10.md § Gherkin test cases Open the doc Open questionsWhat isn't settled yet
The honest list of everything the source is silent on — flagged, never invented. Read this before building.
…/aiu-blueprint/GOAL1-FLOWS-AND-REQUIREMENTS-2026-07-10.md § Open questions Open the docGrounded, not invented
Every screen traces to the product proposal §10 (elicit → numbered decisions → predicted-answer proposals → ratify → written to RoadWork; Design Hub = store of record). The customer world — Dr. Mara's clinic and her "Recovery Rounds" idea — is the demo, the way the homepage uses mock client sites. Anything the source is silent on is in Open questions, never guessed.