docs(claude): standing rule — cc the operator on direct sends, schedule every follow-up, node/key/vector TTL

Three things landed together because the same incident produced all three:
(1) --allow-direct still needs --cc elias@/eliasmoosman@ — five sends today
went out with zero visibility to the operator, and one bounce went unnoticed
until he asked directly. (2) every outreach send now gets a scheduled
follow-up, both a self-prompt AND a calendar event, not one or the other.
(3) codifies the node/key/vector TTL=3 protocol for deciding when a quiet
door is actually dead vs. just needs a different key or vector — rotating
the node itself after one silent attempt is the drift that makes a thesis
read as a vendor fishing for a problem instead of conviction.

Five self-prompts (sp-006..010) + one calendar event (Fri Jul 10, 2-4:30pm ET)
created this session for the actual Dan/Bryan/Jai/Mark/Jamin follow-ups.

Originating-Terminal: 🎩 operator
Relevant-Rooms: ☕ network, 🧭 navigator, 🎩 operator
Story: Direct response to the operator catching the cc gap live and asking
for a standing scheduling rule, not just a one-off fix.

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

commit 114346d7a — 144×144 lattice triptych (on-chip)

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

⏱ ingest 365.3ms (corpus→lattice) · definer walk 621ms (row→transpose→row, ballistic XOR per hop) · total 1124ms
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) · 7% 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,B1 — Strategy × Tactics·Speed (actor) acting on C1,A1 — Operations·Grid × Strategy·Law (patient) · grip 0.797

actor seed A,B1 — Defining a long-horizon strategy frame requires a lattice where speed and tempo beats prevent missed choices. 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. 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.

patient seed C1,A1 — Power flows where the grid lets it. Choose connections before topologies; the topology is what the connections compose, and a connection added later is a topology silently rewritten. Latency is geography expressed in milliseconds. The grid IS the map of where compute meets storage meets bandwidth; the map is the territory at the scale the request actually traverses. Infrastructure decisions are reversible at ten-times the cost of being right the first time. Buy the irreversibility down before you provision the easy decisions, because the easy decisions ride on the irreversible ones. 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.

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) · 5% 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 · 4% 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: 1 in the 3×3 ABC corner · 7 in the 9×9 A1..C3 square · 1544 in the 132×132 children square · 262 cross-zone
REALITY: 0 in the 3×3 ABC corner · 5 in the 9×9 A1..C3 square · 948 in the 132×132 children square · 138 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 121 claims @ θ 0.6406 · reality 2 claims @ θ 0.5781 · projection 689ms

SHAPE-MATCH σ = 1.34 — the real intent↔reality definer walk vs random-reality (actual 0.1559 vs random 0.101). >0 = the walk distinguishes real alignment from noise; aggregate over independent walks → the divergent series.
σ_drift · weak · panel story is not yet evidence

Most out-of-lane row: C1 · Grid — 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 35% vs tolerance 25%.
512 green · 354 amber · 466 red · 438 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 77% **Through-holes (H state in grid):** - Type: UPSIDE-DOWN PYRAMIDS (inverted, point down) - Why:

reality 63% (no distinctive match)

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

intent 75% ### SQL (Central Supabase: `bvhhlosblntckhwyagvp.supabase.co`) | File | Purpose | |---|---| | `

reality 69% (no distinctive match)

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

intent 80% # Claude Code Configuration

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

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

intent 83% (no distinctive match)

reality 67% (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 77% ### DELEGATION NEVER GIT-BRANCHES (HARD RULE — enforced by tests, not by prose) **We NEVER auto

reality 69% (no distinctive match)

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

intent 73% (no distinctive match)

reality 70% (no distinctive match)

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

intent 81% (no distinctive match)

reality 69% (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% ## 👤 CANONICAL INVENTOR / AUTHOR **Name:** Elias Moosman **Email:** elias@thetadriven.com **NE

reality 63% (no distinctive match)

C1,C1 Power flows where the grid lets it.

intent 78% (no distinctive match)

reality 63% (no distinctive match)

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

intent 80% ### MDX FORBIDDEN CHARACTERS **The following CRASH the MDX parser (500 error on blog posts):**

reality 73% (no distinctive match)

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

intent 78% - **NEVER** just substantiate claims - show why the reader should care - **EVERY** section shou

reality 69% (no distinctive match)

commit context — 2 file(s)

docs(claude): standing rule — cc the operator on direct sends, schedule every follow-up, node/key/vector TTL

Three things landed together because the same incident produced all three:
(1) --allow-direct still needs --cc elias@/eliasmoosman@ — five sends today
went out with zero visibility to the operator, and one bounce went unnoticed
until he asked directly. (2) every outreach send now gets a scheduled
follow-up, both a self-prompt AND a calendar event, not one or the other.
(3) codifies the node/key/vector TTL=3 protocol for deciding when a quiet
door is actually dead vs. just needs a different key or vector — rotating
the node itself after one silent attempt is the drift that makes a thesis
read as a vendor fishing for a problem instead of conviction.

Five self-prompts (sp-006..010) + one calendar event (Fri Jul 10, 2-4:30pm ET)
created this session for the actual Dan/Bryan/Jai/Mark/Jamin follow-ups.

Originating-Terminal: 🎩 operator
Relevant-Rooms: ☕ network, 🧭 navigator, 🎩 operator
Story: Direct response to the operator catching the cc gap live and asking
for a standing scheduling rule, not just a one-off fix.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

CLAUDE.md
data/self-prompts.json

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

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.