Skip to main content

AEROSIM-TS-112

Project task

Load the confirmed terrain configuration for the session

The new flight session renders and collides against the world identified by the immutable launch configuration.

AEROSIM-TS-112Canonical ID TASK-0112
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — R3F flight scene and deterministic flight runtime
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Resolve the launch world snapshot to one terrain asset and physics profile; load both under the reserved session initialization context; verify their identifiers and catalogueVersion; activate the R3F terrain and Rapier collision world as one transaction; and expose SessionWorldState only after both are ready.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/world/initialize-session-world.ts
  • applications/web/src/flight/world/session-world-state.ts
  • applications/web/test/flight/initialize-session-world.spec.ts

Inputs

  • An immutable launch world snapshot and loaders for its terrain asset and physics profile.
  • A reserved session initialization context that is not yet active.

Outputs

  • SessionWorldState with the applied identifiers, catalogueVersion, and ready state.
  • One active render terrain and one matching collision world bound to the session.

Failure boundaries

  • Unresolved identifier, asset-load error, physics-profile error, identifier mismatch, or cancellation tears down all partial world resources and leaves the session inactive.
  • A repeated initialization command for the same context returns the existing result and does not create duplicate terrain or collision objects.

Excluded scope

  • No fallback terrain is selected and no failed load is retried automatically.
  • World authoring and in-flight environmental changes are excluded.

Verification steps

  • Run applications/web/test/flight/initialize-session-world.spec.ts and assert render and collision identifiers equal the launch snapshot.
  • Fail each load stage and cancel between stages; assert resources are disposed and no SessionWorldState is ready.
  • Repeat the same initialization command and assert exactly one render terrain and collision world exist.

Traceability

Requirements

Dependencies

UI/UX applicability

non_visual

This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.

Acceptance evidence

Verified delivery: application PR #101 reviewed head 5eb16ee352dff502a27ade311295082dbd16b05d passed exact-head required jobs 3048, 3049, 3050, 3052, 3053, 3054, and 3055, merged as 90bed03f05b6dc32214e26a39f9a8c2f22201b33, and exact integration/publication tasks 3056, 3057, 3058, and 3060 succeeded. The reviewed implementation loads and validates the immutable launch world configuration, atomically activates matching R3F terrain and Rapier collision resources, exposes readiness only after both succeed, rejects stale or mismatched provenance, tears down partial resources, and preserves one idempotent result per reserved context. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.