docs(physics): hand off placement continuation executor
Synchronize the architecture doc, milestones, roadmap, and ISSUES with the
continuation-executor behavior commit (5db3de3c): the residence system is
now a complete dormant mechanism, both independent reviews PASS, and the
next boundary is the all-host production cutover. The admission handoff
gains its superseded banner; the successor handoff records the executor's
ownership, the retail anchors proven during review (the wire-contact gate,
queue-by-parent-GUID relation replay, HasAnims semantics), the seven new
register rows, exact test totals, the rollback command, and the cutover
checklist. #275 filed for the post-cutover legacy-Position unification.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
5db3de3c7a
commit
9ad590dcc7
6 changed files with 288 additions and 17 deletions
|
|
@ -233,6 +233,9 @@ src/
|
|||
boundary for dormant initial placement
|
||||
RuntimeInitialCreateResidenceState.cs -> exact-incarnation initial
|
||||
placement lease and accepted mixed-update FIFO
|
||||
RuntimeInitialCreateContinuationExecutor.cs -> retry-idempotent
|
||||
adoption + retail Create tail + strict-order
|
||||
FIFO/replay execution over the residence
|
||||
Gameplay/
|
||||
RuntimeCommunicationState.cs -> one chat/social owner + ordered stream
|
||||
RuntimeInventoryState.cs -> exact object-table borrower + inventory
|
||||
|
|
@ -608,9 +611,25 @@ entity key. A Create whose parent is not yet addressable is retained even
|
|||
earlier as a complete raw packet, before child timestamp admission, and is
|
||||
guarded by a non-reused admission token. Delete, generation replacement,
|
||||
reset, GUID reuse, and reentrant teardown discard only the matching ownership.
|
||||
This checkpoint (`30012361`) intentionally stops before executing the FIFO or
|
||||
switching graphical/no-window production routes; that later cutover must use
|
||||
this owner rather than create another snapshot or placement path.
|
||||
The admission checkpoint (`30012361`) intentionally stopped before executing
|
||||
the FIFO. The continuation executor (`5db3de3c`,
|
||||
`RuntimeInitialCreateContinuationExecutor`) completes the mechanism: one
|
||||
synchronous, retry-idempotent `Execute` transaction adopts the acknowledged
|
||||
initial placement exactly once, emits the local player's after-enter-world
|
||||
hook request, replays deferred missing-parent raw Creates and queued parent
|
||||
relations by parent GUID (whole-bucket detach, FIFO dispatch,
|
||||
cancellation-aware restore windows), and drains the mixed FIFO strictly by
|
||||
sequence — classifying each retained Position at execution time with live
|
||||
inputs and driving authored placements through the canonical
|
||||
`RuntimeSetPositionState` lifecycle with retryable yields. Apply bodies are
|
||||
shared with the legacy fused inbound paths through gate-less instance seams
|
||||
that keep the one snapshot store in lockstep; same-incarnation Create
|
||||
envelopes apply atomically with buffered publication; every abandonment path
|
||||
retires the residence and converges the combined ownership ledger. The
|
||||
executor has NO production caller yet — graphical and no-window Create still
|
||||
use legacy `RegisterEntity` — and the next checkpoint must switch both
|
||||
production routes onto this owner rather than create another snapshot or
|
||||
placement path.
|
||||
|
||||
`LiveEntityRuntime` is the App projection/lifecycle host.
|
||||
`RegisterLiveEntity` first creates or refreshes canonical Runtime state without
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue