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

6
docs/control-loop-atlas.md
View file

@ -983,9 +983,9 @@ transition.
failure strings 3083 3084 3837 and 3900, the binding-registry lookup path at `0x0045f370`, the
registration block at `0x00460769` through `0x004608e7`, and the localized labels in
`Data/Language/RT3.lng` ids `3466` through `3473`.
- Open Questions: no separate outer gameplay loop is grounded above
`simulation_frame_accumulate_and_step_world` yet and no deeper gameplay-only input object is
grounded either. The new setup-pipeline evidence narrows that question in one direction: the
- Open Questions: current evidence grounds the shell-controller-backed input and frame path as the
only coordinator after world entry; no separate outer gameplay loop or gameplay-only input
object is grounded yet. The new setup-pipeline evidence also points the same way: the
currently grounded chunked burst path at `0x00437b20` now looks subordinate to
`world_run_post_load_generation_pipeline` rather than to the ordinary speed controls, and even
there it still reuses the same lower stepper and pumps shell work between chunks instead of