sots-re/verify/results/shim/bu/claim-order.txt
alex 696935ea2a lane BU: H1 confirmed - the fleet-visit order is ascending fleet->Location, and the two-file outcome set is the two orderings of two heap pointers
Three fresh processes on ad-turn27 with the seeds pinned, hooking the two
single-caller per-element callees of the assignment walk.

  * ascending fleet->Location: 6 of 6 multi-element sequences
  * ascending element address (the committed prediction P3): 0 of 6
  * ascending fleet id / systemId / minimum ship id: 0 of 6 each

Three processes gave three different orders of the same six fleets, and every
difference is a pair whose Location addresses exchanged relative order. Runs 1
and 2 wrote byte-identical autosaves and still visited differently. Run 3
flipped the branch and its two Location addresses flipped with it: it is
byte-identical to lane BP's run B, runs 1 and 2 to BP's A and L.

So P3 is falsified as written and its hypothesis class, H1, is confirmed with
a sharper key. H1b is excluded on this path.

Second finding the static read had missed: the fleets already carry their new
ids when the walk first touches them, so the mint is upstream in the gather.
That moves the engine's canonicalisation point by one level.

rule 26(d) and rule 19 are both met by measurement rather than argument: an
instrumented pinned run reproduced an unpinned natural run byte for byte,
twice.
2026-09-09 03:38:22 -04:00

39 lines
2.3 KiB
Text

### RUN1 (verify/results/shim/bu/BU1-aivisit.txt)
call=4 n=6 loc_asc=True elem_asc=False fid_asc=False
elem=0x3254ba70 loc=0x3205b040 fid= 1970 ships=[6976]
elem=0x3254ac90 loc=0x3205cba0 fid= 1602 ships=[6080, 5920, 5936]
elem=0x3254c600 loc=0x3205eb90 fid= 1986 ships=[5264]
elem=0x325497c0 loc=0x33ae5278 fid= 354 ships=[2176, 2352]
elem=0x3254cbc8 loc=0x33ae7020 fid= 1570 ships=[5840, 6144]
elem=0x3254a100 loc=0x33ae8938 fid= 1346 ships=[5024]
call=7 n=2 loc_asc=True elem_asc=False fid_asc=False
elem=0x3254b4a8 loc=0x0d7a5dc8 fid= 7072 ships=[2720, 2992, 3456]
elem=0x32549698 loc=0x33ae6028 fid= 258 ships=[1728]
-> claim sequences with >1 element: 2 loc-ordered 2/2 elem-ordered 0/2 id-ordered 0/2
### RUN2 (verify/results/shim/bu/BU2-aivisit.txt)
call=4 n=6 loc_asc=True elem_asc=False fid_asc=False
elem=0x326b4c98 loc=0x321c5708 fid= 1602 ships=[6080, 5920, 5936]
elem=0x326b5010 loc=0x321c74b0 fid= 1970 ships=[6976]
elem=0x326b5828 loc=0x321c7940 fid= 1986 ships=[5264]
elem=0x326b3450 loc=0x338ab288 fid= 354 ships=[2176, 2352]
elem=0x326b2e88 loc=0x338ac4c8 fid= 1346 ships=[5024]
elem=0x326b64e0 loc=0x338ae270 fid= 1570 ships=[5840, 6144]
call=7 n=2 loc_asc=True elem_asc=False fid_asc=False
elem=0x326b6bd0 loc=0x0d85a3c0 fid= 7072 ships=[2720, 2992, 3456]
elem=0x326b3578 loc=0x338ad278 fid= 258 ships=[1728]
-> claim sequences with >1 element: 2 loc-ordered 2/2 elem-ordered 0/2 id-ordered 0/2
### RUN3 (verify/results/shim/bu/BU3-aivisit.txt)
call=4 n=6 loc_asc=True elem_asc=False fid_asc=False
elem=0x338cff48 loc=0x333ed4c8 fid= 1970 ships=[5264]
elem=0x338d0510 loc=0x333ed710 fid= 1986 ships=[6976]
elem=0x338cf4e0 loc=0x333eede0 fid= 1602 ships=[6080, 5920, 5936]
elem=0x338d5e18 loc=0x34cc4958 fid= 354 ships=[2176, 2352]
elem=0x338cf168 loc=0x34cc6948 fid= 1570 ships=[5840, 6144]
elem=0x338d69a8 loc=0x34cc7268 fid= 1346 ships=[5024]
call=7 n=2 loc_asc=True elem_asc=True fid_asc=False
elem=0x338cfbd0 loc=0x0d9da788 fid= 7072 ships=[2720, 2992, 3456]
elem=0x338d4b98 loc=0x34cc4710 fid= 258 ships=[1728]
-> claim sequences with >1 element: 2 loc-ordered 2/2 elem-ordered 1/2 id-ordered 0/2