jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Bound runtime-effect per-record trigger gate

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 02:38:53 -07:00
commit bed0ef86b0
2 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/rehost-queue.md
View file

@ -280,6 +280,14 @@ Working rule:
but emits only the corpus-level count fields, so the next broader map-install pass no longer
needs to wade through every occurrence payload just to compare descriptor or trigger-kind
coverage.
- the per-record trigger gate is explicit now too:
direct disassembly of `0x004323a0` shows the service returns before dispatch unless
one-shot latch `[event+0x81f]` is clear, mode byte `[event+0x7ef]` matches the selected
trigger-kind argument from `0x00432f40`, and the compact chain root `[event+0x00]` is
nonzero. The kind-`8` side path at `0x00432ca1..0x00432cb0` only calls `0x00438710` on
already-live records carrying `[event+0x7ef] == 8`. So the remaining ordinary bundle question
is no longer “does the service loop itself bypass the per-record trigger byte?”; it is which
later owner, if any, materializes or retags `[event+0x7ef]` for the nondirect compact rows.
- cross-map probing now gives a better static-analysis lead too:
`British Isles.gmp` shows no current `0x00431b20` dispatch-strip rows, `Germany.gmp` stays on
`Game Variable 1` plus `Company Variable 3..4`, while `Texas Tea.gmp` adds `Economic Status`