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

feat(runtime): own SetPosition collision reports

Browse source
This commit is contained in:
Erik 2026-08-01 00:15:11 +02:00
parent ec627c13a2
commit 237d1184d2
19 changed files with 3744 additions and 103 deletions
Download patch file Download diff file Expand all files Collapse all files

20
memory/project_collision_port.md
View file

@ -1,5 +1,25 @@
# Collision System Port - Status and Plan
## 2026-07-31 placement checkpoint 2
Runtime now owns the retail collision-report state required by canonical
SetPosition: exact-incarnation object-contact tables, the environment latch,
ordinary/ethereal expiry, force-end ordering, asymmetric object/environment
report eligibility, missile-state clearing, reentrant ordered reports, and the
report-result boolean which distinguishes failed-placement `Collided` from
`NoValidPosition`. Successful dormant SetPosition commits reporting after
contact/ground state and before its one response plus shadow reflood. The
named-retail oracle and next-agent instructions are in:
- `docs/research/2026-07-31-runtime-set-position-collision-reporting.md`
- `docs/research/2026-07-31-runtime-set-position-collision-reporting-handoff.md`
This checkpoint deliberately does not activate production placement. Next,
4B2 must prepare exact authored movers and land one atomic Runtime body/local-
controller transaction, followed by presentation-only host projection,
collision-prefix quiescence, and an all-route cutover. AP-1 and AD-1 remain
open until that cutover; AP-22 and AD-10 remain later campaign slices.
## Current State (2026-04-29)
The collision system is no longer a pure placeholder and should not be treated