L4: credit lane L5 for the turn-1 nondeterminism, and record what the block dump adds to it

This commit is contained in:
lane-l4 2026-09-08 18:03:18 -04:00
parent 4a5c218a35
commit c769394b57

View file

@ -76,6 +76,9 @@ per-lane fragment mechanism intends.
The turn-1 workload (`turn1-state.sav` + one End Turn) is **not reproducible**. Three runs produced The turn-1 workload (`turn1-state.sav` + one End Turn) is **not reproducible**. Three runs produced
three different post-turn autosaves, differing in exactly one field: the research target of the one three different post-turn autosaves, differing in exactly one field: the research target of the one
AI player that owns nothing. Every other byte — ids, designs, fleets, `ModCount` — is identical. AI player that owns nothing. Every other byte — ids, designs, fleets, `ModCount` — is identical.
`determinism-oracle.md` verifies the oracle for the `ref-turn2` workload and only for that one; this
lane is the first to run the turn-1 workload more than once, and it is now on the record that a Lane L5 established this first and better, on VM146, and owns it
byte comparison on that workload is a comparison against noise. (`sots-re/findings/subsystems/turn1-to-turn2-nondeterminism.md`); use `ref-turn2 → turn3` as the
oracle, not this pair. What this lane adds is where the divergence lives: the differing value is in
the **submitted command block**, in player 512's research-target gate, so the decision is made
client-side before submission and the sim is not diverging on identical input.