feat(pmu): the PROJECT altitude — portfolio insurability panel (the missing third receipt)

The insurability signals fired on-PROMPT (lens) and on-COMMIT (triptych) but never at
PROJECT level — the underwriter's actual view. This is what we missed in our own process:
we made it scale-invariant WITHIN a panel (dense↔sparse) but never ACROSS altitudes; every
signal we built got wired to the commit node only. project-portfolio.mjs fills the third node,
scale-invariant with the commit receipt — the SAME encircled tolerance panel + reef-named
coordinates + σ + breach, rolled up over the whole repo, LLM-free and deterministic.

Two ledgers, never a re-render (find the running code):
  • measure-history.ndjson (200 commits) → portfolio σ + BREACH 71.5% (the loss ratio)
  • lens-receipts/*.json (2459 placements) → the whole-repo DRIFT MAP, binned to ShortLex
    blocks, coloured by mean σ, run through the ONE region pipeline (detectRegions → encircle
    → expandCoordName). The project's hot regions come out encircled + named by problem space:
    pmu-walk, symbol-grounding, comms-email, ai-regulation.

Guard (the deliverable): project-portfolio.test.mjs — the rollup yields the underwriter numbers,
the drift map is encircled + reef-named (reuses expandCoordName at project scale), it is
deterministic (same ledgers → same rollup), and it is LLM-free. → docs/pmu/project-portfolio.html.

Still open (the other two altitude gaps): package + enrich the on-PROMPT receipt with the reef
expansion, and a scale-invariance guard asserting each signal fires at all three altitudes.

Originating-Terminal: 🔨 builder
Relevant-Rooms: 🧪 laboratory, 📐 architect, 🎩 operator
Story: the operator asked what we missed — the project altitude — so the whole-repo view now ships the same encircled+reef-named insurability panel the commit does, aggregated deterministically from the two ledgers.

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

commit 16669e6f0 — 144×144 lattice triptych (on-chip)

◎ the ingest chose C1,C — Operations·Grid × Operations — acting on C2,C1 — Operations·Loop × Operations·Grid (grip 0.781) · the walk starts at the ACTOR's row · 5 file(s)

⏱ ingest 850.9ms (corpus→lattice) · definer walk 964ms (row→transpose→row, ballistic XOR per hop) · total 2477ms
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

C1,C — Operations·Grid × Operations (actor) acting on C2,C1 — Operations·Loop × Operations·Grid (patient) · grip 0.781

actor seed C1,C — Infrastructure grid and route topology provide the path for power flow during the daily operations run. 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. A connection between two systems is a contract that outlasts the systems on either end. Wire-protocols outlive the processes they connect; the wire is the substrate, the endpoints are the exhaust. 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. Operations earns its keep by being boring. The day the routine is interesting is the day it has already failed and is being narrated rather than executed.

patient seed C2,C1 — Consistent loop iteration and hypothesis test measures evaluate the efficiency of the infrastructure grid and topology flow. 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. 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. 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.

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 · 3% 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 · 4 in the 9×9 A1..C3 square · 1033 in the 132×132 children square · 225 cross-zone
REALITY: 1 in the 3×3 ABC corner · 2 in the 9×9 A1..C3 square · 779 in the 132×132 children square · 153 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 76 claims @ θ 0.6406 · reality 29 claims @ θ 0.625 · projection 756ms

SHAPE-MATCH σ = -0.27 — the real intent↔reality definer walk vs random-reality (actual 0.0567 vs random 0.065). >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

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 0% vs tolerance 25%.
1057 green · 404 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 70% <div style="color:#8a94a8;font-size:13px;margin-bottom:16px">The whole repo at project altitude

reality 69% // node scripts/pmu/project-portfolio.mjs # write docs/pmu/project-portfolio.html + print stats

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

intent 73% (no distinctive match)

reality 64% import { readFileSync, writeFileSync, readdirSync, mkdirSync, existsSync } from 'node:fs';

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

intent 78% (no distinctive match)

reality 69% if (!f.endsWith('.json')) continue;

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

intent 77% (no distinctive match)

reality 67% writeFileSync(OUT, render(p));

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

intent 72% (no distinctive match)

reality 69% export function computePortfolio() {

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

intent 73% (no distinctive match)

reality 67% import { shortLexToBlock } from './shortlex-coords.mjs';

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

intent 75% (no distinctive match)

reality 64% (no distinctive match)

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

intent 77% Guard (the deliverable): project-portfolio.test.mjs — the rollup yields the underwriter numbers

reality 67% // scripts/pmu/project-portfolio.mjs — THE PROJECT ALTITUDE (the missing third receipt).

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

intent 73% (no distinctive match)

reality 70% name: (r.reef && r.reef.name) || r.coord.label, domain: r.reef && r.reef.domain, guessed: r.ree

C1,C1 Power flows where the grid lets it.

intent 77% (no distinctive match)

reality 70% (no distinctive match)

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

intent 75% (no distinctive match)

reality 73% const [br, bc] = k.split(',').map(Number);

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

intent 78% **¶1 — insurability opener** (*"A license makes you insurable — the free install alone doesn't.

reality 70% (no distinctive match)

commit context — 5 file(s)

feat(pmu): the PROJECT altitude — portfolio insurability panel (the missing third receipt)

The insurability signals fired on-PROMPT (lens) and on-COMMIT (triptych) but never at
PROJECT level — the underwriter's actual view. This is what we missed in our own process:
we made it scale-invariant WITHIN a panel (dense↔sparse) but never ACROSS altitudes; every
signal we built got wired to the commit node only. project-portfolio.mjs fills the third node,
scale-invariant with the commit receipt — the SAME encircled tolerance panel + reef-named
coordinates + σ + breach, rolled up over the whole repo, LLM-free and deterministic.

Two ledgers, never a re-render (find the running code):
  • measure-history.ndjson (200 commits) → portfolio σ + BREACH 71.5% (the loss ratio)
  • lens-receipts/*.json (2459 placements) → the whole-repo DRIFT MAP, binned to ShortLex
    blocks, coloured by mean σ, run through the ONE region pipeline (detectRegions → encircle
    → expandCoordName). The project's hot regions come out encircled + named by problem space:
    pmu-walk, symbol-grounding, comms-email, ai-regulation.

Guard (the deliverable): project-portfolio.test.mjs — the rollup yields the underwriter

docs/comms/self/approved/2026-07-10-pricing-iamfim-post-push-grading.grade.json
docs/comms/self/approved/2026-07-10-pricing-iamfim-post-push-grading.md
docs/pmu/project-portfolio.html
scripts/pmu/project-portfolio.mjs
tests/pmu-simulator/project-portfolio.test.mjs

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

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.