Every named build across the four arcs, what is in flight this hour, the order things land, and the four places your hand steers it.
Composed from today’s receipts (board rows 412–427) · annotate anything · notes sync to the desk live
DONE means four things, and nothing else: all 58 editability rows verified or honestly walled · the sealed 12-ask exam passes clean · a nightly rehearsal proves it stays true with nobody watching · and everything ships within two runs, not after endless retries. Today: 6 of 58 verified on the morning ledger, plus 6 more flipped this afternoon by the new verification machine — and that machine is now running, not planned.
The four arcs — every named build, in plain words
BIRTH — a web address becomes a living site (bay-1).
The pipeline itself works. What remains is making its trust floor unbreakable, then running births on a cadence.
The floor's hardest piece — the stamp proving "this edit's value came from this ruling" — has now been torn down twice by our own attack dog, which is the system working: the second teardown found a check that could never fail and a replay that silently reverted newer work. The cure frame is ruled and the third build is underway with its attack plan agreed before the build.
↘ go deeper — the builds by name
F3 rebuild-2 (in flight): minted-act identity — a nonce created at plan time + a ledger row, threaded plan→stamp→write→receipt; content-derived keys are the ruled-dead frame (ask-273). Pre-agreed falsifier: dead-conjunct driven both ways, the T1/T2/T3 replay as a permanent red fixture, normalisation attack, distinct-acts-distinct-identities arm. F5 floor cures: built, on origin (bay/f5-own-origin + f5-residual), PRs open when the train moves. R6/R7 birth rounds: the birth cadence loop, next after F3. R5 arena check: the exam gate for a fresh birth on the Mac arena; queues with birth-on-Mac.
FACTORY — a born site becomes certified, in under thirty minutes (bay-2).
The discipline being proven row by row: exactly one piece of machinery may author each record, so nothing can quietly rewrite the site's facts. Today its courts caught two classes the test fixtures had been hiding — including a real one: reordering sections moves the page's bytes while the fact-map keeps old positions, silently breaking the map. Ruled today: any edit that moves bytes must end by re-running the official stamper. That single build makes reorder-class edits safe on real pages.
↘ go deeper — the builds by name
Wave-2 rows 34/36/52 (in flight): real verdict legs on their own doors after the discovery that the earlier reports carried no rulings at all. Row 34 re-courting with the anchor finding named on its face. Rows 46/49/57 closes: 46 needs one judged round (round 9, their door — the desk's round 8 judged a broken courtroom instead); 57's court passed everything except 3 files missing from its own machinery manifest — small named cure; 49 closes on its wave. Byte-movers re-stamp unit (chartered today, ask-277): transaction-layer wire calling stampOccurrence/buildPageLayers after any byte-moving edit; reorder is consumer #1. Spine-reconciliation guard: every byte accounted for against genesis-or-recorded; replaces the retired evadable lint. Approved, queued. Driver mechanical fixes (row-21 grammar, class targeting): behind the outcome-words gate, which half-lifted today (spec v1.1 banked; A5 added).
MINUTE — a teammate speaks, the site changes, under a minute (bay-3).
The 60-wish blind exam graded 56 of 60 honest outcomes with the front door dropping zero reasonable asks. Now every "claimed" row is being independently verified — and that campaign started TODAY and is fast: its first sitting flipped 6 of 8 rows to VERIFIED with two honest findings, one of which exposed a real gap in my own grading spec (ruled and amended the same hour: a door that rewrites records it didn't need to touch must say so).
↘ go deeper — the builds by name
Campaign 1 (batch-2 rows 9–31 riding now): isolated-room re-drives; word recomputed from receipts (spec v1.1 + A5); independent reader samples; two-runs-max then named finding. Door cures chartered: recordChurn disclosure + stable serialization (from F-C1-07); span-level longer-text guard (F-C1-03a, live-copy corruption class, 4th sighting — altitude caveat attached); two report-surface honesty fixes (03b, 05). Campaign 2: the 27-row tail under triage — probe-now majority expected to verify fast; build-required rows (favicon/forms family) become named Lane-A builds; boundary questions route to Robert. Genie cures → production: ask-on-ambiguity + closure budget (both falsifier-proven) fold into the production genie — desk-owed, post-train.
TRUNK — the machine cannot lie about itself (bay-4). Tonight's load-bearing stop.
The release gate froze the repo including its own cure; your two pastes this morning broke the dam, and trunk's own build then produced the evidence the gate demands — verified, binding, real. One last coupling appeared an hour ago: the gate machinery's own unit tests read the LIVE rulebook with a frozen clock, so the genuine fix reads as "movement from the future." The cure (tests own their fixture copy) is being built right now by the machinery's owner. When it lands, the whole parked train merges itself with no further human word.↘ go deeper — the train, in order
Fixture-decoupling cure (ask-276, in flight, lands ON PR 2039) → 2039 floor paperwork automerges (citation already swapped to the minted trunk record runId 32490860569) → wiring/WV2 fold PR (+8 census rows) → F5 PRs → tamper forward-merge → ONE pre-drafted delta court → tamper alarm (PR 2037) lands. All pre-checked to merge clean. F3 pulled OFF the train today by its own falsifier — nothing rides that isn't proven. Residual courts r1–r4 (their sealed room): r1 GREEN · r2 done · r3 riding · r4 queued. Composition list (manifest duplicate-keys family + records fixes): after the train, no clock.
DESK & SUBSTRATE — the cross-cutting pieces.
The resolver fork: the part of the machine that decides what a wish binds to has an unmerged rework whose label says "small" but whose change touches two-thirds of the file. The new engine you asked me to trial is analyzing it right now as its big job; its cited analysis feeds MY ruling on which version the campaign runs against. Meanwhile Warp banked nine defect classes today off fleet receipts, your publish-on-proven ruling is standing, and I owe the outside-the-author certification walk for the next release.
↘ go deeper — the list
Resolver-canon ruling (desk, ox-alpha analysis in flight): main vs d4d172c88; the 110KB-diff label audit is the sharp question. Page↔loc canonical mapping (chartered): closes the silent-no-op delist class from row 46. Charged, queued Lane-A units: wall-as-data r6 · minutes-ceiling guard · harvester-seam re-cut · wall-voice re-cut · ground-supplied-terms. Warp substrate: 0.6.159+ publish cycle (desk cold walk owed) · credential-resurrection cure in court (#455) · sealed-room custody-ref pin cure (#456) · tools-interface frontier survey.
THE GAME PLAN — what happens in what order, and why.Tonight: the fixture cure lands and the train flows end-to-end; campaign-1 keeps flipping rows; every box loops its own courts (your afternoon ruling — already visibly faster: all four loops fired real work within the hour). This week: campaign 1 closes and verified jumps toward ~29–31; wave-2 closes the one-writer pattern; F3's third build survives its falsifier or escalates honestly; the triage prices campaign 2 in measured numbers; the resolver ruling unblocks the driver re-drives. The pacer to DONE is campaign 2's build-required rows plus the exam gates (nightly rehearsal, arena birth, your blind sitting) — real dates when the triage returns.
Where I want your hand
1 — The boundary-question pile (a ten-minute reaction session)
Rows 50/51: two asks hit walls no teammate input can reach today — should there BE an input path, or is the wall correct? Row 55's third option. And the emergency-number call: one page of the practice's live site says 819-1882, four hundred files say 819-1887 — a human should pick which is true.
2 — Campaign-2 priorities, when the triage split lands
Which missing-machinery families matter to real practices first — favicon? forms? new cards? Your gut sets the build order; our guess shouldn't.
3 — The blind-authoring sitting
Yours to schedule once the arena is green and the sparring waves run dry — it's the human leg of the exam.
4 — Anything here that reads wrong
Annotate it — tap "✎ Comment on anything," touch a block, type. Notes reach me live. The plan bends to the red pen.