df9431be64
Decides lane AG's section 3.3 final paragraph, which lane AD correctly reported it could not separate on sector 832. STATIC: FUN_00841700 is the writer AG's section 7 lists as not found. It resizes the +0x0c vector to the length of the systems vector -- the container trfr indexes -- and fills it with containingSector[system.Idx] = sector. It runs from the deserialiser, so a loaded save has it populated. G_B1a cannot reject a valid trfr. LIVE: four raiders parked (2 CR on sector 832, 2 DE on sector 816), probes=8. Slot13RngCalleeA entered 4x/turn at 4 words every turn; on turn 42 the pick fired at 0x0088b613, calls=1 words=1, and the tail cost 5 words against 4 elsewhere. The same run carries its own control: B entered on 832 twice at 0 words. B costs ONE word, not two: FUN_00820af0's third short-circuit is a flag word InitTable sets only for Human and Zuul, so AG's committed 3-words-on-success is 2. Two hooks=off processes gave byte-identical autosaves, and so did a probes=8 process -- an oracle pair and a whole-save byte-neutrality proof for the instrument, both firsts on this lineage. Also first firings of 0x008939ee (rule 20's case study) and 0x00820c1b. |
||
|---|---|---|
| .. | ||
| ag.json | ||
| ar.json | ||
| as.json | ||
| lane-a.json | ||
| lane-a2.json | ||
| lane-ac.json | ||
| lane-ai1.json | ||
| lane-ai2.json | ||
| lane-ai3.json | ||
| lane-ai4.json | ||
| lane-b5.json | ||
| lane-b6.json | ||
| lane-c3.json | ||
| lane-d2.json | ||
| lane-e1.json | ||
| lane-e3.json | ||
| lane-ev.json | ||
| lane-g2.json | ||
| lane-g3.json | ||
| lane-h.json | ||
| lane-i.json | ||
| lane-id.json | ||
| lane-j.json | ||
| lane-k.json | ||
| lane-l1.json | ||
| lane-l3.json | ||
| lane-l4.json | ||
| lane-l5.json | ||
| lane-n.json | ||
| lane-o.json | ||
| lane-p2.json | ||
| lane-par.json | ||
| lane-pl.json | ||
| lane-q.json | ||
| lane-rb.json | ||
| lane-sd.json | ||
| lane-sv.json | ||
| lane-t.json | ||
| lane-t2.json | ||
| lane-u.json | ||
| lane-v2.json | ||
| lane-w.json | ||
| lane-w2.json | ||
| lane-w3.json | ||
| lane-z.json | ||
| README.md | ||
Per-lane address fragments
addresses.json is a single shared file. When several lanes run concurrently they edit the
same lines, and three times on 2026-09-08 one lane's git add swept another's in-flight
entries into the wrong commit. Nothing was lost, but authorship and atomicity were.
A lane may instead drop its own file here:
{ "entries": [ { "name": "...", "addr": "0x...", "convention": "...",
"prototype": "...", "status": "verified", "source": "findings/..." } ] }
Name it after the lane (lane-d.json). tools/gen_addresses.py merges every fragment in
sorted order after addresses.json. A duplicate name across files is a hard error, not
last-wins — two lanes disagreeing about an address is exactly the thing we must not paper over.
The integrator folds fragments back into addresses.json once the lane's work is merged.