fix(comms): receipt emails shipped panels from TWO different renders — 'the wrong panels are in that email'

Operator caught it. He is right, and it is the worst class of bug we can have.

Receipt emails assembled their panel set by globbing a temp render dir. Concurrent
renders write there with a per-run suffix, so a SINGLE SENT EMAIL carried:

  trip-tolerance-3fe7640cd-mrjzb4za.png   run mrjzb4za
  trip-intent-3fe7640cd-mrjzb4za.png      run mrjzb4za
  trip-encircled-3fe7640cd-mrjzb574.png   run mrjzb574   <- A DIFFERENT RENDER

The encircled overlay did not correspond to the grid printed beside it. Same defect
in the latest drift-watch (mrk0j2bq for six panels, mrk0j2i7 for encircled). We shipped
a receipt whose own panels disagreed with each other — to the exact audience whose only
reason to believe us is that the receipt is a reproducible function of ONE commit.
Not a crash. A LIE, in the artifact that IS the product.

THE FIX (operator's call, and it dissolves the race instead of patching it): never
assemble a set — READ the one that was atomically published. public/home-panels/ already
holds exactly one coherent set, manifested by latest.json {"sha":"9788c7a2a","slots":7}:
intent · reality · delta · tolerance · encircled · raw-intent · raw-reality. That is what
the front page serves at thetadriven.com/home-panels/latest-*.png?v=<sha>. The email now
carries THAT — the same seven bytes the public can see — and links to it as the latest
receipt we publish (github.com/wiber/thetacog-mcp).

scripts/pmu/latest-receipt-set.mjs is now the ONE place that answers 'which panels go in
this email'. It REFUSES an incomplete set rather than degrading: a partial receipt is
indistinguishable from a complete one to the person receiving it, so silently sending
five of seven panels is the same failure wearing a different mask.

GUARD: tests/comms/receipt-panel-set-coherent.test.js — parses the ledger's own attachment
names and turns red if any email sent from here on carries panels from more than one render
of a commit. It reproduces the historical mismatch first (measure, don't assume), so the
guard is proven to bite before it is trusted. 6 tests green.

Originating-Terminal: 📐 architect
Relevant-Rooms: 🧪 laboratory, 🎤 voice, 🔨 builder
Story: Mid-way through building the outreach target list, the operator flagged the wrong panels in a live email. Stopped the list — a wrong receipt discredits every other artifact we have shipped this week, and we are days from putting this in front of underwriters. Laboratory owns the render, voice owns the send path, builder owns the publish step that produces the one coherent set.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EssMgKix9aZmZ5dxGPqYCW

commit 6654832dd — 144×144 lattice triptych (on-chip)

◎ the ingest chose B2,C3 — Tactics·Deal × Operations·Flow — acting on B,C3 — Tactics × Operations·Flow (grip 0.781) · the walk starts at the ACTOR's row · 2 file(s)

⏱ ingest 574.3ms (corpus→lattice) · definer walk 711ms (row→transpose→row, ballistic XOR per hop) · total 1548ms
ingest here = commit-scoped SENSING only (this commit's message + changed files → lit anchors) — deep seed authoring lives in the reef-self-loop, off the commit path

rows = ACTOR (lens) · cols = PATIENT (object) · diagonal = self-reference; ◎ at actor-row × patient-col — every panel, same orientation. Heat above the diagonal = actors ranking ShortLex-earlier than their patients (the walk follows definers uphill in rank).
The 12 canonical lanes (rows top→bottom, cols left→right): A·Strategy · B·Tactics · C·Operations · A1·Law · A2·Goal · A3·Fund · B1·Speed · B2·Deal · B3·Signal · C1·Grid · C2·Loop · C3·Flow

PAIR LATTICE (the map we normally see)

PRE-WALK SENSE · INTENT grid — the snapshot, no point of view

the no-point-of-view snapshot — what the sensor lit before any walk; the leaf walk below is what bridges the two grids

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

PRE-WALK SENSE · REALITY grid — the snapshot, no point of view

the no-point-of-view snapshot, reality side — same sensor law

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

PRE-WALK Δ · straight comparison of the two ingested grids (green both · cyan intent-only · amber reality-only) · 4% overlap · ◎ = where the competence pixel sits in the raw overlap

good = green overlap without being a copy — near-100% is self-similarity, not alignment

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

◎ the pixel this commit belongs to

B2,C3 — Tactics·Deal × Operations·Flow (actor) acting on B,C3 — Tactics × Operations·Flow (patient) · grip 0.781

actor seed B2,C3 — Current negotiation rates for a deal determine the flow throughput and delivery rate of the finished value. The deal sets the exchange rate between two value substrates. Mis-priced exchange is a slow-bleed; correctly priced exchange compounds both sides, because each cycle of trade enriches the bench on both ends. Terms are the API between two organizations — every clause is a contract method that survives the handshake. Renegotiation is the breaking change; the deal is the stable interface either side can build against. Negotiation closes at the moment both parties' BATNAs cross. Push past that point and you've bought regret at retail; stop short and you've left margin on the table that the next deal will not return to you. A signed counterparty is more valuable than an unsigned promise. The signature is the substrate; the conversation that preceded it is the exhaust the signature converted into substrate. Flow is the rate at which committed work crosses the finish line. Inventory accumulates upstream; flow is the only thing the customer pays for, and the only thing the operator can measure honestly. Movement is the irreversible delivery of value across the boundary. Anything stationary is cost; anything moving is either revenue, deferred revenue, or the exhaust of revenue not yet realized. Throughput dominates utilization. A ninety-nine-percent utilized system at low throughput pays the same wages as a fifty-percent utilized system at twice the throughput, but the second one ships the customer's order. Flow has a direction. Bidirectional flow is two flows, each measured separately; calling them a single flow hides the chokepoint and the chokepoint is where the leverage lives.

patient seed B,C3 — Timing and leverage maneuvers in tactics accelerate the flow rate and delivery throughput of the finish. Flow is the rate at which committed work crosses the finish line. Inventory accumulates upstream; flow is the only thing the customer pays for, and the only thing the operator can measure honestly. Movement is the irreversible delivery of value across the boundary. Anything stationary is cost; anything moving is either revenue, deferred revenue, or the exhaust of revenue not yet realized. Throughput dominates utilization. A ninety-nine-percent utilized system at low throughput pays the same wages as a fifty-percent utilized system at twice the throughput, but the second one ships the customer's order. Flow has a direction. Bidirectional flow is two flows, each measured separately; calling them a single flow hides the chokepoint and the chokepoint is where the leverage lives. Tactics is the choice of which leverage to pull at which beat. Not what we want, but how the want lands on Tuesday: the sequence of irreversible commitments, each made before the next one's information is available. Speed of feedback dominates speed of execution. Tactics that converge fast beat tactics that compute long, because the loop closes around the world's response before the world has moved. The tactical map is a ranked list of moves where each move carries a cost-of-delay. Pick the move whose cost of doing it tomorrow exceeds the cost of doing it imperfectly today. Execution is a sequence of bets made under uncertainty. Tactics is the discipline of betting the right size on the bet whose information value pays for the loss-if-wrong.

INTENT · leaf-walk clouds · BLUE→VIOLET by ply (◎ = the competence pixel: actor∩patient)

good = the clouds concentrate where the commit SAYS it works

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

REALITY · leaf-walk clouds · ORANGE→RED by ply (◎ = the same pixel — the shared perspective)

good = the same clouds as intent — shipped where declared

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

DELTA · graded cloud divergence (green agree · magenta declared-not-done · amber done-not-declared) · 2% agree

good = mostly green; magenta = said-not-done (chase it in the code), amber = done-not-said (chase it in the docs)

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

TOLERANCE · cloud topology (dim green in-shape · hot amber bleed · red orthogonal concentration) · ⚠ TOO MANY

red only matters above the flip — a few amber is normal bleed

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

SHORTLEX-3 PROJECTION (ABC · A1..C3 · the 132 children — candidate, pre-ratchet)

PROJECTED INTENT · the commit’s claims, head→axis_i tail→axis_j (cyan)

the three-length view — good = claims land inside their own zone

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

PROJECTED REALITY · same projection law (amber)

same projection law — good = reality occupies the zones intent does

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

STRAIGHT COMPARISON · green both · cyan intent-only · amber reality-only · 7% overlap

good = the zones agree; cross-zone scatter is the drift to read

	ABC A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N A1–C3
ABC A1–C3 A1A–O A2A–O A3A–O B1A–O B2A–O B3A–O C1A–N C2A–N C3A–N

shortlex-3 zone occupancy (lit cells per diagonal square)
INTENT: 3 in the 3×3 ABC corner · 13 in the 9×9 A1..C3 square · 2054 in the 132×132 children square · 469 cross-zone
REALITY: 0 in the 3×3 ABC corner · 6 in the 9×9 A1..C3 square · 854 in the 132×132 children square · 137 cross-zone
axes: identical 144 ShortLex names both sides (symmetric); weights asymmetric
zone 3 = candidate children, pre-ratchet (repo-derived dumps not yet past the perturbation-probe gate) · intent 54 claims @ θ 0.625 · reality 24 claims @ θ 0.625 · projection 513ms

SHAPE-MATCH σ = -0.13 — the real intent↔reality definer walk vs random-reality (actual 0.0481 vs random 0.054). >0 = the walk distinguishes real alignment from noise; aggregate over independent walks → the divergent series.
σ_spec-delta · noise · no measurable relation between the work and the declared spec

Most out-of-lane row: A · Strategy — that lane is drifting most (read the red band in that row).

Three-colour tolerance (out-of-lane = reality fires where intent is weak, in orthogonal blocks): green=in-lane agreement · amber=a few out-of-lane (tolerated) · red=FIRED — orthogonal out-of-lane 27% vs tolerance 25%.
499 green · 683 amber · 444 red · 119 XOR-friction cells.

Both axes = the 144 ShortLex anchors, cell=row⊕col, on the chip. INTENT=docs+rules · REALITY=code · DELTA=friction.

tile dump — what the SimHash matched on the diagonal (inspect the sensor; tap to expand)

A,A The lattice we build today is what next year's underwriter inherits.

intent 70% fix(comms): receipt emails shipped panels from TWO different renders — 'the wrong panels are in

reality 73% name: `latest-${slot}.png`,

B,B Tactics is the choice of which leverage to pull at which beat.

intent 77% (no distinctive match)

reality 78% // the receipt is a reproducible function of one commit. This is the worst class of bug we can

C,C Operations is the loop that runs whether anyone watches.

intent 81% ## REQUIREMENTS (falsifiable) - **R1 — reef-from-spec.** A command that compiles an arbitrary m

reality 75% (no distinctive match)

A1,A1 EU AI Act Article 14 requires human-on-the-loop oversight, with the supervisor able to interrupt the system at

intent 83% (no distinctive match)

reality 75% (no distinctive match)

A2,A2 The target is the cell coordinate the system MUST occupy by end-of-quarter.

intent 80% (no distinctive match)

reality 75% export function latestReceiptSet() {

A3,A3 Every dollar builds either the floor (substrate that lifts future bets) or the ceiling (cap on the next round)

intent 75% (no distinctive match)

reality 73% const DIR = resolve(REPO, 'public/home-panels');

B1,B1 Latency is the price of a missed beat.

intent 72% (no distinctive match)

reality 72% catch (e) { return { ok: false, reason: `unreadable manifest: ${e.message}` }; }

B2,B2 The deal sets the exchange rate between two value substrates.

intent 75% (no distinctive match)

reality 83% (no distinctive match)

B3,B3 Signal-to-noise is the inverse cube of bandwidth — narrow the channel, the message arrives; broaden it, recipi

intent 75% (no distinctive match)

reality 70% if (import.meta.url === `file://${process.argv[1]}`) {

C1,C1 Power flows where the grid lets it.

intent 73% (no distinctive match)

reality 70% // THE FIX — never assemble a set; READ a published one.

C2,C2 Each iteration is a hypothesis tested against the ground truth of the world.

intent 73% (no distinctive match)

reality 73% (no distinctive match)

C3,C3 Flow is the rate at which committed work crosses the finish line.

intent 77% (no distinctive match)

reality 72% (no distinctive match)

commit context — 2 file(s)

fix(comms): receipt emails shipped panels from TWO different renders — 'the wrong panels are in that email'

Operator caught it. He is right, and it is the worst class of bug we can have.

Receipt emails assembled their panel set by globbing a temp render dir. Concurrent
renders write there with a per-run suffix, so a SINGLE SENT EMAIL carried:

  trip-tolerance-3fe7640cd-mrjzb4za.png   run mrjzb4za
  trip-intent-3fe7640cd-mrjzb4za.png      run mrjzb4za
  trip-encircled-3fe7640cd-mrjzb574.png   run mrjzb574   <- A DIFFERENT RENDER

The encircled overlay did not correspond to the grid printed beside it. Same defect
in the latest drift-watch (mrk0j2bq for six panels, mrk0j2i7 for encircled). We shipped
a receipt whose own panels disagreed with each other — to the exact audience whose only
reason to believe us is that the receipt is a reproducible function of ONE commit.
Not a crash. A LIE, in the artifact that IS the product.

THE FIX (operator's call, and it dissolves the race instead of patching it): never
assemble a set — READ the one that was atomically published. public/home-panels/ already
holds exactly one coherent set, manifested by latest.json {"sha":"9788c7a2a","slots":7

scripts/pmu/latest-receipt-set.mjs
tests/comms/receipt-panel-set-coherent.test.js

Produced on the chip by the running pipeline (scripts/pmu/pipeline.mjs → runPipeline → walk + xor), commit-scoped · on-chip per-walk 636.99ns (this commit). Recompute: node scripts/pmu/commit-triptych.mjs --commit 6654832dd

Commit artifacts (open on a computer — Gmail mobile won't follow file:// links; the inline images above are the phone-viewable form): reef grid · this triptych · the HDL — all three are also attached to this email.