- OObjective
- The checkout shows a total. Prices can change between loading the page and paying.
- NNeeds
- Your decision: where is the total worked out? (a) on the page · (b) on the server. My pick: (b).
- HHow
- (b) asks the server once more, at the moment of paying.
- TTrajectory
- (a) is quicker to build, and can charge a stale total. (b) becomes a decision record every later build cites.
01 / 07 · the principle
Rigour, not vibes.
Work that is long lasting, has general consensus, and is easy to maintain: this needs rigour.
- Every surprise in a build is an expectation nobody wrote down.
- Rigour in the specs: functional, technical and visual.
- Written down, agreed by all, built to a t.
WatchOne request, built two ways. Watch where you get to decide.
WatchOne request, built two ways. Watch where you get to decide.
Vibe coding
- a prompt
- →
- the agent runs
- →
- close enough? you
you decide once, after it is built
With rigour
- Specified you
- →
- Agreed you
- →
- Met a check
- →
- as agreed ✓
you decide early, on paper, while a change is still cheap
Same agent. Different expectations.
you marks every point where the decision is yours. It comes back on the slides that follow.
02 / 07 · your judgment
The thinking stays yours.
The agent does the legwork. Your experience makes the calls, and they hold.
- When the agent needs you, it asks in four parts: Objective, Needs, How, Trajectory.
- Before anything that cannot be undone, it stops: the options, its pick, the risk.
- Your answer is written down once. Every later session builds on it.
ImagineThe agent meets a choice that is yours to make. Watch how it asks.
ImagineThe agent meets a choice that is yours to make. Watch how it asks.
ADR-007 · Server-side totalsyour answer, written down: it comes back on slide 03
Where it stops to ask, in the same four parts
ONHT is the frame behind te;lt. There it helps you think a problem through. Here the agent uses it to ask.
03 / 07 · specified
Write it down first.
What it must do, how it works, how it looks: the functional, technical and visual specs.
- Every requirement numbered, every one paired with a check.
- Each big decision keeps its reason. Six months on, nobody has to guess why.
- Nobody approves a description. They approve the drawing.
ImagineYou ask for "a clear checkout". Once the specs have been created and drawn, they are ready for you to review, approve or send back.
ImagineYou ask for "a clear checkout". Once the specs have been created and drawn, they are ready for you to review, approve or send back.
1It is written as numbered lines. A gap is flagged, not guessed at. 2You close the gap. The line gets a check that can prove it. 3Each technical line points back to the line it serves. 4Your decision from slide 02 is kept, with its reason. 5The pages are drawn, each with an id. ✓Nothing is left to guess. It is ready for you to review: approve it, or send it back.
Checkout
functional requirements · the Garden shop
- FS-010Show the basket with totals✓
- FS-011Show the delivery day✓
- FS-012One clear action to payopen✓
- check · the page has exactly one primary button
✓ ids · checks · nothing left opena placeholder is flagged
Checkout
technical requirements
- TS-004Prices from the catalogue APImeets FS-010
- TS-005Totals on the server · ADR-007meets FS-010
- TS-006Card payment via the providermeets FS-012
Server-side totals
the decision, and why
- DECISION
- Compute totals on the server.
- WHY
- One source for what is charged.
- DECIDED
- by you, on slide 02's ask
Screenflow
- Basketscreen-basket-1
- →
- 1Checkoutscreen-checkout-1
- →
- Confirmationscreen-confirm-1
from slide 02your answer is now ADR-007 · each technical line points back to the requirement it serves
the toola mis-named spec is refused as it is written · a copy is kept before every edit · a lint flags a bare placeholder when it is run · the rest is the method, and you are the check
04 / 07 · agreed
Agree it first.
Everyone who relies on it sees the outcome before a line is built.
- The builder, the lead and the person who signs off read the same pages.
- A wrong turn on paper is an edit. In code it is a rebuild.
- Consensus is written down, not assumed.
ImagineBefore anything is built, you review the specs. Here, the drawing. Watch a review that ends with your approval.
ImagineBefore anything is built, you review the specs. Here, the drawing. Watch a review that ends with your approval.
Storyboard
from slide 03✓ ApprovedIn reviewscreen-checkout-1- ✓Basket
- 2Checkout
- 3Confirmation

Your order is nearly there.
One plant, one pot, delivery on Thursday.
Fiddle-leaf fig60 cm£38
- Terracotta pot24 cm£14
- DeliveryThursday£6
Total£58
Secure paymentFree returns
- ✓ headline
- ✓ basket and total
- ↩ Pay button · sent back: two primary buttons, FS-012 asks for one✓ Pay button · redrawn, one action
you one drawing was sent back before anything was approved
approvals.jsonl +1 line screen-checkout-1 · approved · operator · 2026-10-09 the tool: this approval belongs to the page as it was · change the page, and it has to be approved again
05 / 07 · met
Built to a t.
The agent builds to the approved set, not to taste, and proves it.
- The build cites the ids it came from.
- A phase is done when its check passes, never because someone said so.
- Close enough is not done.
ImagineEverything is agreed, and the agent builds. Watch what guards the work, then the plan: what is done, what is left, and what needs you.
ImagineEverything is agreed, and the agent builds. Watch what guards the work, then the plan: what is done, what is left, and what needs you.
from slides 03 – 04the ids written, drawn and approved before
the toolthe checks you map to a file run after every edit, and the result lands in the same turn · a failing check before a commit blocks the commit
- Running
- Numbers
- Plan
- Workbench 1
- Envisionthe brief, four questions answereddone · verified
- Designflow · screenflow · storyboarddone · verified
- Buildto the approved storyboarddone · verified
- Testthe checks, runnow · 1 of 5 checks
- Reviewread by someone who did not build itlater
- Deployreleasedlater
- Verifychecked where it runslater
Needs you: one document is waiting for your approval in the Workbench.
an example plan, on the starter ladder · the tab says so when there is no plan yet
when the session ends: handover · next session · lessons · /dr-close · written, then verified on disk · the next session opens on it
06 / 07 · kept true
Change the spec first.
Months later, the documents still say what was built, how and why.
- A change starts in the spec, not in the code.
- The old version is kept. The new one is agreed again.
- Then the agent rebuilds from it, not from a guess.
ImagineSix months on, you want to add a gift message to your shop. Watch where the change starts.
ImagineSix months on, you want to add a gift message to your shop. Watch where the change starts.
·Today: every document is at v1.0.0, and approved. 1The request arrives. Nothing is coded yet. 2First, the documents as they stand are kept. 3Then each document changes. It moves to v1.1.0, and it is no longer approved. 4The change is drawn on the storyboard, where you can see it. 5You review the new version, and approve it. 6Now the whole set is at v1.1.0, and approved again. ✓Only then does the agent rebuild, from the new documents. The code changes last.
- Change requestAdd a gift message
- FSDv1.0.0v1.1.0 · FS-013✓ approvednot approved✓ approved
- TSDv1.0.0v1.1.0 · TS-007✓ approvednot approved✓ approved
- Screenflowv1.0.0v1.1.0✓ approvednot approved✓ approved
- Storyboardv1.0.0v1.1.0✓ approvednot approved✓ approved
1CHECKOUTStoryboard v1.0.0 · screen-checkout-1Storyboard v1.1.0 · screen-checkout-1 · FS-013✓ ApprovedNot approved · changed✓ Approved again · by you
- ✓Basket
- 2Checkout
- 3Confirmation

Your order is nearly there.
One plant, one pot, delivery on Thursday.
Fiddle-leaf fig60 cm£38
- Terracotta pot24 cm£14
- DeliveryThursday£6
Total£58
Secure paymentFree returns
_archive · what was there, kept before the edit
07 / 07 · built to last
Built to last.
Not a quick, throwaway build. Well made, then maintained meticulously.
- For a quick prototype or a one-chat job, skip it. Vibe coding is fine there.
- It takes longer up front, and it costs less over time.
- Made for
- people who know what good looks like, and want to review the work as it goes
- You need
- Claude Code · Node.js 23.6 or newer · a terminal
- Not for
- prompt and walk away: it asks for your judgment at every step that matters · who it is for
AskHow much of this does your work need?
AskHow much of this does your work need?
As much as the work needs
- ✕A throwaway prototype, a one-chat jobskip it · vibe coding is fine, and the set-up costs more than it saves
- ✓Everyday work like in slides 02 – 06the default: your files guarded · careless moves stopped · asked when a decision is yours · the Runway
- ✓Substantial worka short plan you confirm first · the architecture and a security walk before the first build · how it will be checked, said before it is built
- ✓High stakessign-in · payments · personal data · a destructive migration: more stops, more pushback, a stricter bar for done
- ✓More than one sessionthe orchestration profile, off by default: Builder · Gatekeeper · Advisor, one shared ledger
yoursdev-rigour-min sends nothing · what it reads and records stays on your machine · open source, Apache-2.0 · no dependencies · the same script installs it, updates it and removes it
Quiet by default. More when the stakes rise, or when one session is not enough · the default, high stakes, and the team profile