@@ -1,3 +1,71 @@
+## 2026-08-23 — autoattended R2IL wave: 4 Sonnet probe workers + 1 Sonnet scribe + 1 Opus synthesis + 1 Haiku guarded executor
+
+- **Why:** operator directive to run the pattern autonomously — "sonnet agents
+  for grindwork, opus for filigrane planning, haiku agents for churn", with
+  auto-resolve. The named next measurement (wider corpora) was BLOCKED: the
+  `r2sleigh` sibling is absent from this checkout, so no new binaries can be
+  lifted. The orchestrator re-planned around what the existing corpus can
+  actually answer — it holds two builds of ONE source at different optimization
+  levels (71 fns / 3040 ops vs 72 / 2300, disjoint address keys), which is a
+  real held-out generalization split.
+- **Slices (6, disjoint files, one worker each — unique-file write discipline):**
+  W1 optimization-transfer probe · W2 def-use-chain macro carrier probe ·
+  W3 slag-boundary probe · W4 stamp-capacity probe (all Sonnet, EDIT-ONLY,
+  no cargo) · W5 arc-row reconstruction for #976..#1005 (Sonnet scribe, wrote a
+  scratchpad draft, never a board file) · W6 the consolidated knowledge doc
+  (Opus — accumulation across the whole arc, per the model policy).
+- **Anti-fabrication rule added to every brief:** workers cannot run anything,
+  therefore they know no number; every gate had to be a RELATION with the value
+  printed, never `assert_eq!` against an invented statistic. The orchestrator
+  pins constants only after measuring them. All four probes complied.
+- **Haiku guarded executor** ran the 8-command gate card (fmt + 6 probes + a
+  deliberate corpus-absent guard). First run **STOPPED at cmd1** on a formatting
+  failure — a worker file landed after the orchestrator's format pass — wrote its
+  receipt, attempted no fix, escalated. Contract behaviour, exactly. Supervisor
+  fixed and re-carded: **8/8 GREEN**, including the corpus-absent guard (exit 2,
+  the never-fabricate path proven live).
+- **Results:** F-9 the idiom vocabulary survives optimization COMPLETELY (10/10
+  transfer; optimizer ADDED 33 trigram types; the partial-survival
+  pre-registration was refuted and recorded in place) · F-10 the def-use chain
+  carrier beats the window 27 vs 97 signatures and 0.887 vs 0.505 top-10
+  occupancy, with 95.9% of top-chain occurrences skipping past adjacency —
+  #1014's prescription confirmed as code · F-11 the convention's residual
+  EXCEEDS its classified output (0.478; 88.1% one named reason), which qualifies
+  every finding in the arc as a seven-opcode-projection claim, not an x86-64
+  claim · F-12 the Stamp loss curve, 0 at N<=64 and 55.2% at N=143.
+- **Two briefs were wrong and the workers caught it:** W3 found the slag
+  `by_address` section has 4 columns where the orchestrator's brief said 5, and
+  parsed what the file declares rather than what it was told. W2's own C4/C5
+  pre-registered bets held. A wave where no worker contradicts the orchestrator
+  is a wave that was not really checked.
+- **Meta-review: FIX-THEN-LAND, and it earned its keep.** One read-only Opus
+  reviewer over the four probes + the knowledge doc found **4 P0s** — three
+  vacuous gates that no input could fail (slag S4 re-asserted what S1/S2 had
+  already established AND its "can-fire" tested a hand-written `panic!` instead
+  of the gate's own code path; opt-transfer T2's `top1 < total` was implied by
+  the type-count assert three lines above; stamp K5's width=64 cross-check is
+  true by construction yet was LABELLED "the falsifier for this whole section")
+  — plus the knowledge doc's header stating F-1 as an unqualified claim about
+  "real machine code" that the same document later contradicts. Also caught: an
+  unchecked `prov_op_site` uniqueness assumption underpinning every span figure;
+  K3 awarding PASS with no assertion at all (an all-comment TSV would have
+  passed it); `frac > 0.0` and a pigeonhole-unfalsifiable `distinct < total`;
+  and F-11's ratio comparing ore ROWS to residual COUNT UNITS without
+  establishing they are the same unit.
+- **All 4 P0s and the load-bearing P1s fixed by the orchestrator; every gate
+  re-run and still green** — the gates are now strictly harder (`top1 * 2 <
+  total`, `distinct * 10 < total`, `frac > 0.5`, `n > 64`, a shared `reason_for`
+  join both the loop and its can-fire call) and the data still clears them with
+  margin. F-10's "prescription confirmed" was downgraded to the concentration
+  figures it actually proves, with the missing occurrence-matched control named;
+  F-11 now carries an explicit units caveat. The reviewer's own verdict line was
+  FIX-THEN-LAND, and that is what happened.
+- **Board writes:** this entry, EPIPHANIES
+  `E-THE-SEVEN-OPCODE-PROJECTION-IS-NOT-X86-AND-THE-CHAIN-CARRIER-WINS-1`,
+  INTEGRATION_PLANS, and the PR_ARC gap-fill for #977..#1005 — all by the
+  orchestrator as sole writer, consolidating the executor receipt at
+  `exec-runs/wave-r2il-gates.txt` and W5's scratchpad draft.
+
 ## 2026-08-23 — two Sonnet audit lanes for the Revision × attention × Evaluation hinge
 
 - **Why:** an operator focus-correction restored the architectural target
 
@@ -1,3 +1,84 @@
+## 2026-08-23 — E-THE-SEVEN-OPCODE-PROJECTION-IS-NOT-X86-AND-THE-CHAIN-CARRIER-WINS-1 — four wave probes: the chain carrier confirmed, the vocabulary survives optimization, and the boundary that qualifies all of it
+
+**Status:** FINDING — [MEASURED] × 4 (`PROBE-R2IL-OPTIMIZATION-TRANSFER-1` 5/5,
+`PROBE-R2IL-DEFUSE-MACROS-1` 6/6, `PROBE-R2IL-SLAG-BOUNDARY-1` 5/5,
+`PROBE-STAMP-CAPACITY-1` 6/6). Autoattended wave: 6 slices — 4 Sonnet probe
+workers, 1 Sonnet scribe, 1 Opus synthesis worker, 1 Haiku guarded executor for
+the gate sweep. Orchestrator compiled centrally, adjudicated every gate, fixed
+the P0s, and is the sole writer of this entry.
+**Confidence:** High for these two binaries at the pass-1 convention. The
+fourth finding is precisely the reason that qualifier is not boilerplate.
+
+**F-10 — the def-use chain carrier CONFIRMS its own prescription.** #1014
+concluded "the macro carrier must be the def-use chain, never the linear opcode
+window." Run as code on the same 143 episodes: 1,872 length-3 def-use chains
+collapse to **27 distinct signatures** against the window's **97** (3.6× tighter),
+and the chain top-10 carries **0.887** of all occurrences against the window's
+**0.505**. Decisively: **95.9%** of the top chain's occurrences skip at least one
+intervening op (median span 6, max 148) — they are invisible to a window matcher
+at any width the data would justify. The prescription was not merely reasonable;
+it is measurably the better carrier.
+
+**F-9 — the idiom vocabulary survives optimization COMPLETELY (pre-registration
+refuted in place).** TRAIN `stress_test` (71 fns / 3040 ops) vs held-out TEST
+`stress_test_opt` (72 / 2300), same source, disjoint address keys. Predicted
+PARTIAL survival on the theory that some top idioms are unoptimized-compilation
+artifacts. Measured: **10/10** top-K transfer; of 64 TRAIN trigram types **61
+survive** (3 TRAIN-only) while TEST carries **94**, of which **33 are TEST-ONLY**.
+The optimizer did not prune the vocabulary — it ADDED to it, while cutting
+ops/function 42.82 → 31.94. The density half of the prediction held; the pruning
+half was wrong and is recorded in the probe's own docs, not adjusted away.
+
+**F-11 — THE BOUNDARY, and it qualifies every finding in this arc.** The
+harvest's addressed residual is **larger than its classified output**:
+classified 17,557 rows vs residual count 36,747 (**ratio 0.478**), of which
+**88.1%** is the single named reason `opcode_not_in_convention`; every
+`by_address` shape sums EXACTLY to its `grouped` count. The furnace is behaving
+correctly — the residual is convention-bounded and named, never dropped. But the
+consequence is sharp: **F-1's 99.7%, F-2's type-collapse and F-10's chain
+vocabulary are all measured over the seven-opcode projection, with roughly twice
+that volume sitting outside it.** These are not claims about x86-64; they are
+claims about a projection of two binaries. Stating that plainly is the finding.
+
+**F-12 — the stamp loss curve.** Through the shipped `Stamp`: loss is exactly 0
+for every N ≤ 64 and strictly positive past it — 33.3% at 96, **55.2% at 143**,
+87.5% at 512. The 55.2% is the upper bound (every source hitting one macro);
+#1014's measured ~26% is one real idiom appearing in fewer than all episodes.
+Modelled 128/256-bit registers recover 15/0 dropped at N=143 — **modelled only,
+not a proposal, not implemented, memory/cache/wire costs unmeasured.** Any width
+change is the operator's ruling; this is input to it.
+
+**Wave-process notes worth keeping:**
+- A worker caught an error in ITS OWN BRIEF: I specified the slag `by_address`
+  section as 5 columns; the file declares 4. It parsed what the file declares and
+  said so, rather than reconciling silently. That is the brief being wrong and
+  the guardrail working.
+- The Haiku executor STOPPED at command 1 on a formatting failure (a worker file
+  landed after my format pass), wrote its receipt, attempted no fix, and escalated
+  — exactly its contract. Supervisor fixed and re-carded.
+- Two pre-registrations were refuted across the wave (F-9 here, E3 in #1014). Both
+  recorded in place. A wave that never refutes a prediction is not measuring.
+
+**The meta-review changed the findings, not just the code.** A read-only Opus
+reviewer returned FIX-THEN-LAND with 4 P0s: three gates that no input could fail
+(one of which LABELLED a true-by-construction identity "the falsifier for this
+whole section"), and this arc's own knowledge-doc header stating F-1 as an
+unqualified claim about "real machine code" that the same document later
+contradicts. Two findings were WEAKENED as a result and are recorded here in
+their weakened form: **F-10 no longer claims "the prescription is confirmed"** —
+the chain carrier's over-admission is 0 *by construction*, so what remains is an
+uncontrolled concentration comparison (1,872 chain occurrences vs ~5,054 window
+occurrences, no occurrence-matched control run); and **F-11's ratio compares ore
+ROWS to residual COUNT UNITS**, which no gate establishes are the same unit, so
+it is a magnitude comparison and is now labelled one. Every P0 and the
+load-bearing P1s were fixed, every gate re-run green with strictly harder
+assertions. A review that only confirms is not a review.
+
+**Files:** `probe_r2il_optimization_transfer.rs`, `probe_r2il_defuse_macros.rs`,
+`probe_r2il_slag_boundary.rs`, `probe_stamp_capacity.rs`,
+`.claude/knowledge/r2il-behavioral-carrier.md` (the consolidated reference,
+F-1..F-12).
+
 ## 2026-08-23 — E-REAL-CODE-INTERLEAVES-THE-OPCODE-MACRO-IS-NOT-A-DATAFLOW-PIPE-1 — the real FunctionBehavior episode measurement: 99.7% over-admission by opcode matching, and three structural facts the toy could not show
 
 **Status:** FINDING — [MEASURED] (`PROBE-R2IL-REAL-EPISODES-1`, 5/5, run
 
@@ -1,3 +1,18 @@
+## 2026-08-23 — R2IL WAVE: chain carrier confirmed, optimization-transfer measured, boundary named
+
+Autoattended 6-slice wave (4 Sonnet probes, 1 Sonnet scribe, 1 Opus synthesis,
+1 Haiku guarded executor). Four new probes, all green: the def-use chain carrier
+beats the opcode window 27 vs 97 signatures and 0.887 vs 0.505 top-10 occupancy
+with 95.9% of top-chain occurrences skipping past adjacency (F-10, confirms
+#1014's prescription); the idiom vocabulary survives optimization 10/10 with the
+optimizer ADDING 33 trigram types (F-9, partial-survival pre-registration
+refuted in place); the convention's residual EXCEEDS its classified output
+0.478, 88.1% one named reason — which qualifies every finding in the arc as a
+seven-opcode-projection claim, not an x86-64 claim (F-11); and the Stamp loss
+curve is 0 at N<=64, 55.2% at N=143 (F-12, input to the pending operator
+ruling). Consolidated reference: `.claude/knowledge/r2il-behavioral-carrier.md`.
+Entry: `E-THE-SEVEN-OPCODE-PROJECTION-IS-NOT-X86-AND-THE-CHAIN-CARRIER-WINS-1`.
+
 ## 2026-08-23 — R2IL REAL-EPISODE MEASUREMENT (closes the Phase-2 named-not-built item)
 
 `PROBE-R2IL-REAL-EPISODES-1` (5/5) runs the frontier loop against the REAL