Read more · slide 04 / 07 · agreed
Agree it first.
Consensus is not a meeting that went well. It is a set of pages everyone read, and a record that the person responsible approved them before the build began.
Who reads the same pages
- You run an agent. You build from the pages, and you can point to the line you built.
- You lead a small team. You see the work drawn and approved before it is built, so the direction stays yours.
- You sign off. You do not need a terminal. You see the outcome as a drawing, in a browser, and approve what you see. The approval is made on the machine where the Runway runs. From another device on the same network the pages can be read, not approved.
This works for one person as well as a team. Working alone, the pages are how you check your own wrong turn before an agent builds it.
- ✓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
Why before the build
A wrong turn costs a little at each step it survives. On paper it is an edit. In a storyboard it is a redraw. In code it is a rebuild, and after release it is a change request. Agreeing first moves the disagreement to where it is cheapest.
Saying no is part of it
An approval that could never have been a refusal is a rubber stamp. On the slide, the first drawing of the Pay button is sent back: it showed two primary buttons, and FS-012 asks for one clear action. The drawing changes, and only then is the frame approved. In the Workbench an element can also be left out of an approval. The record shows that it was left out. The reason is yours to note, for example on the bug board.
How an approval is recorded
The Workbench, part of the local Runway, opens any governed document: a spec clause, a decision record read whole, or a storyboard frame with its design in view. Approve it, and one line is added to one file.
approvals.jsonl +1 line screen-checkout-1 · approved · operator · 2026-10-09
It is done by you, on your own machine. It is the only thing the Runway writes. Everything else it does is read-only.
An approval belongs to the page as it was
The record keeps a fingerprint of the page that was approved. Change the page afterwards and it reads as not approved, with the reason: edited since approval. A new version does not inherit the old approval, and the old version stays approved until the new one is.
Each line in the file is chained to the one before it, and the approver is always you, never an agent.
Carries forward: the screen screen-checkout-1 from the screenflow on slide 03. The build on slide 05 is built to this approved frame.