Phase 5 step 1
This commit is contained in:
@@ -7,8 +7,8 @@ Phase 1 named the subsystems. Phase 2 added the typed event substrate. Phase 3 m
|
||||
## Status
|
||||
|
||||
- Phase 5 design package: proposed.
|
||||
- Phase 5 implementation: not started.
|
||||
- Current alignment: Phase 3 introduced the first pure composition boundary and transient OSC overlay owner, but committed runtime values are still physically stored through `RuntimeStore`/`LayerStackStore`, and transient OSC overlay state is applied through render-facing helpers rather than through a first-class layered state model.
|
||||
- Phase 5 implementation: Step 1 started.
|
||||
- Current alignment: Phase 3 introduced the first pure composition boundary and transient OSC overlay owner, and Phase 5 now has a small `RuntimeStateLayerModel` inventory that names the current state categories. Committed runtime values are still physically stored through `RuntimeStore`/`LayerStackStore`, and transient OSC overlay state is still applied through render-facing helpers rather than through the final layered composition contract.
|
||||
|
||||
Current live-state footholds:
|
||||
|
||||
@@ -18,6 +18,7 @@ Current live-state footholds:
|
||||
- `RuntimeLiveState` owns transient OSC overlay bookkeeping, smoothing, generation tracking, and commit-settlement policy.
|
||||
- `RenderStateComposer` combines base render states with live overlay state and returns final per-frame layer states plus settled commit requests.
|
||||
- `RuntimeServiceLiveBridge` drains OSC ingress/completion queues and applies them to render live state during frame preparation.
|
||||
- `RuntimeStateLayerModel` names the Phase 5 state categories and classifies current fields as base persisted, committed live, transient automation, render-local, or health/config state.
|
||||
|
||||
## Why Phase 5 Exists
|
||||
|
||||
@@ -239,9 +240,9 @@ Document and/or encode where each current state category lives:
|
||||
|
||||
Initial target:
|
||||
|
||||
- identify which fields are durable, committed-live, transient automation, render-local, or health/config
|
||||
- update subsystem docs where the current ownership is misleading
|
||||
- add small tests for classification if a pure helper exists
|
||||
- [x] identify which fields are durable, committed-live, transient automation, render-local, or health/config
|
||||
- [x] update subsystem docs where the current ownership is misleading
|
||||
- [x] add small tests for classification if a pure helper exists
|
||||
|
||||
### Step 2. Name The Layered Composition Input
|
||||
|
||||
|
||||
Reference in New Issue
Block a user