Bind event-detail trigger and builder lanes

This commit is contained in:
Jan Petykiewicz 2026-04-19 00:11:26 -07:00
commit a3c4d4e032
2 changed files with 21 additions and 2 deletions

View file

@ -234,6 +234,13 @@ Working rule:
startup compact-effect question is no longer whether kind `8` is a special synthetic class, but
which loaded kind-`8` rows in `0x0062be18` can actually reach the placed-structure mutation
opcode families under `0x00431b20`
- the event-detail editor family tightens that one step further too:
selected-event control root `0x4e84` and refresh strip `0x004db02a / 0x004db1b8..0x004db309`
mirror current trigger field `[event+0x7ef]` back into those same `0x4e98..0x4ea2` controls,
while editor-side builder `0x004db9e5..0x004db9f1` allocates an ordinary runtime-effect row
into `0x0062be18` through `0x00432ea0`; so the remaining startup compact-effect question is no
longer whether kind `8` lives on a separate editor/build class either, but which loaded
kind-`8` rows actually carry the mutation-capable compact payloads
- the `[site+0x27a]` companion lane is grounded now too:
it is a live signed scalar accumulator rather than a second owner-identity seam, with zero-init
at `0x0042125d` and `0x0040f793`, accumulation at `0x0040dfec` and `0x00426ad8`, direct set on