Document exact reactive world transport

This commit is contained in:
Meta Vens 2026-07-19 03:30:15 +01:00
commit 3bfcc02d81
2 changed files with 17 additions and 5 deletions

View file

@ -34,9 +34,11 @@ var program = node.Documents
metric "Opacity" bind program.Field(x => x.Layers[1].Opacity)
```
Today the lower substrate exposes reactive document changes through CultMesh /
CultNet database watch streams. The field-level POCO binding handle is the
next ergonomic cut. Eve documents now carry explicit
The lower substrate exposes reactive document changes through CultMesh/CultNet
database watch streams. `CultMeshDocumentHandle<T>.Field(...)` compiles a
member/index selector once and exposes that field as a stable typed pointer;
providers do not need to republish a surface tree when only the value changes.
Eve documents carry explicit
`CultMeshStateBindingDescriptor` values on each component so renderers do not
have to infer provider state from string props:

View file

@ -80,8 +80,11 @@ invent provider semantics to compensate for missing contract information.
`gamecult.eve.entity_soa_view.v1` is the portable descriptor for hot entity
presentation state. A `world.scene2d` or `world.scene3d` component points to it
with `entityViewPointerId`; `entityViewSchema` names the schema. The surface
does not duplicate entity transforms as retained child components.
with `entityViewPointerId`; `entityViewSchema` names the schema and
`entityBodyId` names the stable logical hot body whose representations the
client may demand. Body identity is provider-advertised contract state, not a
provider-specific convention embedded in a lowerer. The surface does not
duplicate entity transforms as retained child components.
World scenes may also publish generic presentation intent derived from provider
state:
@ -187,6 +190,13 @@ bootstrap snapshot. Live entity generations do not. UI values bind to reactive
typed documents named by state pointers. Versioned asset manifests are
bootstrap state and their content-addressed artifacts are cached.
An exact entity subscription includes the view record, the logical body's
stable latest-publication record, the supported body transports, and the
consumer runtime identity. CultMesh combines actual peer locality with those
capabilities to select shared memory for same-machine clients and a network
body plane otherwise. No consumer fetches a second snapshot per generation,
and a provider does not build an unrequested representation.
Provider advertisements attach the reusable boundary to world surfaces through
`surfaces[].worldInteraction`. That block names: