Design Hub · Blueprint · a visual flow
Blueprint — idea in, decided plan out
The AI requirements studio · designed-only, backend in flightBlueprint is bring a fuzzy idea, answer four plain questions, and confirm a plan you barely had to write. This is the elicit → decide → RoadWork-write journey, screen by screen: a founder brings a rough thought, answers the interview one question at a time, watches the board fill with numbered decisions that arrive pre-answered, confirms rather than writes, watches it refuse to guess the one fact only she knows, ratifies a fail-closed gate, and sees the plan written into RoadWork — honest-pending until the real write lands. Dr. Mara Okafor, DVM (Riverside Animal Care), brings "Recovery Rounds": recovering patients need follow-up and the clinic keeps dropping people. The class this kills is Blueprint's own — a guessed fact, a fake success, a blank-page re-ask, a half-written plan reaching the handoff.
Entry point ABring your ideaA founder with a fuzzy thought she can't spec — never used an AI agent.
Entry point BResume the studioThe studio remembers the draft, the place, every confirmed decision.
The payoffA decided plan in RoadWorkThe truth for what this should be — the store of record wins.
Every decision state — glyph + word + lightness, never a red/green hue
✓ Confirmed settled
▸ Predicted answered for you
◇ Open question it won't guess
✎ Changed by you
The journey
One clear spine: bring the idea → interview → drafting → confirm the decisions → the open question → ratify → to RoadWork → the store of record. Honest designed-only: the #780 backend contract (persistence · server-side ratify gate · variable-length refuse-to-guess generation · the SO #30-gated RoadWork write) is designed, not built — nothing persists today (the studio state lives in the browser). Return/everyday moments design against that intended contract and say so. No price anywhere. Success renders only on the landed write.
1 Front door
Idea in → decided plan out
landing.html
Reads— (static · the living hero)
Writes—
Statecold · signed-in returns to studio
aiuni.tech/blueprint
Turn a fuzzy idea into a decided, buildable plan.
Bring a rough idea; Blueprint runs the interview, drafts every decision with a predicted answer you mostly just confirm, and once you ratify it writes the plan into RoadWork. For founders · domain experts · PMs who have an idea but can't spec it.
AIU Blueprint decides RoadWork tracks Agent Engine executes
Bring your idea
no price shown — pricing is pulled until full release
"Idea in → decided plan out" read in ~3 seconds, no reading required — the hero shows a fuzzy vet-clinic idea turning into a numbered, decided plan.
A signed-in returning user routes to their studio, not the pitch. The honest-status band states the real grain: in-design · nothing-saved · open-questions-named.
2 The idea
Bring the idea (fail-closed)
#/intake
Reads—
Writesthe draft designed-only (#780 · not built)
Stateempty / <8 char → rejected in place
app.aiuni.tech/blueprint · #/intake
Bring your idea — in your own words.
Your idea (rough is fine)"Recovering patients need follow-up and we keep dropping people. Some kind of… recovery rounds?"
Start the interview
This is the only time the idea is asked for — every downstream surface derives from it and never re-asks. An empty or <8-char idea is rejected in place — a blank blueprint can never start (TC-1).
A single free-text field and plain permission to be rough — no spec-speak, no template.
The interview opens with question 1 visibly about her idea — proof it was heard. Back to studio is always available.
3 Interview
Four plain questions, one at a time
#/interview
Readsthe idea + answers so far
Writesanswers persist (designed) · Back-safe
StateQ1 Back disabled · last → See decisions
app.aiuni.tech/blueprint · #/interview
Who is it for, exactly?
Question 3 of 4
What exists today that you'd build on?
"We tag surgeries in the practice system, and the front desk keeps a whiteboard. Nothing automatic."
Next
One question at a time, the way a sharp product lead would ask — who it's for · what "done well" means · what exists · the one non-negotiable.
Back never loses a shown answer; no question re-asks the idea. No-JS renders all four stacked — pacing is enhancement, never hidden content. The last question swaps Next for See your decisions.
4 Drafting
Reading your answers
#/drafting
Readsintake + interview answers
Writesnumbered decisions (designed generation)
Statereal work · stall → honest error
app.aiuni.tech/blueprint · #/drafting
Reading your answers, drafting each decision.
Blueprint is turning the interview into numbered decisions — and predicting an answer for each from what you actually said. This is real work, not a spinner for show.
When a decision has no honest prediction, it's flagged as an open question, not guessed. Stalls route to the honest error state ("your work is saved") — never an infinite spinner.
The board opens populated — the promise ("drafting each decision") is visibly kept.
Variable-length generation (refuse-to-guess) is the #780 contract's core — designed, not built. The demo fixes nine decisions; the surface renders the real count.
The board opens — confirm, don't write
5 The win
The decisions board
#/decisions
Readsthe drafted decisions · her answers
Writesper-decision state (designed rows)
Statepredicted · confirmed · changed · open
app.aiuni.tech/blueprint · #/decisions
Your decisions — mostly answered. Confirm what looks right.
3 of 9 confirmed
D1What do we call it? Confirmed
Answer Recovery Rounds
D2Who owns the daily list? Predicted
Predicted answer Front-desk team; vets can see it.
Why we predict this: you said the front desk keeps the whiteboard today.
Confirm thisChange
D3What starts a follow-up? Confirmed
Answer A visit tagged surgery / serious diagnosis
Her job has visibly shrunk from writing a spec to confirming one — each card carries the question, a predicted answer, a "why we predict this," and ≥1 alternative.
Every prediction traces to her own words; every decision is addressable by its number (
#/proposal/dN). An empty change never counts; disagreement is a first-class path, not an error.6 Refuse to guess
The open question
#/proposal/d7
Readsthe decision flagged open-question
Writesanswer or carry — either settles it
Statenull predicted answer (mechanically)
app.aiuni.tech/blueprint · #/proposal/d7
D7Where does the visit data come from? Open question
Blueprint won't guess this. This is the fact only you or your vendor knows.
Save my answer Carry it as open
Carrying it makes a "confirm the data source with your vendor" task in the plan — never an invented integration. She can answer it any day later.
The trust guarantee is demonstrated, not claimed — she watches the product decline to invent, on the one decision where inventing would be easy.
An open question is a legitimate settled outcome, never a blocker. The generator emitted it with a null predicted answer — no fabricated value exists anywhere (the refuse-to-guess invariant, mechanically enforced).
7 The gate
Ratify (fail-closed)
#/ratify
Readsthe real settlement state
Writes— (locks on ratify)
Statefenced until all settled · server-side too
app.aiuni.tech/blueprint · #/ratify
Recovery Rounds · the settled plan
Ratifying locks it and writes it into RoadWork for the build. You can still reopen any decision until you do.
6 decisions still need you
D4, D5, D6, D8, D9 to confirm — and D7 is an open question you can carry as-is. Back to the decisions ›
Ratify & send to RoadWork
While anything is unsettled: an honest fence + a back-link, with Ratify disabled. When everything's settled the gate flips: "everything's settled" and Ratify enables.
Forcing the route early shows the fence, never a half-written handoff. The gate is enforced server-side too — the UI's disabled state is UX, the server's refusal is the law.
Ratified — the honest handoff (SO #30-gated write)
8 To RoadWork
The honest write
#/handoff → work.aiuni.tech
Readsthe ratified decisions
Writesthe RoadWork tree (gated · idempotent)
Stateready-to-write → written(real) only
app.aiuni.tech/blueprint · #/handoff
Your plan, as a work-tree
Idea
Recovery Rounds — never drop a recovering patient
from your intake + D2
Initiative
Follow-up program for post-surgery / serious-diagnosis patients
from D3
Feature
Auto-triggered recovery track + day-3 / day-10 schedule
from D3 · D4
Epic
Confirm the visit-data source with your vendor
from D7 · the carried open question — never a fake integration
Ready to write — pending the durable RoadWork write
The write is a gated production write (SO #30 · FOUNDER's to arm). Your screen never says "written" until it is. Re-running is safe — the write is idempotent per blueprint, never a duplicate tree.
The tree is composed from her decisions — every task carries a priority and a source-decision tag; nothing is there by accident. She structures nothing.
Success is the landed write, never an assertion. "Ratified · written to RoadWork" renders only after RoadWork really has it; a failed write is an honest state with one retry — the plan stays decided and safe.
The decided plan lives in the store of record
9 The record
The store of record
#/hub
Readswhat she ratified (byte-honest)
Writes— (read-only truth)
Statebuild drifts → the record wins
app.aiuni.tech/blueprint · #/hub
Recovery Rounds — the truth for what this should be
The decisions
Every decision + its answer + the why.
The requirements
The work-tree — priorities + source tags.
The screens
The UI intent for the build.
The live build
Tracked in RoadWork ↗
If the build and this record disagree, this record wins. Stated on the card, so she knows which way truth flows before she ever needs it.
She can point a colleague at one place and say "this is what we decided" — and it matches what she confirmed, decision for decision.
Weeks in, "why did we scope it to post-surgery check-ins?" → she opens the record, finds the decision by number, reads the answer and the why. Her answer is a link, not a recollection — and word of mouth (the landing URL) is a peer's first touch.
↑ the second idea starts in the studio · showing the decided plan to a peer loops back to a first touch
The rules every screen keeps
Never guess a fact it can't stand behind
A decision needing a fact only the user or a vendor knows is an open question (◇, null predicted answer) — settled by carrying, never by invention. Every predicted decision carries a non-empty why + ≥1 alternative + a source reference.
Fail-closed gates, client AND server
An empty idea never starts a blueprint; an unsettled plan never ratifies; a bypassed disabled button never reaches the handoff — and the server refuses independently of the UI.
Success is the landed write
"Written to RoadWork" renders only after the real, gated write lands; until then the honest "ready to write — pending." A count with no source hides. No fabricated toast, ever.
State-aware always
Every surface reads the real draft/decision state and shows the one dominant action; never a blank-page re-ask, never onboarding to a returning user, never "Resume" into a ratified plan.
Colorblind-safe · one vocabulary · no price
Decision states read by glyph + word + lightness, never a red/green hue (FOUNDER is red/green colorblind). The artifact is a "blueprint", the unit a "decision" (handle = its number). Brand renders AIU. No pricing anywhere.
Drill in