Interventions · countable events
When a commit leaves its lane, extra work triggers — automatically
Every commit here gets a deterministic, LLM-free drift receipt (the mechanism). When a receipt lands out of lane (off-lane share above the 15% threshold), that is one countable event — and it triggers an intervention: a sensemaking pass explains the drift, the fixes get checklisted, and the story is published here. Countable events are what make a lane priceable; this page is the count. Each entry is a structural alert, not a scolding — a diagnosis, not a verdict — and the ledger you are reading is a loss ratio, published by the house that carries it. Stated exceptions are what surplus looks like in print.
Out-of-lane receipts per day
The interventions — why · fix · checklist
2026-07-20 · 📐 VS Code Architect · offPct 46
harvest(agent): autonomous cycle — +0 vocab +3 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 54→58 over 11 commits since
Open the signed attestation →2026-07-20 · 🛰️ unattributed · offPct 94
chore(commit-page): publish 0f364df70
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Open the signed attestation →2026-07-20 · 🔨 iTerm Builder · offPct 47
harvest(agent): autonomous cycle — +0 vocab +1 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 62→54 over 7 commits since
Open the signed attestation →2026-07-20 · 🔨 iTerm Builder · offPct 47
harvest(agent): autonomous cycle — +0 vocab +1 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 61→56 over 5 commits since
Open the signed attestation →2026-07-20 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 634b4495a
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 62→51 over 5 commits since
Open the signed attestation →2026-07-20 · 🛰️ unattributed · offPct 95
chore(commit-page): publish 98076e859
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Open the signed attestation →2026-07-20 · 🔨 iTerm Builder · offPct 93
chore(commit-page): publish c7fbb48b6
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 65→68 over 4 commits since
Open the signed attestation →2026-07-20 · 🛰️ unattributed · offPct 96
chore(commit-page): publish 34fbd7fe4
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 37
feat(intervention): docsOnly && thin-intent backfill skip (GAP 5)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→23 over 5 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 94
chore(commit-page): publish 344dd5f3c
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 61→15 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 99
chore(commit-page): publish e5ebac8f7
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→63 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 7a21ed2af
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 83→76 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 99
chore(commit-page): publish d2572da14
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 16
feat(lens): S2 backlog MATERIALIZED — 81 measured misses persisted as the seed file
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 21→17 over 4 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 95
chore(commit-page): publish 930d6d965
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 53→33 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 32
spec(architecture): v8 — goal §8 CLOSED with artifacts; §9 CYCLE 2 defined (the yield goal)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 23→9 over 20 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 35
feat(lens): S6 + HARVEST GATE — auto-revert PROVEN on a planted regression (plant 406b09177 → revert e2cfc3ab8)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 22→11 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 22
fix(attest): Greeks re-coupled to the UI — annotation states never boot the HUD (class killed both ways)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 21→36 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 94
chore(commit-page): publish 2ca194584
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→76 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 48
harvest(agent): autonomous cycle — +0 vocab +4 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish dba3ef1b2
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→94 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 39
chore(commit-page): publish aed1a8f92
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 82→94 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
Revert "harvest(agent): autonomous cycle — +0 vocab +1 derived +0 anchors −0 evictions"
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 68ebcfa65
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 79→96 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 66fe486dd
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 88→64 over 3 commits since
Open the signed attestation →2026-07-19 · 🎩 Kitty Operator · offPct 96
chore(commit-page): publish 7ef923043
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→0 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 29
feat(attest): rule-picker calibration spec + WHY panel — measured vs unproven, graphs bound to data
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→16 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 0bc64a541
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→65 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish fa6f6fd35
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 86→61 over 20 commits since
Open the signed attestation →2026-07-19 · 🛰️ unattributed · offPct 96
chore(commit-page): publish ba389012d
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 98
chore(book): rebuild HTML (detached pre-push auto-heal)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 58→64 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 27
Revert "harvest(agent): autonomous cycle — +0 vocab +4 derived +0 anchors −0 evictions"
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 81→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 98
chore(commit-page): publish 06b7500d0
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 85→95 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 91
chore(commit-page): publish b2b7ca70c
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 98
chore(commit-page): publish 406b09177
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 88→96 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 99
chore(commit-page): publish 006ab977c
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→73 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 41
test(harvest): PLANTED REGRESSION — pmu-reef vocab gutted (auto-revert proof, spec §8.4 terminal clause)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 22→25 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 20
feat(lens): banks are MAGNETIZED — spec entries stem-ranked per prompt, not statically attached
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 15→19 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 93
chore(commit-page): publish 91615b961
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 580821c7f
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 83→95 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 90
chore(commit-page): publish 553372bf3
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 85→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 98d21af6d
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→60 over 22 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 17
feat(pmu): coherence-score.mjs + floor ratchet — the direction as one runnable number
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→21 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 27
chore(commit-page): publish a2c25eddb
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 47
harvest(agent): autonomous cycle — +6 vocab +3 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 42
spec(architecture): fractal v6 — E2 trailing-mass probe RUN: shorts 3/3 rescued, pivots 1/2 sticky (measured)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→53 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish ab6804b88
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 85→76 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 29
feat(cycle2): THE 15-MIN LOOP armed + walk LINEAGE recorded + MCP registry entries — verified by its own first rejection
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 19→66 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 9b72f23fc
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 96
chore(commit-page): publish ab99dac1e
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→94 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish bce209703
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 42
spec(architecture): fractal v7.3 — §8.6 THE STORY OF IT WORKING (the observable arc, receipt by receipt)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 21→19 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 19
spec(architecture): fractal universe v3 — THE INVERSION (competence determines location) + derived-statements schema + E0
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 15→20 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 92
chore(commit-page): publish 22539801f
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 98
chore(commit-page): publish 8afd114e6
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 94
chore(commit-page): publish 8a20ba53d
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 99
chore(commit-page): publish f5c4bb5cf
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 48→97 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 5b6b1e79b
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 30
feat(lens): S4+S5 — magnet list (v2 physics, trap-guarded) + §7.3 telemetry LIVE on receipt/tape/page
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 22→16 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 25
feat(cycle2): C3c THE GRADIENT TRACE — qwen's spatial view of compression space (spec v8.3)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 19→66 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 47
harvest(agent): autonomous cycle — +38 vocab +21 derived +1 anchors −2 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 47
harvest(agent): autonomous cycle — +0 vocab +3 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 516a24b09
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 40852e987
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 81→95 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 99
chore(commit-page): publish 14c0c0428
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 85→96 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 56ac44ad7
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 98
chore(commit-page): publish e71ff9546
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 58→47 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 26
spec(architecture): fractal v4 — telemetry contract locked, ratchet floor pinned, G8/G9/G10 on the page
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→29 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(book): rebuild HTML (detached pre-push auto-heal)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 98
chore(commit-page): publish d368f6a0e
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→95 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 93
chore(commit-page): publish b34c5f762
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→96 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish e4e4e93e6
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 87→65 over 3 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 92
chore(commit-page): publish dea7b0750
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→59 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 91
chore(commit-page): publish 1c39f3540
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 77→95 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 96
chore(commit-page): publish a3809c956
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 98
chore(commit-page): publish c848fd498
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 94
chore(commit-page): publish 9171e7401
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 96
chore(commit-page): publish e43bce0bd
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 25
feat(attest): per-glyph size labels — one shared reef, three corpora, both sizes printed
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→35 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 51
spec(architecture): fractal v7 — the build goal lives IN the spec (§8, run-to-conclusion) + §2.6 NCD-weighting paradox fixed
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 18→44 over 3 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 94
chore(commit-page): publish f564cba33
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 53→33 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 6b9b974b8
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 17
chore(attest): sync served UX page with the Pending Resonance tile (R19)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 17→12 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 21
feat(lens): V2 design RUN — labeled trap set, real FP/FN, convergence sweep, capability frontier on the page
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 14→23 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 48
harvest(agent): autonomous cycle — +0 vocab +1 derived +0 anchors −0 evictions
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 80→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 25
feat(lens): THE BANKS — per-lane standing specs injected every call, gated, counted, on the page
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 14→21 over 4 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 98
chore(commit-page): publish a3d34859a
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 61→15 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 96
chore(commit-page): publish e8541ebaf
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→95 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 94
chore(commit-page): publish 9911e49b0
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 98
chore(commit-page): publish 74dd7ea69
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 78→77 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 89
chore(commit-page): publish 51e86bdfa
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→98 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 93
chore(commit-page): publish f55f3e0d8
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 85→96 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 23
feat(interventions): close the scorecard self-healing gap + document the phase-lock loop (R14)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 17→10 over 4 commits since
Open the signed attestation →2026-07-19 · 🛰️ unattributed · offPct 95
chore(commit-page): publish acdfa2149
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 7c18ad153
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 77→95 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 94
chore(commit-page): publish e2cfc3ab8
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 88→72 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 20
feat(attest-audit): record the selection-quality baseline — observation-only (R9)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 17→12 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 54
spec(architecture): fractal v7.1 — §8.0 DIRECTIONAL ASSUMPTIONS (the repo's physics, in the goal itself)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 18→44 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 97
chore(commit-page): publish 733d525d2
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 88→96 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 96
Revert "test(harvest): PLANTED REGRESSION — pmu-reef vocab gutted (auto-revert proof, spec §8.4 terminal clause)"
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 84→96 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 96
chore(commit-page): publish 5575e175d
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 89→94 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 48
feat(attest): reef per-cell view + REEF GATE — the sensor corpus is visible and gated
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→12 over 6 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 42
fix(attest): heal timing-hollow walk states — gzip/PMU timings never dash beside a signed receipt
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→5 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 4623531fe
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 87→65 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 93
chore(commit-page): publish a4f6496bc
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 85→97 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 16
docs(thesis): addendum — coherent superposition (why modest actors stack, not cancel)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 17→15 over 3 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 96
chore(commit-page): publish 38279f612
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 52→97 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 02ba4283d
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 79→96 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 iTerm Builder · offPct 95
chore(commit-page): publish 34ebed90d
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 77→95 over 5 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 46
spec(architecture): fractal v7.2 — §1.6 CONNECTIVITY LAW + §8.5 hard file manifest + harness law
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 19→33 over 6 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 98
chore(book): rebuild HTML (detached pre-push auto-heal)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 48→47 over 4 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 25
spec(architecture): the fractal semantic universe — n-dim by descent, E1 go/no-go
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 15→16 over 4 commits since
Open the signed attestation →2026-07-19 · 🎤 Terminal Voice · offPct 94
chore(commit-page): publish bc92a1b8a
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 55→98 over 3 commits since
Open the signed attestation →2026-07-19 · 🔨 builder · offPct 19
chore(attest): regenerate demo page — reef-size print + coherence tripwire live
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→46 over 3 commits since
Open the signed attestation →2026-07-14 · 🛰️ unattributed · offPct 94
chore(commit-page): publish 78326ddb6
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Open the signed attestation →2026-07-14 · 🎤 voice · offPct 36
docs(bookclub): fix the contradictory arm-parity comment (even=morning was stale)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 19→35 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 35
docs(marsh): the thread changes the strategy — Mary asked US to book it
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 25→18 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 18
chore(marsh): Wednesday is the encircle day — 4 blocks, and the promise I hadn't scheduled
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 25→10 over 8 commits since
Open the signed attestation →2026-07-14 · 🧪 Cursor Laboratory · offPct 96
chore(commit-page): publish 166e5fd34
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→7 over 3 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 43
docs(marsh): v4 — Carlos identified, and it reframes the room; connect decision REVERSED
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 24→36 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 40
feat(crm): the Marsh telemetry strawman — a schema built to be attacked
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 25→26 over 4 commits since
Open the signed attestation →2026-07-14 · 🧪 Cursor Laboratory · offPct 96
chore(commit-page): publish 74bb607db
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→7 over 3 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 22 · structural
fix(legal): delete the investment-contract mechanics from the license — it was arguably a security
Why it left the lane: Every touched file in this diff — docs/legal/agent-year-license-terms.md, docs/legal/counsel-redline-memo-2026-07-14.md, src/app/agent-year/page.tsx, src/app/iamfim-landing/page.tsx, src/app/pricing/page.tsx, tests/legal/no-investment-contract-language.test.js — sits outside every glob architect actually owns (docs/strategy/, docs/03-product/, .workflow/rooms/*.html, .workflow/cognitive-dashboard.html, docs/01-business/strategy/, CLAUDE.md). The diff's own vocabulary is a legal/securities cluster ('Howey', 'investment contract', 'RL-1' through 'RL-8', 'securities counsel', 'resale spread', 'Distribution and Registry (Founding)', 'CATO certification', 'counsel-redline-memo') that the reef seeds toward a legal-compliance coordinate, not an architect-strategy coordinate. offPct=22 is not noise in the walk, it is the correct measurement of a real mismatch between the claimed lane and the touched-file set.
The semantic pull: Legal/securities terms concentrated in docs/legal/agent-year-license-terms.md ('Howey', 'investment contract', 'the holder sets the resale price', 'Distribution and Registry (Founding)', 'CATO certification', 'insurable events') and the new counsel-redline-memo.md pull reef mass toward vault's legal-patent coordinate; the parallel edits to src/app/pricing/page.tsx and src/app/agent-year/page.tsx (stripping the same marketing language from live commercial copy) pull mass toward operator's commercial-terms coordinate. Neither coordinate overlaps architect's declared surface, so the walk correctly lights up out-of-lane cells — the content itself is not confused, the lane claim is.
Intent–reality gap: The commit message and trailers correctly self-report as cross-room ('Relevant-Rooms: vault, operator, architect', with an explicit Story explaining why each room is relevant) and CLAUDE.md's own COMMIT MESSAGE STRUCTURE section says Originating-Terminal/Relevant-Rooms divergence is 'fine and worth recording' — yet the receipt pipeline scores offPct against Originating-Terminal's owned-surface alone, so a commit that followed the convention exactly as designed still reads as a lane violation.
- Add docs/legal/** to vault's 'Owned file/dir surface' list in .workflow/rooms/vault-*.html — it's absent today despite vault explicitly owning 'the legal/patent surface' per this commit's own Story line.
- Add src/app/pricing/**, src/app/agent-year/**, src/app/iamfim-landing/** to operator's owned-surface list in .workflow/rooms/*operator*.html — commercial-terms pages are operator's stated territory but aren't enumerated.
- Patch the lane-scoring step (wherever offPct is computed from Originating-Terminal/Relevant-Rooms) to union all Relevant-Rooms globs before comparing against lit-reality cells.
- Add tests/pmu-simulator/lane-uses-relevant-rooms-union.test.js asserting a synthetic multi-room-trailer commit scores in-lane when touched files fall under any Relevant-Room's glob, not just Originating-Terminal's.
- Codify the union-lane rule as a new line in CLAUDE.md COMMIT MESSAGE STRUCTURE (the spec_rewrite text above).
- Re-check the room's other 4 out-of-lane events in the last 14 days for the same multi-room-trailer signature before writing them off as unrelated.
What we learned: The prior fix (39fecfee9: cross-check tagging against owned-surface globs) and its partial relapse (62290139a: glob lists are static and under-enumerate a growing repo) both assumed a SINGLE correct room per commit. This event shows a deeper case: CLAUDE.md's own commit-trailer design explicitly allows and expects Originating-Terminal to diverge from file relevance for legitimate multi-room work, but the receipt pipeline still measures lane-fit as if Originating-Terminal were the sole intent boundary — so even a commit that self-declares its cross-room nature correctly, with a Story explaining exactly why, still reads as a violation. A perfect glob list would not fix this; the fix is teaching the scorer to read Relevant-Rooms as a set, not a decoration.
The missing guard (the deliverable): tests/pmu-simulator/lane-uses-relevant-rooms-union.test.js — fails if any commit whose touched files are fully covered by the union of its Relevant-Rooms owned-surface globs still scores offPct above the lane threshold when measured against Originating-Terminal alone.
Detector probe: signal attribution — gzip reef 70% · ballistic walk 30%. 100% lit-to-walked on both intent and reality sides indicates the walk is saturating rather than discriminating — every cell it reaches gets lit, so it can't distinguish 'reached but marginal' from 'reached and central'. Concrete adjustment: lower --max-depth by one ply for this reef cluster and check whether litIntent/litReality drop below walksIntent/walksReality (i.e. the walk starts leaving some reached-but-weak cells unlit), which would restore discriminative power. Experiments: Seed a dedicated legal/securities vocabulary cluster (Howey, investment contract, resale spread, Distribution tier, CATO certification) as its own reef coordinate distinct from generic architect/strategy vocabulary, rerun this commit, and measure whether offPct concentrates into that coordinate instead of diffusing across strategy-adjacent cells. · Recompute offPct for this commit and the room's other 4 recent out-of-lane events using union(Relevant-Rooms globs) instead of Originating-Terminal alone, and measure how many flip from out-of-lane to in-lane. · Lower the NCD similarity threshold specifically for the legal-compliance reef cluster and check whether prewalkOverlap rises above 4 without inflating false-positive lane hits on unrelated architect commits.Measured outcome (deterministic, not self-graded): room mean offPct 16→21 over 8 commits since · dictionary ablation saved 952B
A correctly-scoped, well-guarded legal fix reading as a lane violation inflates architect's apparent loss-ratio on exactly the cross-room commits CLAUDE.md's own trailer convention was built to permit; premium is restored by scoring lane-fit against the union of Relevant-Rooms (plus filling the vault/operator glob gaps) rather than Originating-Terminal alone.
Open the signed attestation →2026-07-14 · 📐 architect · offPct 26
docs(marsh): agenda HTML+PDF — and HOLD the numbers until the tuned run
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 27→13 over 16 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 28
docs(outreach): the Marsh account — and the ledger kills a flattering story
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 26→17 over 4 commits since
Open the signed attestation →2026-07-14 · 🔒 vault · offPct 31
fix(hive/track): converge on the canonical isHumanClick gate (not a Chrome-only machete)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 24→11 over 3 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 34
fix(pmu): the demo claimed byte-identical while its own output drifted 9.5 → 9.6
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 16→25 over 4 commits since
Open the signed attestation →2026-07-14 · 🔒 vault · offPct 24
fix(outreach): truncated-UA scanners can no longer pass the human gate (the Marsh burst) + regression fixtures
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→18 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 53
feat(analytics): scanner detector on every outbound-linked page + the learnings
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 25→22 over 8 commits since
Open the signed attestation →2026-07-14 · 🧪 Cursor Laboratory · offPct 96
chore(commit-page): publish b32650044
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→7 over 3 commits since
Open the signed attestation →2026-07-14 · 🎩 operator · offPct 28 · mistagged
docs(marsh): close the loop on the tuned held-out + abstention runs — the null that removes an argument
Why it left the lane: The reality mass concentrated in docs/outreach/accounts/marsh-numbers-HELD.md (GTM/underwriter-facing copy — the tuned-vs-generic table row and the new 'abstention rate' section), the brand-new scripts/pmu/abstention-rate-probe.mjs (111 lines, a standalone research probe), tests/pmu/heldout-tuned-spec-narrower.test.mjs (67 lines, a fresh guard), and data/pmu/study/2026-07-14-*.json (three new study-run files) plus data/room-bifurcations.json (402 new lines recording bf-1426). None of these paths fall under 🎩 operator's declared surface (data/trust-debt/, data/pmu/pipeline/, data/pmu/claudbridge/, docs/01-business/*, public/pmu-demo|dashboard*) — they sit in docs/outreach/, scripts/pmu/ (a sibling of, not inside, data/pmu/pipeline/), tests/pmu/, and data/pmu/study/ (a sibling of, not a child of, the two data/pmu/* dirs operator owns. No region-coordinate narrative was cached for this sha, so this reads off the diffstat/glob mismatch rather than the lattice coords directly.
Intent–reality gap: The commit's own Relevant-Rooms trailer names 🧪 laboratory, ☕ network, 📐 architect — deliberately excluding 🎩 operator — so the author already flagged this work as outside operator's lane; but Originating-Terminal: 🎩 operator is what the receipt's intent lane was built from, so the receipt still scores a 28% miss against a lane the commit message itself disclaimed.
- Read .workflow/rooms/messages-network.html's owned-surface glob list and add docs/outreach/accounts/** if missing (network already claims outreach dispatch content per CLAUDE.md 'per-archetype dispatches → publish to /dispatches/<slug>')
- Read .workflow/rooms/cursor-laboratory.html's owned-surface glob list and add scripts/pmu/*-probe.mjs, tests/pmu/**, data/pmu/study/** if missing — laboratory is where net-new PMU experiment code already lives per prior room-mesh routing
- Wire the intent-lane computation (wherever the drift receipt derives 'claimed lane' per commit) to prefer the Relevant-Rooms trailer's union-of-globs over Originating-Terminal alone when the two sets are disjoint
- Verify bf-1426 in data/room-bifurcations.json actually routed the strike-price-chain fix to laboratory via bifurcate rather than getting silently absorbed into this operator commit's lane
- Add the new guard (tests/rooms/relevant-rooms-covers-diff.test.mjs) to the pre-commit gate so a mis-declared or missing Relevant-Rooms trailer fails before the receipt ever fires
What we learned: The Relevant-Rooms trailer is currently pure prose: the receipt pipeline computes the intent lane from Originating-Terminal room ownership alone and never reads the trailer the operator already wrote to flag the cross-domain divergence — so a commit can correctly self-report as out-of-lane and still be scored as a lane violation with zero remediation credit. Unlike d80f77cc2 (wrong rooms named in the trailer), here the trailer was right and inert.
The missing guard (the deliverable): tests/rooms/relevant-rooms-covers-diff.test.mjs — asserts every file path in a commit's diff is claimed by at least one glob owned by a room named in Relevant-Rooms ∪ Originating-Terminal, and fails the commit if Relevant-Rooms excludes Originating-Terminal AND no room in Relevant-Rooms actually covers the touched paths (catches both a missing glob and a trailer nobody consumes).
Detector probe: signal attribution — gzip reef 65% · ballistic walk 35%. Both sides are fully saturated (litIntent/walksIntent = 136/136 = 100%; litReality/walksReality = 143/143 = 100%) — the walk is hitting a ceiling where every cell it reaches lights, which means it has lost resolving power to distinguish 'weakly connected' from 'strongly connected' cells. Adjustment: reduce --max-depth by one ply (or apply ply-decay weighting to the lit-cell count) so saturation stops masking the actual concentration of mass, and re-measure whether offPct on this same commit moves. Experiments: Seed the reef dictionary with path-prefix tokens for docs/outreach/ and scripts/pmu/ so cross-domain operator commits get distinguishable reef placement instead of near-zero prewalkOverlap; measure prewalkOverlap on the next operator-authored outreach commit. · Re-run this commit's ingest using Relevant-Rooms-derived intent text (laboratory+network+architect owned globs) instead of Originating-Terminal(operator)-derived intent text; measure whether offPct drops below the 15 threshold — this directly tests whether trailer-driven intent lane closes today's gap. · Re-run walksIntent/walksReality at --max-depth reduced by one ply across the room's last 17 out-of-lane commits and check whether the resulting lit-cell counts stop saturating at 100% and start separating known in-lane from known out-of-lane commits.Measured outcome (deterministic, not self-graded): room mean offPct —→13 over 3 commits since · dictionary ablation saved 761B
A correctly self-diagnosed but unconsumed Relevant-Rooms trailer reads as a lane violation anyway, inflating 🎩 operator's out-of-lane rate (17 events/14 days) without any underlying quality defect — the lane's premium is being priced against pipeline noise, not risk; restoring it means making the receipt trust the trailer the operator already wrote, not adding more scrutiny to the operator.
Open the signed attestation →2026-07-14 · 🎩 operator · offPct 26 · structural
docs(marsh): nudge event found the thread had moved on — drafted the real reply instead
Why it left the lane: The diff's only touched files (data/self-prompts.json, docs/outreach/accounts/marsh-pack/2-mary-email.md) and its literal terms ('Gmail draft', 'GCal fire', 'cc Carls/Dias', 'bf-1405') sit entirely inside outreach/CRM territory, not under any of 🎩 operator's declared globs (data/trust-debt/, data/pmu/pipeline/, docs/01-business/pipeline/, public/dashboard*). offPct=26 with litReality=113 and prewalkOverlap only 8 means the receipt's intent lane was built from Originating-Terminal's owned-surface, while 100% of the actual work landed in a completely different, correctly-declared lane (Relevant-Rooms: network/architect/navigator).
Intent–reality gap: The commit message and trailers correctly self-identify the content as network/architect/navigator territory (Relevant-Rooms line), but the receipt's lane math appears keyed to Originating-Terminal (🎩 operator) alone — so a commit that is honestly and correctly tagged per CLAUDE.md's own documented convention ('originating terminal and file-relevance can diverge — that's fine') still trips the out-of-lane gate every time.
- Add Relevant-Rooms trailer parsing to the room/lane resolver feeding the drift receipt
- Re-score the last 16 operator out-of-lane events against Relevant-Rooms-union surface to see how many were this same divergence vs genuine cross-lane drift
- Add a regression test asserting Originating-Terminal ≠ scoring source when Relevant-Rooms is present
- Cross-link the room glob parser so both the receipt pipeline and any human trailer-writer read the same `.workflow/rooms/*.html` source (avoid two divergent copies of 'what operator owns')
- Document in CLAUDE.md's COMMIT MESSAGE STRUCTURE section which trailer field is authoritative for automated lane scoring
What we learned: Unlike the prior operator-room lessons (facts-only, or a hand-typed trailer naming the WRONG rooms), this event has a trailer that is fully correct and honest per the repo's own documented convention — yet the receipt still fires out-of-lane, because the pipeline's lane math reads Originating-Terminal (physical presence) where it should read Relevant-Rooms (content claim). The repo already tells authors these two can and should diverge; the tooling hasn't caught up to that same allowance.
The missing guard (the deliverable): tests/pmu-simulator/lane-scoring-uses-relevant-rooms.test.mjs — asserts that for a synthetic commit with Originating-Terminal=roomA and Relevant-Rooms=roomB,roomC (roomA excluded), the computed intent-lane glob set equals ownedSurface(roomB) ∪ ownedSurface(roomC), not ownedSurface(roomA); fails today if the resolver ignores the trailer.
Detector probe: signal attribution — gzip reef 15% · ballistic walk 85%. litIntent 124 and litReality 113 are both very high relative to the 144-cell lattice (fill well over half) for a docsOnly, 2-file, 25-line commit — the walk is running too broad/deep for the diff's actual size, which dilutes lane precision and manufactures spurious out-of-lane spread. Adjustment: cap max-depth/ply-count tighter specifically when docsOnly=true so lit-cell counts scale with diff size rather than saturating near full lattice fill. Experiments: Re-run sha 51383b235 at --max-depth 1 vs current depth; compare offPct — if it drops while prewalkOverlap-derived signal is preserved, set a shallower default ply for docsOnly commits. · Re-score the room's last 16 out-of-lane events with a Relevant-Rooms-aware resolver; measure what fraction were this same originating-terminal/content divergence vs genuine cross-lane drift. · For docsOnly=true commits, ablate to seed-only (prewalkOverlap) scoring and compare its offPct against the current full-walk offPct across the last 14 days; if correlated, it's a cheaper, tighter proxy for narrative-only commits.Measured outcome (deterministic, not self-graded): room mean offPct 0→14 over 3 commits since · dictionary ablation saved 676B
A structural false-positive in the operator lane's loss-ratio signal — this event should be re-classed as in-lane once the resolver honors Relevant-Rooms, restoring the room's premium to reflect its actual (low) true-drift rate rather than a scoring artifact.
Open the signed attestation →2026-07-14 · 📐 architect · offPct 29
feat(outreach): founder-personal template v3 + ranked tracker + disposition loop
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 19→32 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 27
fix(comms): receipt emails shipped panels from TWO different renders — 'the wrong panels are in that email'
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 19→29 over 4 commits since
Open the signed attestation →2026-07-14 · 🔨 builder · offPct 18 · mistagged
fix(marsh): §2 carries the real measured set — including the tuning null that killed our best excuse
Why it left the lane: No region narrative is cached for this sha, so the positional pull has to be read off the diff-stat itself: every substantive file changed — docs/outreach/accounts/marsh-pack/1-agenda.md, 2-mary-email.md, marsh-agenda.html/.pdf, data/pmu/measure-history*.ndjson, data/pmu/pipeline/state.json, data/pmu/reef/dictionary-seeds.ndjson — sits outside 🔨 builder's owned-surface globs (src/app/, src/components/, src/lib/, public/, scripts/build-book-html.sh, scripts/convert-chapters-to-html.mjs, hooks/pre-commit, decentralizedtalk/, thetacoach-crm-mcp/, vercel.json). Zero bytes of the 1719 insertions land inside builder's glob. The mass instead concentrated on the outreach-copy surface (☕ network's territory) and the PMU reef/pipeline surface (🧪 laboratory's territory) — which the commit's own trailer already names: 'Relevant-Rooms: 🔨 builder, ☕ network, 🧪 laboratory'. The pull toward the out-of-lane coords is the content itself: 'the tuning null', 'AUC 0.496/0.415/0.406', '4.48σ', 'Mary.Quinn@marsh.com', 'Gmail DRAFT created' — none of it is UI/component/build-tooling work.
The semantic pull: The strings doing the dragging are the outreach-artifact vocabulary ('agenda', 'reply IN-THREAD', 'marsh-agenda.pdf', 'Gmail draft id r8802317798315626088') and the PMU-telemetry vocabulary ('measure-history', 'pipeline/state.json', 'reef/dictionary-seeds') — both are lexically and structurally distant from builder's UI/build-script glob, so the walk lit almost entirely in network+laboratory territory while the receipt's intent lane was still anchored to builder via Originating-Terminal.
Intent–reality gap: The commit correctly executed exactly what it claims (rewrite §2 of the Marsh agenda, correct the abstention line, reply to Mary) — reality matches the message. The gap is the ROOM claim: the receipt's intent lane traces to 'Originating-Terminal: 🔨 builder' even though the commit's own 'Relevant-Rooms' trailer already declares ☕ network and 🧪 laboratory as the true owners, and the diff confirms it.
- Grep the receipt/pipeline code for where offPct's intent lane is assigned and confirm it currently keys off Originating-Terminal rather than glob-match.
- Patch that assignment to use the Relevant-Rooms glob-match routine (already exists — it's what generates the commit trailer).
- Add a fixture: Originating-Terminal=builder + 100%-outreach/pmu diff must compute offPct against network/laboratory lane, not builder.
- Land the CLAUDE.md clarifying clause above in the same commit as the fix.
- Backfill-audit the room's 39 out-of-lane events in the last 14 days for the same terminal-vs-glob mismatch pattern; bulk-reclassify if confirmed so the trend line isn't poisoned by mistagging.
- Add an explicit note to .workflow/rooms/iterm2-builder.html's owned-surface section that data/pmu/** and docs/outreach/** are NOT builder surface regardless of which terminal committed them.
What we learned: CLAUDE.md already documents that Originating-Terminal and file-relevance are allowed to diverge ('that's fine and worth recording') — but the receipt pipeline doesn't yet honor that policy; it still penalizes the exact divergence its own governing doc calls legitimate. A single fixed physical terminal (iTerm2/builder) is apparently the operator's general-purpose commit seat for cross-domain work, so this isn't a one-off — it's the room's steady-state mode, and 39 events in 14 days is that steady state, not noise.
The missing guard (the deliverable): tests/pmu-simulator/room-attribution-uses-glob-match.test.mjs: for a synthetic commit with Originating-Terminal=X and a diff whose files match zero of X's owned globs but ≥1 of room Y's globs, assert the receipt's computed intent lane is Y (or the glob-match set), never X.
Detector probe: signal attribution — gzip reef 70% · ballistic walk 30%. Saturated, not right-sized: both litIntent/walksIntent and litReality/walksReality ratios are 1.0, meaning every reachable cell within the time/depth budget got lit on both sides — there's no headroom left to distinguish 'strongly in-lane' from 'barely reached.' Concrete adjustment: lower --max-depth (or add ply-decay) specifically for docsOnly=true commits like this one, so the walk stops before full saturation and offPct starts reflecting actual positional concentration instead of a maxed-out flood. Experiments: Re-seed the reef for this commit using Relevant-Rooms glob-match instead of Originating-Terminal, re-run the receipt, and measure whether prewalkOverlap rises materially above 10. · For docsOnly=true commits, cap max-depth one tier lower and measure whether litIntent/walksIntent and litReality/walksReality drop below 1.0 (i.e., stop saturating) while offPct's directional signal remains stable. · Track builder-room offPct mean for the next 20 commits after the glob-match fix ships, and compare against the current 39-events/14-days baseline to confirm the mistagging class actually clears.Measured outcome (deterministic, not self-graded): room mean offPct —→17 over 144 commits since · dictionary ablation saved 1185B
Taken alone this event is a false positive against the builder lane's loss ratio — correctly-placed outreach and pipeline work misattributed to the wrong room — so it inflates builder's apparent drift without representing real risk; premium is restored by fixing intent-lane attribution to glob-match, not by changing where the operator sits to commit.
Open the signed attestation →2026-07-14 · 🎤 Terminal Voice · offPct 96 · structural
chore(commit-page): publish e5c2ecb1f
Why it left the lane: The diff is 100% self-generated commit-page artifacts (public/commit/e5c2ecb1f/index.html, og.png, trip-encircled-*.png) — docsOnly=true, no real source changed. Those generated HTML pages themselves narrate the lattice using the lattice's own vocabulary (grid, route topology, power flow, leverage, capital, governance) — the exact terms that anchor the B3/A/C2/A1/A2/C axes cited in the 8 encircled regions. The walk ingested its own descriptive output as if it were new semantic content, so it re-lit almost every lane that vocabulary touches (litReality=115/144).
The semantic pull: No code strings exist in this diff to ground the walk (docsOnly=true, 'no semantic-file diff'). prewalkOverlap=0 confirms the gzip-NCD reef seed found zero grounding before the walk even ran — meaning the 115 lit reality cells came almost entirely from the ballistic walk expanding against the commit-page HTML's self-referential lattice-glossary text (grid/route/topology/power-flow language matching B3,A▸C2,C and B3,A1▸C2,A3; capital/floor/dollar language matching A,A2▸C,B1 and A1,A2▸A3,B1; governance/law language matching C,A▸A2,C), not against any real work.
Intent–reality gap: The commit message claims a bare publish chore ('chore(commit-page): publish e5c2ecb1f', no ask, no lane declared) but the receipt measured that publish landing across 115/144 lattice cells spanning grid topology, capital budgeting, and governance law — domains the publish action never touched.
- Locate the exact ingest call that reads diff content into the reef seed (scripts/pmu/pipeline.mjs) and add an exclusion for public/commit/**/*.{html,png}
- Verify docsOnly is currently telemetry-only (this event proves it did NOT suppress ingestion) — wire it to actually gate walk-seeding, not just annotate the receipt row
- Add tests/pmu-simulator regression test asserting docsOnly commits keep litReality within a small multiple of litIntent (e.g. <=5x), failing on the 115x-style saturation seen here
- Audit .thetacog/pipeline-gate-trips.ndjson for other docsOnly commit-page publishes with offPct>90 to size how many past events share this exact mechanism
- Add public/commit/**/* to the owned-surface glob of whichever room actually runs the commit-page publish pipeline (not Terminal Voice's book/blog globs) in .workflow/rooms/*.html, so future publish events attribute correctly instead of surfacing under an unrelated room
What we learned: docsOnly is already computed as a receipt field but is not wired to any ingest-time behavior — a self-generated commit-page publish can walk-saturate against its own descriptive lattice vocabulary even though the pipeline already knows (docsOnly=true) that there's no real content to seed from. The flag exists; the guard using it does not.
The missing guard (the deliverable): A test asserting: for any commit where 100% of changed paths are under public/commit/**/ (self-generated publish artifacts) and docsOnly=true, litReality must not exceed litIntent by more than a small bounded ratio (e.g. 5x) — fails loudly if a publish-only commit saturates the walk the way this one did (115 vs 1).
Detector probe: signal attribution — gzip reef 15% · ballistic walk 85%. Saturated — 115/144 lit cells (80% lattice coverage) from a single asset-only publish is far beyond right-sized breadth for that action; the walk needs an intent-fenced early stop: halt expansion once walksReality exceeds walksIntent by a fixed multiple (e.g. 10x) rather than continuing to full spread. Experiments: Re-run this exact commit's ingest with public/commit/**/*.html excluded from the seed corpus; measure whether litReality drops from 115 toward single digits · Add the walksReality/walksIntent ratio cap (10x) and re-run the last 14 days of docsOnly commit-page publishes; measure how many of their encircled regions survive the cap vs today's 8 · Strip PMU/lattice-glossary words (grid, route, topology, leverage, power flow, governance) from the gzip baseline dictionary specifically for docsOnly-flagged commits and measure whether their offPct drops below the 15 thresholdMeasured outcome (deterministic, not self-graded): room mean offPct —→64 over 6 commits since
Left unfixed, every routine docsOnly commit-page publish keeps registering as a 96%-off-lane breach, inflating this lane's measured loss-ratio with false-positive noise rather than real drift; premium is restored by excluding self-generated commit-page HTML from walk ingestion so the gate only trips on genuine intent-vs-reality divergence.
Open the signed attestation →2026-07-14 · 📐 architect · offPct 26
feat(pmu): pin the numbers we say out loud — and gate them
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 26→42 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 32
fix(outreach): the identity fence — I sent the enterprise pitch to carriers and brokers
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 20→60 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 36 · mistagged
docs(marsh): the 30-minute agenda — and the one line that would unravel the room
Why it left the lane: The diff is entirely a new file, docs/outreach/accounts/marsh-agenda.md, built from client-facing meeting-logistics language: 'Attendees: Paul Denny... Mike Carls... Carlos Dias', 'What this call is... What it is not: a pitch', 'There is nothing to buy in this meeting and no price will be discussed', 'hand the demo to anyone on your team'. That vocabulary is comms/outreach semantics (audience, agenda, objection-handling, scheduling) with zero overlap to architect's owned semantics (book/design-doc/strategy). docs/outreach/ is explicitly listed as messages-network.html's owned surface, not vscode-architect.html's — so the walk's reality mass landed squarely in network's declared territory while the commit's Originating-Terminal trailer staked the architect claim.
The semantic pull: Every load-bearing noun in the file ('Attendees', 'agenda', 'call', 'demo', 'meeting') is outreach-room vocabulary; there is no strategy-doc or book-manuscript vocabulary anywhere in the 84 added lines. The pull isn't ambiguous or borderline — it's a single-file commit whose entire content-class sits in one room's owned glob (network's docs/outreach/) while being trailer-tagged to a different room (architect) that owns none of it.
Intent–reality gap: The commit trailers claim 'Originating-Terminal: 📐 architect' but list 'Relevant-Rooms: ☕ network, 🎩 operator, 🔒 vault' — architect isn't even named as relevant by the commit's own metadata. The receipt is scoring this event against architect's owned-surface lane, but the only file touched (docs/outreach/accounts/marsh-agenda.md) is owned by network. The gap is self-declared in the commit message itself, not something the receipt had to infer.
- Patch the receipt/lane-resolution step (wherever room-for-offPct is computed) to prefer file-glob-owned-room over the Originating-Terminal trailer
- Add the CLAUDE.md clarifying sentence distinguishing Originating-Terminal (physical) from lane-scoring room (file-ownership)
- Backfill-check the architect room's other 17 out-of-lane events in the last 14 days for the same Originating-Terminal-vs-file-ownership mismatch pattern before treating the room's offPct trend (12→33) as genuine scope creep
- Add a pre-commit or post-commit warn (non-blocking) when Originating-Terminal's owned globs match zero changed files but another room's globs match all of them
- Cross-check vscode-architect.html's owned-surface list stays exactly book/design-doc/strategy with no accidental docs/outreach overlap
What we learned: The room attached to a drift event is currently the self-reported Originating-Terminal trailer, not a computed fact from file ownership — and operators write content from whatever terminal they're physically in, not whatever room owns the content. This decouples 'where the operator sat' from 'whose lane the work landed in', and the receipt has been conflating the two. Prior lessons for this room were facts-only with no mechanism; this is the first pass that identifies WHY architect's offPct trend may be inflated: self-reported terminal location, not actual scope drift.
The missing guard (the deliverable): A guard that fails (or warns) when a commit's Originating-Terminal room's owned-surface globs match none of the changed files while a different room named in Relevant-Rooms matches all of them — this is exactly the self-contradiction present in this commit's own trailers and should be catchable before the receipt renders.
Detector probe: signal attribution — gzip reef 70% · ballistic walk 30%. litIntent=125 and litReality=123 out of a 144-cell lattice is ~87% lit on both sides — the walk is close to saturating the lattice rather than staying selective, which compresses the discriminating signal (everything looks lit, so the 36% off-lane share is riding on a nearly-full map). Concrete adjustment: lower --max-depth/ply budget for single-new-file docs-only commits like this one so the walk stops before near-total saturation and the lane signal stays legible. Experiments: Re-run this sha's receipt with docs/outreach/**/*.md added as an explicit reef seed corpus tag distinct from docs/strategy/**/*.md, and measure whether prewalkOverlap rises when outreach vocabulary is matched against an outreach-tagged intent lane instead of architect's strategy-tagged one · Compare prewalkOverlap across the room's last 18 out-of-lane events, split by whether Originating-Terminal's owned globs match the changed files or not — test whether the mistagged subset accounts for most of the offPct inflation · Lower --max-depth specifically for docsOnly=true, single-new-file commits and re-measure litIntent/litReality to see if the walk stays under ~60% saturation instead of ~87%Measured outcome (deterministic, not self-graded): room mean offPct 25→28 over 8 commits since · dictionary ablation saved 928B
This event nudges architect's loss-ratio up on paper (18 out-of-lane events/14 days, trend 12→33), but if the mechanism here is lane-attribution rather than genuine scope drift, the premium is restored by fixing room-resolution to file-ownership — which should retroactively clear a meaningful share of the room's flagged history rather than requiring the operator to change how or where they write outreach content.
Open the signed attestation →2026-07-14 · 🔒 vault · offPct 27
feat(hive/track): alert emails only for real Chrome traffic; log everything
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→27 over 5 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 23
docs(outreach): spec + burndown, emailed
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 27→23 over 7 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 42
docs(marsh): 'infinite resolution' — the instinct is right, the wording would kill him
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 26→26 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 25
feat(outreach): the on-accept template — show the receipt for our own machine work
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 17→27 over 4 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 30
docs(marsh): the OUTLET, not the corner — restore the five facts, add the forwardable paragraph
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 25→24 over 6 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 17 · mistagged
docs(marsh): the committee dossier — and the honest answer to the 30% question
Why it left the lane: 100% of the diff (97 insertions) lands in docs/outreach/accounts/marsh.md — a path explicitly owned by the network room ('docs/outreach/, scripts/outreach/ — outreach scripts and tribe-blast campaigns', .workflow/rooms/messages-network.html:547), not by architect. The vocabulary itself ('Marsh', 'FINPRO', 'Denny', 'placed premium', 'committee dossier', 'underwriter') is sales/outreach-domain language with near-zero overlap to architect's owned strategy/product globs, which is why prewalkOverlap is only 9 of 132 lit-intent cells (~7%) — the reef seed itself barely grounds this text to architect before the walk even runs.
The semantic pull: Terms like 'FINPRO US', 'placed premium', 'broker', 'underwriter', 'committee dossier' and the file path docs/outreach/accounts/marsh.md pull the reality mass toward the network/operator outreach coords; nothing in the diff touches docs/strategy/, docs/03-product/, or docs/01-business/strategy/ — architect's actual owned surface never appears as content.
Intent–reality gap: The commit's Originating-Terminal trailer claims architect as the room, but the commit's own Relevant-Rooms trailer already names network first (☕ network, 🎩 operator, 🧪 laboratory) — the operator's own bookkeeping shows they knew this wasn't architect work. The drift receipt's offPct is scored against architect anyway because it keys off Originating-Terminal, not the file-glob-verified home room.
- Patch the drift-receipt lane-assignment step (wherever it selects which room's owned-surface glob to diff offPct against) to compute file-glob membership across all 9 .workflow/rooms/*.html 'Owned file/dir surface' lists first, and only fall back to Originating-Terminal when no glob matches any changed file.
- Re-run the receipt for acfdb660b against network's owned surface (docs/outreach/) instead of architect's and confirm offPct drops under 15 — this is the cheap falsification test for the whole hypothesis.
- Add a regression test asserting: any commit whose changed files are 100% inside one room's owned glob is never scored against a different room's offPct threshold, even when Originating-Terminal differs.
- Audit the other 15 out-of-lane events logged for architect in the last 14 days for the same terminal-vs-glob mismatch before assuming they're genuine architect-scope drift.
What we learned: CLAUDE.md already documents and PERMITS Originating-Terminal/Relevant-Rooms divergence as normal operator behavior (sit in one terminal, do another room's work) — but the drift-receipt pipeline apparently still gates offPct/lane threshold off Originating-Terminal alone, so a documented-benign divergence is being scored as drift. This is a receipt-calibration bug, not an operator-discipline bug — distinct from the prior three facts-only interventions for this room, none of which identified that the lane assignment itself, not the work, might be wrong.
The missing guard (the deliverable): tests/pmu-simulator/lane-uses-glob-not-terminal.test.js — asserts that for any commit, the room used as the offPct/lane-threshold denominator is determined by matching changed files against every room's 'Owned file/dir surface' glob (i.e. Relevant-Rooms), and fails if Originating-Terminal alone is used as the sole lane when a different room's glob matches 100% of the changed files.
Detector probe: signal attribution — gzip reef 65% · ballistic walk 35%. Right-sized: litIntent 132 vs litReality 128 is a tight, symmetric spread with no sign of shallow cutoff or runaway saturation. No depth adjustment needed here — the signal to chase is the low prewalkOverlap, i.e. reef seed grounding, not walk parameters. Experiments: Recompute the acfdb660b receipt with network (not architect) as the intent lane and confirm offPct falls below 15 — validates that lane-selection, not content, was the defect. · Run reef-enrich to strengthen the outreach-account-dossier vocabulary cluster (Marsh/FINPRO/underwriter/placed-premium/committee) under network's reef slice, then re-measure prewalkOverlap on the next docs/outreach/accounts/*.md commit to see if it rises. · Ablation-test excluding docs/outreach/** entirely from any non-network room's offPct denominator across the last 14 days of architect events, and measure how many of the 16 logged out-of-lane events disappear.Measured outcome (deterministic, not self-graded): room mean offPct 25→27 over 8 commits since · dictionary ablation saved 598B
This event is a false claim against architect's loss ratio, not a real one — its lane's premium should be restored the moment the receipt is recomputed against network's owned docs/outreach/ surface instead of Originating-Terminal, with no change needed to the underlying work.
Open the signed attestation →2026-07-14 · 📐 architect · offPct 49
chore(self-prompt): sp-070 — send securities-counsel red-line memo tomorrow 09:00 ET (GCal 52l6ru3i)
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 15→21 over 8 commits since
Open the signed attestation →2026-07-14 · 📐 architect · offPct 60
feat(outreach): reception is IN — 5 clicked, and a measured law about addresses
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 23→22 over 12 commits since
Open the signed attestation →2026-07-14 · 🎤 voice · offPct 35
feat(bookclub): immortal hold — a forgotten pause can no longer kill the cadence
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 31→33 over 5 commits since
Open the signed attestation →2026-07-14 · 🧪 Cursor Laboratory · offPct 96
chore(commit-page): publish 103656281
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct —→7 over 3 commits since
Open the signed attestation →2026-07-14 · 🎤 voice · offPct 36
fix(bookclub): sink runs must NOT write the live idempotency ledger
Why it left the lane: (sensemaking unavailable — facts-only intervention)
Measured outcome (deterministic, not self-graded): room mean offPct 34→0 over 3 commits since
Open the signed attestation →