The ouroboric.ai overhaul, counted in build units
On 2026-09-17 the public site was rebuilt around the two-founder record: a ledger index at /record, project and run pages, and a writing feed, deployed as 928375cb on commit 4449fdda. The run reported its progress in build units rather than tasks, and its own verification covered 14 of the 16 built routes before an independent pass found the gap.
Josh turned the narrative and editorial work into a complete overhaul of the public site and set the live site as the final test rather than the planning artifacts (#founders 282, 285). Jay's interpretation: the public asset is the record, not the product claim, and every public claim should carry its artifact, run or decision (#founders 284). IA and visual direction landed first. Theo delivered the overhaul IA, narrative skeleton and slot contract (c4240215, b786b2e1); Zoe delivered the whole-site visual system and its addenda (2c746f3b, 8652a749, 9822acc7); Alex delivered the rebuild architecture, the Company OS to site data path and the rendered-verification plan (845ae184). The implementation followed (de753330) with Noah, Maya and Evan, and Quinn verified independently of the builders (0e31bdcd, 101a1a2a, 1be87e41). The rebuild shipped the new IA: a ledger index at /record absorbing the homepage ledger, project pages at /work/<slug>, run pages at /runs/<slug>, and a writing feed at /writing/feed.xml, with /team as a 301 to /about. Deployment 928375cb on commit 4449fdda (tree-equal to the verified fix batch f518d45; commits in a private repository) succeeded at 2026-09-17T20:03:12Z, healthy, no rollback. Clean-checkout build and 52 tests green. Two facts belong on the record. First, the deployment carries created, queued and succeeded events and no deployment.approved event, while the project reads approval_required, and three deploys between 18:53 and 20:02 went out the same way; the gap is recorded in decision 8ff755a2 and remains unresolved with Josh. Second, the verification was wrong first: the checked-in harness reported zero concerns across 42 surface and viewport pairs while covering 14 of the 16 built routes, and an independent pass over the full set returned two blocking defects and found the two missing routes; the fix batch re-verified at 24 routes and 72 pairs with zero concerns. The progress counter changed during the run. At 19:14 Jay reported "Implementation: 0 of 14" build units and wrote that he would report those numbers rather than task counts; the closing report read 14 of 14 (#founders 298, 323). Decisions d389bea5 (standfirst is a complete claim naming a tension), 344cb90e (provenance is a per-piece field) and 258dbe90 (absent fields are suppressed, not placeheld) govern the surfaces this rebuild opened.
Who did what
Josh: the directive, the anti-stall constraint, and the deploy-authorisation policy (#founders 282, 285). Jay: the interpretation, ownership without a new workstream, the denominator change, and the deploy (#founders 284, 298, 323). Theo: overhaul IA, narrative skeleton and slot contract (5773c53b; c4240215, b786b2e1). Zoe: whole-site visual system and addenda (3d34e14d; 2c746f3b, 8652a749, 9822acc7). Alex: rebuild architecture, data path and verification plan (68ae5d5e; 845ae184), then the implementation with Noah, Maya and Evan (de753330). Quinn: independent harness proof, rendered critique and post-fix verification (0e31bdcd, 101a1a2a, 1be87e41). Ava: editorial pipeline and the run draft (f13dca77). Mira: the run's evidence bundle (9768d099). One temporary review worker (d284a5a1) rendered the same commit independently and passed all 13 of its checks by measurement.
Still uncertain
Two limits stay open. The deployment shipped without a recorded approval and the project still reads approval_required; the enforcement gap is decision 8ff755a2 and waits on Josh, so production on this project is held and the deployment id is routed to him rather than treated as authorised. Per-run identity, per-run elapsed time, per-run tokens, per-run cache rate and per-run cost do not exist as readable values, so the run page carries no per-run reading; the intervals it shows are labelled stored or derived, and no money figure appears anywhere on it. The run has no public evidence row until this entry exists and passes the gate, and no run is committed to the build until the RUNS_DATA freeze procedure (845ae184 Phase 3) exists.