BS: cross-reference lane BR - the global generator's three-word seed mint reproduces, and it is not the whole story on an encounter turn

findings/control-flow/per-history-residue.md

@@ -453,6 +453,46 @@ four processes, byte for byte.
 > outcome set of 2 came from two observations — but it does bound the claim: *a turn that mints new
 > fleet ids is not thereby a turn whose visit order varies.* One datum, one turn, handed to lane BR.
 
+### 4.7 Lane BR merged while this was being written — one confirmation and one scope correction
+
+Lane BR's `ai-visit-order-probe.md` landed on `main` at 02:52 local, after this lane's predictions
+were committed (15c4471, 02:31) and while its runs were in flight, so neither lane knew the other's
+answer. Its headline and mine are the same measurement taken from opposite sides — BR held the
+**route** fixed and varied the process; this lane held the **process shape** fixed and varied the
+route — and they agree.
+
+**Confirmation, on a different save, a different lineage and a third guest.** BR: the per-process
+global generator at `0x00af6e58` was "touched three times in the entire process, all three at one
+return address `0x00784f9e` inside `StrategyNetworkClient::OnMessage`, sixteen bytes before the
+`RunAI` call — one seed per AI client". Run **L**'s census, independently, on `ar-oracle-A-pre`:
+
+```
+airngcensus rng=0x00da6e58 ret_rva=0x00384f9e va=0x00784f9e entry=NextUInt calls=3 words=3
+```
+
+Three words, one site, the same Ghidra address, for the whole process. Two lanes, two saves, two
+guests, same number and same return address.
+
+**And a scope correction to BR's row title, measured here.** BR's turn had no encounter. Run **C**'s
+turn 38 does, and on it the global generator does **not** stop at three:
+
+| run | turn | global generator lifetime at the last bracket |
+|---|---|---|
+| **L** | 39 only, no encounter | 3 words — `0x00784f9e` NextUInt ×3 |
+| **C** | 38 (encounter) + 39 | **87 words** — `0x00784f9e` NextUInt ×3, `0x008622aa` NextInt ×2, `0x006f3517` NextInt ×2, `0x006fb6a1` **Chance ×80 = 80 words** (with the inner `0x008e6e09` NextFloat ×80 at 0 words) |
+
+The 84 extra words appear **between the turn-38 client sweep and the turn-39 client sweep** — an
+interval that contains the deep-space encounter and its peaceful auto-resolve. This lane did **not**
+bracket that interval, so "the encounter spent them" is the obvious reading and not a measurement;
+what *is* measured is that they are on the global generator, at three named return addresses, and
+that **none of them is inside any AI client's bracket** (`foreign_words=0`, 14 of 14).
+
+> So *"the global generator only mints seeds"* is true **on a turn with no encounter** and false on a
+> turn with one. That is rule 28's shape exactly: a zero on a gated path is a statement about the
+> states measured until the gate is a predicate. BR's H2 verdict is untouched — the question there
+> was whether a foreign draw fires **inside** an AI bracket, and it does not, on either lane's
+> workload. Only the row's summary sentence needs the scope.
+
 ---
 
 ## 5. Verdicts on the committed predictions
@@ -664,4 +704,5 @@ Edits to existing rows:
 - **Row 426** (the 09-09 resolution's row) — append: `LANE BS RAN §8's VM144 PARAGRAPH 2026-09-09. §9.2 candidate 1 (AI agent state the save does not carry) SURVIVES and is measured, not inferred: the missing input is a TASK. Candidate 3 (server-side state) is disfavoured - every diverging save leaf has a block-side counterpart. Candidate 2 (stream position) is not what explains it, though the two routes DO differ in stream position, so this run does not exclude it on that ground; the seed-insensitivity of both routes does. §9.3's (a) and (d) CONFIRMED, (b) CONFIRMED and sharper than written, (c) CONFIRMED with the word difference in the OPPOSITE route from the one implied. Two clauses FALSIFIED, both over-specifications: there is no list-14 pair on turn 39, and probe 11 is NOT entered on the load route at all.`
 - **Row 360 / the pinned-seed rows** — append: `BOUNDED 2026-09-09 (lane BS): a turn that mints new client fleet ids is not thereby a turn whose visit order varies. AR turn 38 minted TWO (2466 counter 154, 2482 counter 155, both absent from ar-turn37) through six entries to AssignFleetsAndIssueOrders, and four processes (AR's three hooks=off plus BS's instrumented one) produced 15b99255... byte for byte - outcome set 1 on that turn.`
 - **`determinism-hashes.txt`** — the AR load-form pair (resolution §9.3) enters with the route on the line, and BS adds a second certified procedure for the same lineage: `ar-turn37-816raiders.sav -> (load, End Turn, Auto Resolve Peacefully, End Turn) -> (Autosave EndTurn) 15b99255... / (Autosave) 7a8b3d5e...`, four processes, three of them un-instrumented. **Both lines must carry the `/CD[1]/NPrvVa` mask note**, and the load-form line must say that its `(Autosave EndTurn)` is a RESAVE of `ar-oracle-A-pre.sav` differing on that one leaf.
+- **Lane BR's new row** (`RNG excluded by measurement, the global generator only mints seeds`) — append a scope clause: `SCOPED 2026-09-09 (lane BS, VM144, independently and on a different lineage): the three-words-one-site measurement REPRODUCES EXACTLY on ar-oracle-A-pre - `rng=0x00af6e58 ret_rva=0x00384f9e va=0x00784f9e NextUInt calls=3 words=3` for a whole process. **But "only mints seeds" holds only on a turn with NO ENCOUNTER.** On the AR continuation's turn 38, which has a deep-space encounter auto-resolved peacefully, the same generator ends the process at **87 words**: the 3 seed words plus `0x006fb6a1` Chance x80 = 80 words and two NextInt pairs at `0x008622aa` / `0x006f3517`. The 84 extra words fall between the turn-38 and turn-39 client sweeps - an interval containing the encounter - and were NOT bracketed, so their attribution to the encounter is a reading, not a measurement. **H2's verdict is untouched** (the question is whether a foreign draw fires INSIDE an AI bracket, and foreign_words=0 in 14 of 14 brackets across BS's two runs as well); only the summary sentence needs the scope. Rule 28's shape.`
 - **Rule 26 (c) term (5)** — append one clause to the load-history term: `and the difference can be that the load route does not run the machinery at all: on the AR lineage the continuation enters AssignFleetsAndIssueOrders twice on turn 39 and the load zero times, because the TASK that would have called it does not exist after a load (lane BS).`