Stage 6 of 6 · The second proof · on the bench
D3: the rung after
An hour after the paper, a different kind of proof: not what you know, but how you work when a week is deliberately hard. D3 was engineered to be small, one thickness on the skeleton, chosen in the studio and landed early in the week, so that today it asks only for a demonstration you have already run. If that is your situation, this page is a victory lap with paperwork; if it is not, the honest-demo rule from Week 12 still applies, and it still earns.
The mode switch
The exam is convergent work: alone, silent, closed, producing fixed answers. The studio is the opposite: paired, talking, open, producing a running system. Switching between them in minutes is a real skill with a simple protocol: use the reset break fully (stand, leave the room, eat something, say nothing about the paper), and start the bench half with the pair's smallest ritual, the stand-up, because its three mechanical questions (done, next, blocked) restart the collaborative mode the way a key starts an engine. What not to do in the break is relitigate the exam; the paper is submitted, the marks are fixed, and the only thing post-mortems can still affect is the demonstration you are about to give.
The demonstration
The shape is Week 12's, unchanged and now familiar: cause, travel, name, three minutes. What is new is what the marker is looking behind the demo for, per the milestone's three faces: method under pressure. Concretely, the demo should let you say three sentences that D2 could not: "this is the rung we chose in the studio, sized for this week"; "here are the old rungs, still green behind it", shown by re-running the D2 skeleton path; and "here is the verification table's first dated green". A tiny rung fully landed with nothing broken behind it is the entire assignment; the risk table's Friday-feature row describes the only way to fail it from a working position.
If the week won the fight
Weeks collide with life, and the half-width week is the most collision-prone of the term. If the rung is not landed, Week 12's honest-demo rule is still the best available move: demonstrate the skeleton still walking, name what the rung was, where it stands, and the diagnosis if something broke, with half-split evidence. Method shown over a partial beats silence over a promise, at D3 exactly as at D2; and tell the teacher today, because raising it early is itself the method being graded.
The evidence, by end of day
- The rung, tagged:
git tag d3-rung, pushed, from a main that walks. - The regression check, recorded: the journal line stating which old rungs were re-run today and what they showed.
- The table's first greens: the requirement rows this rung satisfies, dated today, per the format.
- The D3 document per the brief, in
docs/, beside its predecessors.
Where the project stands tonight
Before leaving, the pair spends the Week 12 ten minutes one more time: the rung list re-ranked for D4, which asks for breadth, the high-value rungs, the table filling with green, with the milestone's faces open while you rank. The freeze that protects D5 starts when D4's last rung lands; plan its date now, while the calendar is in your hands.
Exit checklist
Next week
Week 14 · Dec 7
D4 build week: the table turns green
15 %, the project's biggest single grade: the build week with a clear run, the studio rhythm back, the high-value rungs landing and the verification table turning green.
Week 15 · Thu Dec 10
D5: the public demonstration
The frozen system, rehearsed twice, performed once: cause the disturbance, let the dashboard narrate, answer anything. The course ends the way it was built, live.