Rule down Tier2 startup availability preseed

This commit is contained in:
Jan Petykiewicz 2026-04-19 14:01:47 -07:00
commit e5c4f0b6ac
2 changed files with 18 additions and 0 deletions

View file

@ -715,6 +715,14 @@ Working rule:
candidate pool through `0x004131f0` and the auxiliary/source pool through `0x0041aa50`, and
both constructors tail directly into the same fixed tagged-import families rather than taking a
title-specific source-selection branch in between.
The startup-side availability preseed is negative in the same way now too: direct disassembly
of `0x00437737` and its sibling callsite `0x00436ad7` shows both branches only *reading*
live candidate subtype `[candidate+0x32]` plus bank bytes `[candidate+0xba/+0xbb]` and then
feeding those predicates into the scenario-side availability table at `[state+0x66b2]` through
`0x00434f20`; the later bring-up caller `0x00444acc` simply re-enters that same
`0x00437737 -> 0x00434f20 -> 0x00412c10` strip. So even the visible startup preseed still
consumes already-materialized bank/template bytes rather than explaining how they became
nonzero in the first place.
So the honest next queue head is now one step earlier again:
recover the non-stock writer or restore-time projection owner that makes some live candidates
reach those later consumer strips with nonzero `[candidate+0xba/+0xbb]` despite the observed