7e6bda3699
findings/subsystems/ai-order-capture.md -- two workloads on VM145, every submitted TurnCommands block dumped at the batch applier, plus sixteen pass-attributed entry probes on the task bodies and the emission gates. Headline: our emission model reproduces both real blocks exactly, list for list and element for element, and both turns land on the measured ModCount of 12. What it did not have: a list-23 element on every AI turn (the first element ever observed in the free half of the cost table, and it really is free), client-allocated ids travelling inside the commands (design 18, fleet 34 -- neither in the input save), and build, rates and population all naming the same home system. Two predictions falsified, both usefully: the batch is n = playerCount = 8 with the four monster factions holding untouched slots, not n = 4; and the fleet order names the fleet the client has ALREADY created, not the one in the save. AITRaid's pass-0 question stays open and now says why -- the task never ran on either board, so the list-16 zero is 'never entered', not 'entered and silent'. Rule 19: the ref-turn2 control passed byte-identical to the published oracle with all seventeen detours installed. Separately, the turn-1 workload is NOT reproducible -- three runs, three autosaves, differing in exactly one field: the research target of the AI player that owns nothing. ghidra/addresses.d/lane-l4.json: 9 entries (8 IAITask::Execute bodies + the list-16 order method). Raw logs and the two divergent autosaves in verify/results/shim/aiorders/.
65 KiB
65 KiB