feat(outreach): the on-accept template — show the receipt for our own machine work

CRO ghost-read of the old email produced four deal-killing questions and a delete.
Each question is a committee, and a committee is a slower death than a no:
  1. 'Sender is hello@ — I connected with Elias, not his marketing software.'
  2. 'What is npx? I haven't opened a terminal in fifteen years.' → Engineering → backlog
  3. 'Is this a SaaS sucking up my procurement data?' → CISO murders it
  4. 'Am I the buyer or the seller here?' → can't place self → forwards to nobody
  5. 'What does it cost?' → can't budget → no proposal

ENVELOPE BUG — a fix applied to ONE door is not a fix. e1f45cc8b (today) set the
reader-facing From to Elias for src/lib/emailUtils.ts, and MISSED
scripts/email-artifact.mjs — the path every outreach send actually uses, which still
defaulted to 'ThetaDriven <hello@>'. So the objection was live. Fixed at the second
door; the guard now covers both.

THE FRAME (operator's correction, and it is the better one): the email is FROM ELIAS,
in his voice, under his name — he wrote it and he owns every word. The MACHINE did the
RESEARCH: it read their public position and answered one question — given what this
person is responsible for, what does our thing mean for THEIR desk. And that research
carries a receipt we hand over, recomputable by anyone.

We refuse both easy moves: faking the human (a fragile lie — the moment they suspect
automation they discount everything) and disowning the words ('software wrote this, I
just pressed send' — unaccountable, and it makes the sender a bystander to his own
letter). Instead: a person sends it, a machine researched it, and the audit trail of
the machine is attached. Every other AI-assisted email in their inbox hid the machine.
This one shows its work — which IS the product, running live in their inbox.

Zero-questions structure: command handed to THEIR engineer (never the CRO) ·
zero-exfiltration stated with the mechanism (local binary, your VPC, your iron) ·
exposure denominator + $100k harness + $20/agent-year in the body · ONE audience per
send (a CRO wants agents audited, a broker wants to build coverage — pitching both
makes the reader ask 'am I buyer or seller' and forward to nobody) · the 30% miss rate
kept, because it is the fence that makes the rest credible.

GUARD: tests/outreach/on-accept-template.test.js — both send paths default to a human
From; each of the five questions stays answered; and the three false claims (premium
reduction, MIT/open-source, CATO/certification) can never re-enter the sendable copy.
17 tests green.

Originating-Terminal: 📐 architect
Relevant-Rooms: ☕ network, 🎤 voice, 🔒 vault
Story: The forward-premortem armored the artifacts, but the ghost-read proved the questions were firing upstream of them — in the first email. Network owns the outreach vector, voice owns the send path where the envelope bug hid, vault owns the claim fences the template must never breach.
Persona-Intent: corporate CRO / risk executive — should finish the email with zero unanswered questions, able to forward one line to an engineer and one page to procurement, and should believe the automation disclosure BECAUSE it came with a receipt they can check.

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

commit 9788c7a2a — 144×144 lattice triptych (on-chip)

◎ the ingest chose A,C2 — Strategy × Operations·Loop — acting on B1,C — Tactics·Speed × Operations (grip 0.828) · the walk starts at the ACTOR's row · 3 file(s)

⏱ ingest 323.2ms (corpus→lattice) · definer walk 1611ms (row→transpose→row, ballistic XOR per hop) · total 2124ms
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) · 2% 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,C2 — Strategy × Operations·Loop (actor) acting on B1,C — Tactics·Speed × Operations (patient) · grip 0.828

actor seed A,C2 — Substrates of strategy underwrite the long-horizon lattice for every iterative feedback loop and hypothesis test cycle. 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. Each iteration is a hypothesis tested against the ground truth of the world. Loops shorter than the feedback half-life waste the half-life; loops longer than it pay compounding interest on the wait. 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. Cycles compound when each turn's exhaust feeds the next turn's intake. Closed loops compound; open loops decay. The closing of the loop IS the productivity, not the running of it. Capital lives where strategy is durable. Frame the ten-year shape of the business before optimizing the ten-week sprint; the substrate decisions compound while the surface decisions decay. Iteration discipline: one commit per iteration, never bundled. Bundled iterations destroy the bisect, and the bisect is the future agent's only tool for finding which round of feedback produced which artifact. The strategic question is which doors close on purpose. Anything that keeps every option open until next year has already chosen the option of inaction, paid in optionality cost. A loop that does not learn is a treadmill. The cycle has to update its own model on the way around, or the same lap teaches nothing the previous lap did not already teach.

patient seed B1,C — Tactics Speed as the lens on Operations. 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. Operations is the loop that runs whether anyone watches. The daily commit, the hourly hook, the per-request fingerprint — the substrate of the substrate, ambient and unwatched. Process is what you forget to do; ops is what does itself. Convert manual moves into ambient state, because the tax of remembering compounds faster than the tax of automating. The daily friction is the diff between your intent and your harness. Close the diff or pay the tax twice — once in the slip, once in the apology to the next agent.

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) · 1% 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 · 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: 2 in the 3×3 ABC corner · 9 in the 9×9 A1..C3 square · 1789 in the 132×132 children square · 459 cross-zone
REALITY: 1 in the 3×3 ABC corner · 9 in the 9×9 A1..C3 square · 1574 in the 132×132 children square · 230 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 136 claims @ θ 0.6406 · reality 22 claims @ θ 0.6094 · projection 1347ms

SHAPE-MATCH σ = -0.43 — the real intent↔reality definer walk vs random-reality (actual 0.0501 vs random 0.067). >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: 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=armed — orthogonal out-of-lane 25% vs tolerance 25%.
229 green · 643 amber · 0 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 78% GUARD — the on-accept LinkedIn template reaches ZERO QUESTIONS, and the envelope is a person..

reality 69% (no distinctive match)

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

intent 75% > **[THE SPECIFIC FINDING — 2–3 sentences. Not a factoid proving we looked them up; a CONCLUSIO

reality 64% (no distinctive match)

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

intent 78% > email you got this week hid the machine. This one hands you its audit trail.**

reality 67% (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 80% **What the machine did was the RESEARCH.** Not the writing. Elias pointed his own instrument at

reality 70% // --from-room still wins when explicitly asked for (self/internal sends WANT the room identity

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

intent 80% (no distinctive match)

reality 70% (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% 5. **Never claim a premium reduction.** We don't control the carrier's decision, and *"show me

reality 69% (no distinctive match)

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

intent 77% (no distinctive match)

reality 64% (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 80% > without a witness. When one does something expensive, your team pays senior engineers to do

reality 69% (no distinctive match)

C1,C1 Power flows where the grid lets it.

intent 75% > **For your engineer, not for you.** Don't run anything yourself. Forward one line to whoever

reality 66% (no distinctive match)

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

intent 84% (no distinctive match)

reality 67% (no distinctive match)

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

intent 78% (no distinctive match)

reality 67% (no distinctive match)

commit context — 3 file(s)

feat(outreach): the on-accept template — show the receipt for our own machine work

CRO ghost-read of the old email produced four deal-killing questions and a delete.
Each question is a committee, and a committee is a slower death than a no:
  1. 'Sender is hello@ — I connected with Elias, not his marketing software.'
  2. 'What is npx? I haven't opened a terminal in fifteen years.' → Engineering → backlog
  3. 'Is this a SaaS sucking up my procurement data?' → CISO murders it
  4. 'Am I the buyer or the seller here?' → can't place self → forwards to nobody
  5. 'What does it cost?' → can't budget → no proposal

ENVELOPE BUG — a fix applied to ONE door is not a fix. e1f45cc8b (today) set the
reader-facing From to Elias for src/lib/emailUtils.ts, and MISSED
scripts/email-artifact.mjs — the path every outreach send actually uses, which still
defaulted to 'ThetaDriven <hello@>'. So the objection was live. Fixed at the second
door; the guard now covers both.

THE FRAME (operator's correction, and it is the better one): the email is FROM ELIAS,
in his voice, under his name — he wrote it and he owns every word. The MACHINE did the
RESEARCH: it read their public position and answere

docs/outreach/_template-on-accept-linkedin.md
scripts/email-artifact.mjs
tests/outreach/on-accept-template.test.js

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

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.