Welcome back, Mara. One blueprint in progress.
A blueprint turns a fuzzy idea into a decided, buildable plan. Pick up where you left off, or start a new one.
No blueprints yet
Nothing here is a placeholder — this studio is genuinely empty until you bring an idea. Start with a rough one; you don't need to know how to build it.
Why this mattersAn empty studio says it is empty. No fake sample projects, no invented counts — the honest zero (design-standards U2).
Tell it your idea. Rough is fine.
Write it the way you'd say it out loud — messy, uncertain, half-formed. Blueprint reads it and starts asking. You never have to know the right words or how to build it.
A few questions. One at a time.
Blueprint asks the way a sharp product lead would — never a form-dump. Answer in a sentence; it listens and moves on.
Knowing whose screen this is decides almost everything else, so it goes first.
The outcome in the owner's own words becomes the measure of success later.
Blueprint would rather plug into what you already have than make you enter things twice.
The non-negotiable becomes a decision the plan is built to protect.
No-JavaScript noteWith scripting off, all four questions and Mara's answers render stacked and readable — the "one at a time" pacing is a progressive enhancement, never a way to hide content.
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 will be flagged as an open question, not guessed.
Couldn't reach the studio
Your idea and every answer are saved — nothing is lost. This is a connection problem on our side, not yours. Try again, or come back to it later.
Every open question, numbered and mostly answered.
Blueprint drafted a decision for each thing your plan needs settled — and predicted an answer for most from your own words. Confirm the ones that look right; change any you want; answer by number. One (D7) it won't guess.
What do we call it?Confirmed: Recovery Rounds Confirmed
Recovery Rounds
- Alt AAftercare Tracker
- Alt BCheck-In List
You confirmed this. Reopen any time before you ratify.
Who owns the daily list?Confirmed: the front-desk team; vets can see it Confirmed
The front-desk team owns the daily list; every vet can see it.
- Alt AEach vet owns their own patients' list
You confirmed this. Reopen any time before you ratify.
What starts a follow-up?Confirmed: a visit tagged surgery or serious diagnosis Confirmed
A visit tagged "surgery" or "serious diagnosis" automatically starts a recovery track — no one has to remember to add it.
- Alt AStaff add each patient manually
- Alt BRules per procedure type
You confirmed this. Reopen any time before you ratify.
The check-in schedule?Predicted: day-3 call + day-10 recheck nudge, adjustable per case Predicted — your call
A day-3 check-in call and a day-10 recheck nudge, adjustable per case.
- Alt AOne fixed schedule for everyone
- Alt BThe vet sets the schedule per patient
Decided.
What does the owner see?Predicted: a plain "what's normal / when to worry / your recheck date" note Predicted — your call
A plain note: what's normal in recovery, when to worry, and your recheck date. No diagnosis, no medical advice.
- Alt AOwners see nothing in v1 (staff-only)
Decided.
The safety line?Predicted: never states a diagnosis or outcome — only "due for a check-in" Predicted — your call
The tool never states a diagnosis, a prognosis, or a medical outcome. It only surfaces "due for a check-in" and shows the vet's own notes. The clinician decides the medicine.
- Alt ATool suggests likely issues to watch
Decided.
Where does the visit data come from?Open question — a fact we won't guess Open question
You want to read visits from your practice-management system instead of typing them twice. Whether that system lets another tool read its data — and how — is a real fact only you or your vendor can confirm. Guessing it would put a made-up capability in your plan. So Blueprint leaves it open, on purpose.
Noted — carried as an open question.
What's in the first version?Predicted: staff list + auto-triggered tracks + the schedule; owner note is v2 Predicted — your call
Version one: the staff list, auto-triggered recovery tracks (D3), and the day-3 / day-10 schedule (D4). The owner-facing note (D5) follows in v2.
- Alt AEverything at once, including the owner note
Decided.
How will you know it works?Predicted: % of recovering patients checked in on time Predicted — your call
One number the clinic can see: the share of recovering patients who got their check-in on time.
- Alt AStaff satisfaction survey
- Alt BOwner reply rate
Decided.
The magic, plainlyYou don't fill in a blank spec. Blueprint predicts each answer from what you actually said, so you mostly confirm — and where it honestly can't predict (D7), it flags an open question instead of guessing. That's the difference from every "requirements template."
One look at the whole plan, then you ratify.
This is everything you settled, in one place. 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 before you can ratify — D4, D5, D6, D8, D9 to confirm, and D7 is an open question you can carry as-is. Back to the decisions.
Honest fenceYou can't ratify an unfinished plan — the button stays off until every decision is settled. Forcing this screen early shows the "still needs you" fence with a way back, never a half-written handoff.
Ratified. Your plan is now tracked work in RoadWork.
Blueprint's job ends at "decided." The moment you ratified, the plan was written into RoadWork as a work-tree the agents can build — and from here RoadWork owns it.
Every task traces backEach task cites the decision it came from (the small D-tag on the right). Nothing in the plan is here by accident — and the one thing you didn't know (D7) is a task to confirm, never an invented capability.
Your plan's source of truth, kept for good.
The Design Hub holds what Recovery Rounds should look like and what each part is supposed to do. If the build and this ever disagree, this wins. Come back any time — it's yours.
One truth, not twoThe store of record is the truth for UI + requirements. The build reads from it; if they ever drift, the store wins and the build gets corrected. That's what keeps a plan from quietly rotting after it's decided.