Save Selector Gate Sample Values

route map1_01a -> map2_02d; sample source -; sample selectors ; current frontier selector 2:0; save/runtime in-range values 0 / 0; party-slot stat in-range values 0 / 0; proofFound False; promotion status blocked.

The public savedat bytes keep the save/runtime block base plausible only as calibration: loader-aware mapping puts 0x004576d8+0xe8/0xea at save offsets 0x00e2/0x00e4 after the six-byte runtime gap, and all public samples read 0x00 there. Those values are in the expected 0..11 branch-index range, but the samples cover selectors 0:0, 1:0, and 22:0, not the current frontier selector 2:0. The same samples make the party-slot-base mapping weaker: the corresponding stat-byte candidates are 0xe7, 0xa6, or 0x7a, outside the expected selection-index range. This rejects the stat-byte interpretation as promotion evidence while leaving global/save-runtime buffer or object pointer table runtime proof still required.

Failed Gates

• current-selector-2-0-sample
• runtime-pointer-mode-proof
• party-slot-index-evidence
• control-path-gate-byte-proof

Missing Evidence

• public or captured sample covering current selector 2:0 gate bytes
• runtime pointer-mode proof selecting the correct gate base
• party-slot byte evidence that yields a valid branch-state index rather than stat bytes
• control-path proof that sampled gate bytes apply to the current frontier gates

Evidence Refs

• data/savedata_sample_gate_values.json: public savedat byte samples used to calibrate gate offsets
• out/save_selector_gate_base_candidates.json: candidate gate-base mappings and save offsets being sampled

Save/Runtime Gate Bytes

Party Slot Stat Bytes