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

Tighten remaining atlas edge conclusions

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-06 21:36:19 -07:00
commit f0b2426bf6
7 changed files with 57 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/atlas/multiplayer.md
View file

@ -150,9 +150,10 @@ Highest-value open edge:
The negative result is stronger now too: the neighboring replay-band fields
`[transport+0x176c]`, `[transport+0x1770]`, `[transport+0x1774]`, `[transport+0x177c]`,
`[transport+0x1780]`, and `[transport+0x1784]` all have direct local lifecycle owners, but
`[transport+0x1778]` still only appears as the single read in `0x595bc0`. So the remaining
writer is upstream and indirect rather than one ordinary direct field store in the local text
cluster. One adjacent staged-route callback is
`[transport+0x1778]` still only appears as the single read in `0x595bc0`. So this is no longer
a local ownership gap: no local writer is grounded, and the remaining staging path is best read
as upstream and indirect rather than one ordinary direct field store in the local text cluster.
One adjacent staged-route callback is
tighter now too: `0x595860` is the submit-result handler below
`0x5958e0`, using the already-grounded third selector-generation counter at `[transport+0xac0]`
plus the target at `[transport+0xb48]` to choose whether staged route-callback traffic can