Add Unity playable world presentation boundary

This commit is contained in:
Meta Vens 2026-07-09 18:14:33 +01:00
commit eef8a5b7aa
11 changed files with 346 additions and 82 deletions

View file

@ -613,11 +613,15 @@ Recently cut:
`EveUnitySceneClientSession` now consumes provider surface snapshots and emits
movement/focus/target/action intents through the advertised command boundary,
while `EveUnitySceneProviderConnection` defines the generic surface source
and command sink ports that a CultMesh/CultNet adapter must implement. The
Unity client boundary is generic before it learns live transport. The next
blocker is the live generic Unity player loop: implement that CultMesh/CultNet
adapter, instantiate the projected world in Unity, and wait for provider
receipts/next frames rather than renderer-local simulation.
and command sink ports that a CultMesh/CultNet adapter must implement.
`EveUnityPlayableWorldPresenter` now maps provider-authored entity rows and
asset refs into scene sink operations, including removal of entities absent
from later provider snapshots, without importing Aetheria entity/prefab
classes. The Unity client boundary is generic before it learns live transport.
The next blocker is the live generic Unity player loop: implement that
CultMesh/CultNet adapter, provide Unity `GameObject`/prefab-backed scene sink
and asset resolver implementations, and wait for provider receipts/next frames
rather than renderer-local simulation.
- EveElectron capture lifecycle now carries the same kind of structured pending
capture contract. `captureContract` names the Electron shell runtime, capture
kind, PNG artifact pattern, conformance attachment point, required Aetheria

View file

@ -484,9 +484,12 @@ active surface and emits `gamecult.eve.command.v1` intents without Aetheria
types. It also declares `providerSurfaceSource` through
`EveUnitySceneProviderConnection`, `IEveUnitySceneProviderSurfaceSource`, and
`IEveUnitySceneCommandSink`, so the live CultMesh/CultNet adapter has a narrow
runtime-owned port to implement. The remaining blocker is that live adapter,
Unity player instantiation, and Unity screenshot or frame-capture PNG production
from EveUnity.
runtime-owned port to implement. The runtime now also declares
`playableWorldScenePresentation`: `EveUnityPlayableWorldPresenter` maps
provider-authored entity rows and asset refs into scene sink operations while
removing entities absent from later provider snapshots. The remaining blocker is
that live adapter, Unity `GameObject`/prefab-backed scene sink and asset
resolver, and Unity screenshot or frame-capture PNG production from EveUnity.
Runtime capture probe coverage is exported as `runtimeCaptureProbeCoverage[]`.
Each record joins runtime status, capture owner, lifecycle capture contract,

View file

@ -163,14 +163,19 @@ radii, asset refs, controllability, and command affordances. The generic
`gamecult.eve.command.v1` intents through the advertised command boundary.
`EveUnitySceneProviderConnection` adds the live-source port shape:
`IEveUnitySceneProviderSurfaceSource` supplies current and updated snapshots,
while `IEveUnitySceneCommandSink` receives command envelopes. Aetheria-specific
names appear only as provider-authored data and command ids; the Unity client
code does not import Aetheria runtime types or apply movement locally.
while `IEveUnitySceneCommandSink` receives command envelopes.
`EveUnityPlayableWorldPresenter` maps the provider-authored entity rows and
asset refs into scene operations through `IEveUnityPlayableWorldSceneSink` and
`IEveUnityPlayableWorldAssetResolver`, including removal of entities that
disappear from later provider snapshots. Aetheria-specific names appear only as
provider-authored data and command ids; the Unity client code does not import
Aetheria runtime types, prefab classes, or apply movement locally.
This is not yet the final playable client. The remaining cut is a live
CultMesh/CultNet provider subscription adapter implementing those source/sink
ports, Unity player instantiation of the projected world, and proof that daemon
receipts drive the next frame rather than renderer-local state.
ports, Unity `GameObject`/prefab-backed implementations of the scene sink and
asset resolver, and proof that daemon receipts drive the next frame rather than
renderer-local state.
## Non-Goals