alex/sots-re
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Z: S+0x8 is 12-44 per turn, not 12-14 -- it scales with the game state

Browse source 
The second save's numbers were not in the first draft's table. Correcting my
own correction: on a turn-19 Zuul game the counter moves 16, 21 and 44 times
between ProcessTurn entries, against 12-14 on an early two-colony game. So it
is not a driver-invocation counter and not a constant either.
This commit is contained in:
alex 2026-09-08 09:49:17 -04:00
parent 9af2d0c6f4
commit 3a3513b5cc
2 changed files with 33 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
findings/control-flow/combat-done-tail.md
View file

@ -623,12 +623,14 @@ same word. Given §6's inference that the message is delivered every turn, `S+0x
per turn while `S+0xc` (`ModCount`) advances once. They are not in lockstep, and a reimplementation must not per turn while `S+0xc` (`ModCount`) advances once. They are not in lockstep, and a reimplementation must not
treat `S+0x8` as a turn number. It reads as a **server-phase / driver-invocation counter**. treat `S+0x8` as a turn number. It reads as a **server-phase / driver-invocation counter**.
> **MEASURED by lane Z, 2026-09-08 — "at least twice" is the right phrasing; it is 12 to 14.** Read live at > **MEASURED by lane Z, 2026-09-08 — "at least twice" is the right phrasing, and the real number is 12 to
> hook entry over eight turns on two saves, `S+0x8` advances **12–14 times per turn**, of which the two > 44.** Read live at hook entry over eight turns on two saves, `S+0x8` advances **12–14 times per turn** on
> drivers account for 2. Both drivers were hooked, so the other 10–12 increments come from a writer nobody > an early two-colony game and **16–44** on a turn-19 Zuul one, of which the two drivers account for 2.
> has identified, and they happen between the post-turn autosave and the next `ProcessTurn`. `S+0xc` > Both drivers were hooked, so the rest come from a writer nobody has identified, between the post-turn
> advances by exactly 1 per turn over the same records. The conclusion here is strengthened: `S+0x8` is not > autosave and the next `ProcessTurn`. `S+0xc` advances by exactly 1 per turn over the same records. The
> a turn number and is not even a driver-invocation counter. `findings/control-flow/tail-rng-ledger.md` §5. > conclusion here is strengthened: `S+0x8` is not a turn number, it is not a driver-invocation counter, and
> it is not even a constant per turn — it scales with the size of the game state.
> `findings/control-flow/tail-rng-ledger.md` §5.
### 7.2 Turn results and turn events are not where lane T said ### 7.2 Turn results and turn events are not where lane T said

44
findings/control-flow/tail-rng-ledger.md
View file

@ -166,16 +166,16 @@ RNG cost attached*, which none of the eleven corpus saves has.
> **§6, labelled hypothesis:** "I did not prove that `SNMAllCombatDone` is delivered on turns with no > **§6, labelled hypothesis:** "I did not prove that `SNMAllCombatDone` is delivered on turns with no
> combat." > combat."
**The handler runs on every End Turn.** Four out of four, `OnAllCombatDone_Tail` recorded exactly one call **The handler runs on every End Turn.** Eight out of eight, across two unrelated saves,
per End Turn, at depth 0, between the two autosaves, with the post-turn autosave following it. The `OnAllCombatDone_Tail` recorded exactly one call per End Turn, at depth 0, between the two autosaves, with
determinism-note inference was right. the post-turn autosave following it. The determinism-note inference was right.
The stronger claim — that it runs with an *empty encounter vector* — is **not** settled by this workload and The stronger claim — that it runs with an *empty encounter vector* — is **not** settled by this workload and
must not be reported as though it were. On `ref-turn2` the encounter vector is **empty at `ProcessTurn` must not be reported as though it were. On **both** saves the encounter vector is **empty at `ProcessTurn`
entry and holds exactly one encounter by the time the tail runs** on every one of the four turns: detection entry and holds exactly one encounter by the time the tail runs**, on every one of the eight turns:
(`ProcessTurn` phase 31) creates it, and the tail's phase 7 clears it. So what is proved is "the tail runs detection (`ProcessTurn` phase 31) creates it, and the tail's phase 7 clears it. So what is proved is "the
on a turn with **no battle**", not "on a turn with no encounter at all". See §8 for what closing the tail runs on a turn with **no battle**", not "on a turn with no encounter at all". See §8 for what closing
remaining gap needs. the remaining gap needs.
Two things fall out of the same records and are worth more than the phrasing: Two things fall out of the same records and are worth more than the phrasing:
@ -194,18 +194,24 @@ Two things fall out of the same records and are worth more than the phrasing:
Lane K wrote that `S+0x8` "advances **at least twice** per turn". That is correct and this lane's prediction Lane K wrote that `S+0x8` "advances **at least twice** per turn". That is correct and this lane's prediction
that it advances **exactly** twice is **wrong**. Observed `S+0x8` at hook entry: that it advances **exactly** twice is **wrong**. Observed `S+0x8` at hook entry:
| turn | `ProcessTurn` entry | tail entry | tail's callees | next turn's `ProcessTurn` entry | | save | turn | `ProcessTurn` entry | tail entry | tail's callees | increments to the next turn |
|---|---|---|---|---| |---|---|---|---|---|---|
| 3 | 22 | 23 | 24 | 34 | | ref-turn2 | 3 | 22 | 23 | 24 | **12** |
| 4 | 34 | 35 | 36 | 48 | | ref-turn2 | 4 | 34 | 35 | 36 | **14** |
| 5 | 48 | 49 | 50 | 60 | | ref-turn2 | 5 | 48 | 49 | 50 | **12** |
| 6 | 60 | 61 | 62 | — | | ref-turn2 | 6 | 60 | 61 | 62 | — |
| zuul-noderoute | 17 | 253 | 254 | 255 | **16** |
| zuul-noderoute | 18 | 269 | 270 | 271 | **21** |
| zuul-noderoute | 19 | 290 | 291 | 292 | **44** |
| zuul-noderoute | 20 | 334 | 335 | 336 | — |
The two drivers account for 2 of the **12 to 14** increments per turn. Ten to twelve more happen between the The two drivers account for **2 of 12 to 44** increments per turn, and the count is not a constant — it
post-turn autosave and the next `ProcessTurn`, from a writer this lane did not identify (both drivers are grows with the size of the game state (12–14 on a turn-3 two-colony empire, 16–44 on a turn-19 Zuul one).
hooked, so it is neither of them). Lane K's operational conclusion is strengthened, not weakened: **`S+0x8` The rest happen between the post-turn autosave and the next `ProcessTurn`, from a writer this lane did not
must never be treated as a turn number.** `S+0xc` (`ModCount`) reads 3, 4, 5, 6 across the same four turns identify (both drivers are hooked, so it is neither of them). Lane K's operational conclusion is
and is the turn counter. strengthened, not weakened: **`S+0x8` must never be treated as a turn number** — and it is not a
driver-invocation counter either. `S+0xc` (`ModCount`) reads 3, 4, 5, 6 and 17, 18, 19, 20 over the same
records and is the turn counter.
## 6. Corrections to `combat-done-tail.md` §3 and §6.1 ## 6. Corrections to `combat-done-tail.md` §3 and §6.1