feat(pmu): name every encircled coordinate + encircle ALL emails (both, LLM-free)

Operator: 'we need both encircled on all emails AND dig out the 3-levels-deep ShortLex translation of
what a1 etc means — b3 needs their category names; what I asked for was not found.' They were right —
coordGist returned EMPTY for every axis and the registry semantics were all blank, so a coordinate on the
map had no name.

(1) NAMES: new scripts/pmu/shortlex-names.mjs — the canonical, LLM-FREE axis→category translator. Depth 1/2
are the tesseract axes (A=Strategy, A1=Strategy.Law, B3=Tactics.Signal, C3=Operations.Flow — from CLAUDE.md);
depth-3 children (A1A…) get a systematic parent-derived name (Strategy.Law·A) until the registry's phase-2
GDD semantics fill the 132 real names. coordName('A1,B3')='Strategy.Law × Tactics.Signal'. Wired into every
receipt region line — verified: the render now shows Strategy.Law / Tactics / Operations next to each coord.

(2) ENCIRCLED ON ALL EMAILS: a 0-region tolerance is NOT a black square for a direction-only commit — it
carries the ◎ direction pixel. Now it renders as a direction-only headline (the panel + a 'DIRECTION-ONLY'
note, no rings) instead of being suppressed; only a truly all-dark tolerance is skipped. So every receipt
carries the shape.

Guards: shortlex-names.test.mjs (canonical + LLM-free), encircled-on-all-emails.test.mjs (direction fallback
+ name-per-region). Honest scope: the 132 depth-3 SEMANTIC names are still the registry's phase-2 GDD work.

Originating-Terminal: 🔨 iTerm Builder
Relevant-Rooms: 🔨 builder, 🧪 laboratory, ☕ network
Story: The encircled map finally SAYS what each coordinate means, deterministically, on every email.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013BUf5M5p42Zw73VaGt33ZL

commit 8a88e9ed6 — 144×144 lattice triptych (on-chip)

◎ the ingest chose A,A3 — Strategy × Strategy·Fund — acting on B1,A1 — Tactics·Speed × Strategy·Law (grip 0.797) · the walk starts at the ACTOR's row · 10 file(s)

⏱ ingest 511.4ms (corpus→lattice) · definer walk 622ms (row→transpose→row, ballistic XOR per hop) · total 1531ms
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) · 5% 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

A,A3 — Strategy × Strategy·Fund (actor) acting on B1,A1 — Tactics·Speed × Strategy·Law (patient) · grip 0.797

actor seed A,A3 — A strategy lattice frames how capital and the dollar floor fund long-horizon finance across the substrate. The lattice we build today is what next year's underwriter inherits. We set the substrate that downstream pricing rides on, and that choice is paid back across every quarter we keep operating. Direction is what you keep when you forget the calendar. Multi-year posture, irreversibly chosen, defines the boundary every quarter renegotiates inside. Strategy is the bearing the rotation is measured against. Every dollar builds either the floor (substrate that lifts future bets) or the ceiling (cap on the next round). Allocation is which one this dollar chooses, and the choice is irreversible by the time the wire clears. Burn rate divides into substrate-building and exhaust. Substrate compounds; exhaust evaporates by quarter-end. The investor who pays for substrate is buying a different asset than the investor who pays for exhaust.

patient seed B1,A1 — Speed limits are constrained by the binding mandate and governance rule of law within the beat. EU AI Act Article 14 requires human-on-the-loop oversight, with the supervisor able to interrupt the system at any moment. Compliance attaches to the artifact the artifact cannot escape — provenance is a regulatory primitive, not a feature. Constraints precede objectives. The cap-table, the license text, the consent envelope — each draws the inviolate line the action must respect, and the line is enforced before the optimization runs. A rule names what the system MAY NOT do. If the agent can do X, then 'forbid X' is not the constraint — it is wishful thinking dressed as policy. Constraints live in the gate, not in the prompt. Latency is the price of a missed beat. Every hundred milliseconds of round-trip turns a parallel race into a stalemate, because the first arrival sets the rules the second arrival has to honor. Throughput compounds: doubling the rate doubles the surface area where serendipity can hit. A pipeline at twice the velocity is not twice as productive — it is exponentially more lucky. Time-to-first-byte is the only number the operator feels at the wheel. Optimize the felt latency before the raw throughput; the operator's grip on the loop is what drives the loop forward.

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) · 3% 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)

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 · 5% 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: 0 in the 3×3 ABC corner · 8 in the 9×9 A1..C3 square · 941 in the 132×132 children square · 244 cross-zone
REALITY: 1 in the 3×3 ABC corner · 4 in the 9×9 A1..C3 square · 2071 in the 132×132 children square · 221 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 24 claims @ θ 0.625 · reality 23 claims @ θ 0.6094 · projection 1647ms

SHAPE-MATCH σ = -1.05 — the real intent↔reality definer walk vs random-reality (actual 0.0716 vs random 0.104). >0 = the walk distinguishes real alignment from noise; aggregate over independent walks → the divergent series.
σ_drift · noise · below zero — this read is noise, not a measurement

Most out-of-lane row: C3 · Flow — 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=armed — orthogonal out-of-lane 14% vs tolerance 25%.
805 green · 1289 amber · 0 red · 43 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 75% (no distinctive match)

reality 72% This change operates in the blog content domain, involving og image encircled panel needs. This

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

intent 75% (no distinctive match)

reality 72% B1: 'Tactics.Speed', B2: 'Tactics.Deal', B3: 'Tactics.Signal',

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

intent 77% (no distinctive match)

reality 77% if (m && L2[m[1]]) return `${L2[m[1]]}·${m[2]}`; // systematic child descriptor until GDD-named

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

intent 80% (no distinctive match)

reality 73% (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 72% (no distinctive match)

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

intent 80% (no distinctive match)

reality 72% // never fabricated. Fill data/pmu/shortlex-144-registry.json semantics to name them.

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

intent 77% (no distinctive match)

reality 70% (no distinctive match)

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

intent 78% (no distinctive match)

reality 72% (no distinctive match)

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

intent 67% (no distinctive match)

reality 72% // • Depth 3 (A1A..C3N, 132 children) have concept-dumps but no clean names yet (shortlex-regis

C1,C1 Power flows where the grid lets it.

intent 70% (no distinctive match)

reality 69% (no distinctive match)

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

intent 73% (no distinctive match)

reality 67% (no distinctive match)

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

intent 81% (no distinctive match)

reality 72% (no distinctive match)

commit context — 10 file(s)

feat(pmu): name every encircled coordinate + encircle ALL emails (both, LLM-free)

Operator: 'we need both encircled on all emails AND dig out the 3-levels-deep ShortLex translation of
what a1 etc means — b3 needs their category names; what I asked for was not found.' They were right —
coordGist returned EMPTY for every axis and the registry semantics were all blank, so a coordinate on the
map had no name.

(1) NAMES: new scripts/pmu/shortlex-names.mjs — the canonical, LLM-FREE axis→category translator. Depth 1/2
are the tesseract axes (A=Strategy, A1=Strategy.Law, B3=Tactics.Signal, C3=Operations.Flow — from CLAUDE.md);
depth-3 children (A1A…) get a systematic parent-derived name (Strategy.Law·A) until the registry's phase-2
GDD semantics fill the 132 real names. coordName('A1,B3')='Strategy.Law × Tactics.Signal'. Wired into every
receipt region line — verified: the render now shows Strategy.Law / Tactics / Operations next to each coord.

(2) ENCIRCLED ON ALL EMAILS: a 0-region tolerance is NOT a black square for a direction-only commit — it
carries the ◎ direction pixel. Now it renders as a direction-only headline (the panel + a 'DIRECTION-ONLY'
note, no rings) instead of being s

docs/comms/self/approved/2026-07-05-cleartext-capital.grade.json
docs/comms/self/approved/2026-07-05-cleartext-capital.md
docs/comms/self/approved/2026-07-05-cleartext-chat-send.grade.json
docs/comms/self/approved/2026-07-05-cleartext-chat-send.md
docs/comms/self/approved/2026-07-05-cleartext-enterprise.grade.json
docs/comms/self/approved/2026-07-05-cleartext-enterprise.md
docs/comms/self/approved/2026-07-05-cleartext-gtm.grade.json
docs/comms/self/approved/2026-07-05-cleartext-gtm.md
docs/comms/self/sent/2026-07-05-cleartext-capital.grade.json
docs/comms/self/sent/2026-07-05-cleartext-capital.md

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

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.