Clarify Ymir and Unity migration authority
This commit is contained in:
parent
60adf386c1
commit
a4f6316a2b
2 changed files with 46 additions and 16 deletions
|
|
@ -49,9 +49,9 @@ validation proves contract shape, not wiring, exclusivity, lowering, or parity.
|
|||
## Ownership Invariants
|
||||
|
||||
1. Unity objects never decide durable game state.
|
||||
2. Target invariant: Ymir will own spatial truth; the daemon owns game meaning
|
||||
and persistence. Current state: Aetheria still owns multiple local spatial
|
||||
implementations.
|
||||
2. Aetheria owns spatial state, game meaning, and persistence. The daemon calls
|
||||
Ymir directly as an injected in-process physics library and commits its
|
||||
deterministic results; Ymir never becomes a second daemon or state owner.
|
||||
3. Eve publishes semantic facts and commands, not Aetheria implementation
|
||||
objects or runtime-specific layer numbers.
|
||||
4. Runtime-specific asset metadata may map semantic view channels to native
|
||||
|
|
@ -70,12 +70,13 @@ validation proves contract shape, not wiring, exclusivity, lowering, or parity.
|
|||
|
||||
1. Finish archaeology and replace every `reference` row with exact behavior,
|
||||
source anchors, state inputs, outputs, timing, and proof cases.
|
||||
2. Establish complete daemon/Ymir simulation parity before polishing clients.
|
||||
2. Establish complete daemon simulation parity using the injected Ymir physics
|
||||
port before polishing clients.
|
||||
3. Publish combat, thermal, contact, equipment, docking, trade, and feedback
|
||||
facts through Eve without runtime-specific leakage.
|
||||
4. Implement generic EveUnity presentation primitives and plugin lowering.
|
||||
5. Reconstruct Aetheria's authored composition in `Aetheria.Unity` using those
|
||||
generic primitives and provider assets.
|
||||
5. Delete Unity's reconstructed `Entity`/`Zone`/`Behavior` mirror, then compose
|
||||
`Aetheria.Unity` from generic primitives and provider assets.
|
||||
6. Run scenario parity against the fossil and preserve captures, receipts, and
|
||||
state timelines in conformance packs.
|
||||
|
||||
|
|
@ -138,4 +139,20 @@ These are source-confirmed ownership failures, not feature backlog:
|
|||
Aetheria-local spatial implementations.
|
||||
- Conformance scenarios must preserve source baseline, authoritative state
|
||||
timeline, Ymir timeline, command/receipt chronology, rendered capture,
|
||||
runtime/package versions, and negative-authority results together.
|
||||
runtime/package versions, and negative-authority results together.
|
||||
10. **Unity still reconstructs a mutable gameplay graph.**
|
||||
`AetheriaUnityObservedEntityRestorer`, `AetheriaUnityObservedFrameApplier`,
|
||||
`ActionGameManager`, and `ZoneRenderer` can derive or repair state instead of
|
||||
merely lowering Eve facts. The migration must first publish every required
|
||||
presentation fact, then delete those writers and make Eve entity/node IDs
|
||||
the only presentation identity.
|
||||
11. **Provider asset delivery still contains fossil gameplay scripts.** The
|
||||
daemon publishes semantic asset descriptions and CDN records, but current
|
||||
bundles deserialize prefabs containing missing or Aetheria-specific
|
||||
`MonoBehaviour` components. The first asset conformance slice is the
|
||||
player/ship/station/orbital presentation set, packaged as immutable
|
||||
presentation-only variants and cold-loaded by a clean EveUnity client.
|
||||
12. **Local SoA negotiation is not yet an end-to-end process boundary.** The
|
||||
daemon publishes exact immutable generations and the client rejects stale or
|
||||
mismatched bodies, but the live external client still falls through to an
|
||||
unimplemented network byte reader when it cannot redeem the local capability.
|
||||
|
|
|
|||
|
|
@ -86,10 +86,11 @@ state behind the daemon's back nor writes CultMesh documents of its own. Combat,
|
|||
docking, sensors, AI decisions, damage, inventory, triggers, and event chronology
|
||||
remain Aetheria rules even when they consume Ymir results.
|
||||
|
||||
A remote Ymir host is an optional deployment of the same computation port. It
|
||||
does not earn state authority merely by crossing CultNet. Separate persistence
|
||||
or leases are justified only for a future shared spatial Verse with an explicit
|
||||
owner and lifecycle; they are not part of the Aetheria daemon contract.
|
||||
Ymir is linked into the production daemon as an in-process library behind a
|
||||
narrow injected physics port. That port exists for deterministic substitution
|
||||
and language interop, not to create another daemon, transport, lease domain, or
|
||||
copy of the world. Aetheria owns the input projection and every committed
|
||||
result.
|
||||
|
||||
## Terminus Simulation Clock
|
||||
|
||||
|
|
@ -243,8 +244,16 @@ contract should not be designed as if all Aetheria views are flat maps.
|
|||
|
||||
## Asset Contract
|
||||
|
||||
The daemon advertises assets through typed asset manifests and CultMesh CDN
|
||||
refs. Clients resolve those refs through their runtime asset bridge.
|
||||
The daemon advertises immutable runtime variants through `EveAssetCatalogDocument`
|
||||
and CultMesh CDN manifests/chunks. Each variant declares its content hash, byte
|
||||
size, platform, format, and internal asset key. Clients resolve those refs
|
||||
through their generic runtime asset bridge.
|
||||
|
||||
Unity `Resources` paths and source-project asset paths are packaging inputs, not
|
||||
runtime identity. A migrated provider asset must load in a clean EveUnity client
|
||||
without Aetheria gameplay assemblies. Provider bundles therefore contain
|
||||
presentation-only prefabs and generic EveUnity components, never fossil gameplay
|
||||
`MonoBehaviour` scripts.
|
||||
|
||||
Clients should not synthesize icon paths, substitute improvised SVGs, or embed
|
||||
fallback asset lore when the daemon fails to advertise an asset. A missing asset
|
||||
|
|
@ -264,9 +273,10 @@ own Aetheria gameplay semantics.
|
|||
|
||||
Unity:
|
||||
Current ARPG reference client and migration source. It may own engine
|
||||
presentation, input capture, camera, GameObject restoration, native world-state
|
||||
lowering, and temporary adapters. It should not remain the owner of rules,
|
||||
state, level generation, physics truth, or UI/world semantics.
|
||||
presentation, input capture, camera, generic GameObject projection, native
|
||||
world-state lowering, and temporary adapters. It must not reconstruct mutable
|
||||
Aetheria `Entity`, `Zone`, `Behavior`, or item graphs, and it does not own rules,
|
||||
state, level generation, physics, visibility, or UI/world semantics.
|
||||
|
||||
Godot:
|
||||
Future ARPG conformance runtime. It should prove the ARPG client can be rebuilt
|
||||
|
|
@ -294,6 +304,9 @@ simulation, and authority policy.
|
|||
6. Godot lowers the ARPG contract without Unity scene authority.
|
||||
7. Unity-only simulation, generation, physics, UI semantics, and asset fallback
|
||||
paths are deleted or demoted to renderer presentation.
|
||||
8. The generic Unity client loads provider-published presentation-only assets,
|
||||
lowers exact CultMesh body generations, and contains no Aetheria gameplay
|
||||
assembly reference.
|
||||
|
||||
## Verification Strategy
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue