Expand runtime event graph service

docs/README.md

@@ -64,19 +64,23 @@ Current local tool status:
 
 ## Next Focus
 
-The atlas milestone is broad enough that the next implementation focus shifts downward into runtime
-rehosting. The highest-value next passes are:
+The atlas milestone is broad enough that the next implementation focus has already shifted downward
+into runtime rehosting. The current runtime baseline now includes deterministic stepping, periodic
+trigger dispatch, normalized runtime effects, fixture execution, state-diff tooling, and initial
+persistence surfaces.
 
-- 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
+The highest-value next passes are now:
+
+- preserve the atlas and function map as the source of subsystem boundaries while continuing to
+  avoid shell-first implementation bets
+- broaden the normalized event-service layer through staged event-record mutation and follow-on
+  record behavior
+- deepen captured-runtime and round-trip fixture coverage on top of the existing runtime CLI and
+  fixture surfaces
+- use `rrt-hook` primarily as optional capture or integration tooling, not as the first execution
+  environment
+- keep `docs/runtime-rehost-plan.md` current as the runtime baseline and next implementation slice
+  change
 
 Regenerate the initial exports with: