← Back to slide 05Repository →

Read more · slide 05 / 07 · met · running

See it running.

The Runway is a local view of the whole project, in your browser: the plan, what needs your approval, what is running and what it costs. When one session is not enough, it shows a small team of roles passing the work along one ledger.

1 Specified2 Agreed3 Met

The plan: what is going on, and what is next

The Plan tab shows the phases of the work: which are done, which is running, which comes next. A phase that can be read from the work, such as built or tested, is read from git and the checks. A phase someone declares done counts only once a second person has checked it, with evidence. When something needs you, the plan says so.

127.0.0.1:7379/runwayRefresh
  • Running
  • Numbers
  • Plan
  • Workbench 1
  1. Envisionthe brief, four questions answereddone · verified
  2. Designflow · screenflow · storyboarddone · verified
  3. Buildto the approved storyboarddone · verified
  4. Testthe checks, runnow · 1 of 5 checks
  5. Reviewread by someone who did not build itlater
  6. Deployreleasedlater
  7. Verifychecked where it runslater

Needs you: one document is waiting for your approval in the Workbench.

an example plan, on the starter ladder · a tab with nothing to show says so: the plan stays honestly empty until there is one

The Workbench: approve it before it is built

The Workbench lists every governed document, grouped by kind: specs, decision records and the visual chain. For a storyboard it shows how many elements there are to review, and where it stands: pending, approved (with any element excluded), or not approved. Open one and it shows the frame with its design in view, element by element. The person who signs off approves it there, in the browser, on the machine where the Runway runs, and the list updates from the same record. Every approved frame carries an id the build cites, so the agent builds to the drawing, not to taste.

127.0.0.1:7379/runwayRefresh
  • Running
  • Numbers
  • Plan
  • Workbench

Approval Workbench the visual chain · status read from approvals.jsonl

Governed storyboardElementsStateOpen
garden-checkout v1.1.05 reviewableApprovedPendingOpen →
garden-account v1.0.07 reviewableApproved · 1 excludedOpen →
garden-plant-care v0.3.04 reviewableNot approvedOpen →

‹ All storyboards · garden-checkout v1.1.0 · screen-checkout-1

Garden 2
  1. ✓Basket
  2. 2Checkout
  3. 3Confirmation
A fiddle-leaf fig with large glossy green leaves, in a terracotta pot

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

© GardenDelivery · Returns · Privacy

screen-checkout-1 · 5 elements

  • ✓hero the headline and the one action
  • ✓cta one button, the only primary
  • ✓basket three lines, the total at the end
  • ✓cta-motion lifts 2 px on hover, 120 ms
  • ✓footer one line, no more
✓ ApprovedApprove storyboard by you, on this machine

approvals.jsonl +1 line garden-checkout v1.1.0 · approved · operator

the Workbench lists every governed document; this view is the visual chain · a storyboard needs its screenflow beside it before it can be approved · one write door: approve, by you, on this machine, appends to one file · the names and counts are examples

Running and Numbers: what is running, and what it costs

Running lists the sessions at work. Numbers adds up each session's status line into context used and cost, across every session on the machine, with the 5-hour and 7-day limit windows alongside. Useful when you need it; the plan and the Workbench are where the decisions are.

127.0.0.1:7379/runwayRefresh
  • Running
  • Numbers
  • Plan
  • Workbench
sessioncontext
garden-build-02391k / 950k
invoice-fix142k / 950k
notes-design-01256k / 950k
today, all sessions$ 11.80

[Opus 4.8 H] Ctx: 41% 391k/950k $4.12 | 5h: 34% (-2h41m) | 7d: 12% (-5d06h) | [>DRM<]

the status line in each session feeds the Numbers tab · example figures

Orchestration: a small team, when one session is not enough

Three roles, each in its own window: a Builder, a Gatekeeper and an Advisor. The ledger in your repository is the record: tagged, git-stamped rows. In the simple mode you carry each line from one window to the next, and a role reads the last row before it acts. Nothing polls, and nothing runs in the background waiting. A fuller mode adds a Supervisor and a Registrar.

BuilderGatekeeperAdvisor
Builder → Gatekeeper · phase 1 ready for its check · stamped with the commit Gatekeeper → Builder · checks pass, phase 1 done · stamped Advisor → Builder · next: deliver, the handover first · stamped Builder · reads the last row, starts the handover

one shared ledger · read at step boundaries · nothing polls

The close: the next session starts where this one stopped

At the end of a session, /dr-close writes three files: a handover that says where things stand, a prompt for the next session, and the lessons learnt. They are written in one pass and then checked on disk, so the close reports what is there, not what was intended. Work that is not yet committed is named: you commit it, or you say in one sentence that it can be thrown away. The handover also carries a short reflection through the four lenses, and the session's transcript is saved beside it.

When the session ends

HANDOVERwhere things stand NEXT SESSIONwhat to do first LESSONSwhat went wrong, written once

/dr-close · written, then verified on disk · the next session opens on it

Carries forward: the build and the plan on slide 05, and the approval from slide 04, which the Workbench records.