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

Add headless runtime tooling and Campaign.win analysis

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-10 01:22:47 -07:00
commit 27172e3786
37 changed files with 11867 additions and 302 deletions
Download patch file Download diff file Expand all files Collapse all files

23
docs/README.md
View file

@ -17,6 +17,7 @@ project is already mature.
- `re-workflow.md`: how to analyze the binary, record findings, and export reusable artifacts.
- `function-map.md`: canonical schema and conventions for function-by-function mapping.
- `control-loop-atlas.md`: curated atlas of top-level loops, gateways, and subsystem handoffs.
- `runtime-rehost-plan.md`: bottom-up runtime replacement plan and milestone breakdown.
## Repo Conventions
@ -62,17 +63,19 @@ Current local tool status:
## Next Focus
The next milestone is breadth first. The highest-value passes are:
The atlas milestone is broad enough that the next implementation focus shifts downward into runtime
rehosting. The highest-value next passes are:
- promote `docs/control-loop-atlas.md` into the primary human-readable artifact for high-level flow
- name and connect the major loop roots and gateways for startup, shell/UI, frame or presentation,
simulation, map/scenario load, input, save/load, and multiplayer/network
- use `export_startup_map.py` and `export_analysis_context.py` to widen breadth around candidate loop
dispatchers before doing deep leaf naming
- keep the pending-template and multiplayer transport dossiers available, but treat them as targeted
deep-dive tools once a missing atlas edge needs branch-specific grounding
- stand up the Rust workspace so artifacts can be validated in code and a minimal hook DLL can be
built as soon as the 32-bit linker is present
- preserve the atlas and function map as the source of subsystem boundaries while avoiding further
shell-first implementation bets
- stand up a bottom-up runtime core that can load state, execute deterministic world work, and dump
normalized diffs without depending on the shell controller or presentation path
- use `rrt-hook` primarily as an optional capture tool for fixtures and state probes, not as the
first execution environment
- choose early rewrite targets from the lower simulation, event-service, and persistence boundaries
before attempting shell, input, or presentation replacement
- write milestone-scoped implementation notes in `docs/runtime-rehost-plan.md` before expanding the
workspace crates
Regenerate the initial exports with: