erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(physics): close Slice I evidence and roadmap

Browse source 
Record the accepted flat-authoritative collision cutover, production parsed-graph removal, exact rollbacks, zero-residency connected gates, and RDP measurement boundary. Reconcile architecture, milestones, roadmap, issue ledger, agent instructions, and the active Slice J handoff.

Validated by the existing zero-warning Release build, 8,413 passing Release tests with five pre-existing skips, 201 focused closeout tests, and both exact-binary connected routes.

Co-authored-by: Codex <codex@openai.com>
This commit is contained in:
Erik 2026-07-25 18:44:43 +02:00
parent 82f8d4f82e
commit afebbe3eca
11 changed files with 257 additions and 71 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/plans/2026-07-25-modern-runtime-slice-j.md
View file

@ -1,7 +1,7 @@
# Modern runtime Slice J — presentation-independent runtime
**Status:** J0 COMPLETE — lifetime plan, project boundary, and dependency
guards; J1 waits for the Slice I6/I7 user collision/visual closeout
guards; Slice I is closed and J1 is ACTIVE
**Parent:** `2026-07-24-modern-runtime-architecture.md`, Slice J
**Authorization:** the user approved Slices F–L, including the otherwise-frozen
Slice J gameplay-owner moves, on 2026-07-24
@ -36,9 +36,10 @@ deletes the replaced App production path before the next group moves.
9. A headless construction path is proved after every coherent move. “No
window” means no App, Silk, OpenAL, retained UI, particle, or render assembly
is loaded—not a hidden graphical process.
10. The user collision/visual gate for Slice I6 still controls parsed-graph
deletion. J0 may land independently; gameplay-owner moves begin only after
the active I6/I7 closeout has reconciled the final collision owner shape.
10. Slice I is closed: production collision is flat-authoritative and retains
no parsed collision graph. J1 contracts adapt that final canonical owner
shape; they may not reintroduce a graph fallback or mirrored collision
authority.
## 2. Target dependency direction