Skip to main content

AEROSIM-TS-111

Project task

Propagate the confirmed world into the launch configuration

The launch configuration contains exactly the canonical world identifier and terrain configuration confirmed during pre-flight.

AEROSIM-TS-111Canonical ID TASK-0111
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — Pre-flight configurator to Flight shell boundary
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Add the confirmed WorldSnapshot to FlightLaunchConfiguration; freeze its complete identifiers and catalogueVersion with the pre-flight source revision; and reject launch configuration creation unless the snapshot is current and resolves to exactly one catalogue entry.

Implementation contract

Implementation artifacts

  • applications/web/src/session/launch/world-launch-configuration.ts
  • applications/web/test/session/world-launch-configuration.spec.ts

Inputs

  • A confirmed WorldSnapshot and current versioned world catalogue.
  • The sourceRevision for the complete pre-flight configuration.

Outputs

  • An immutable launch world snapshot carrying worldId, terrainAssetId, physicsProfileId, catalogueVersion, and sourceRevision.

Failure boundaries

  • Missing confirmation, unknown worldId, changed asset/profile mapping, or stale catalogueVersion returns invalid_world and emits no launch configuration.
  • Edits made after configuration creation produce a new sourceRevision and cannot mutate the issued snapshot.

Excluded scope

  • This task does not fetch assets, construct terrain, or activate a session.
  • Automatic correction or fallback to a default world is excluded.

Verification steps

  • Run applications/web/test/session/world-launch-configuration.spec.ts and deep-compare confirmation with the emitted launch snapshot.
  • Mutate selection and catalogue after issue; assert the issued snapshot remains unchanged and stale launch is rejected.
  • Inject each mapping error and assert no launch configuration is emitted.

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: final application PR #95 reviewed head 49e4252750fb4ca4d6c3ece2a465d2cdaf6d1911 passed exact-head application validation run 3953 attempt 2, merged as f824eec94b86e942f5990217663a0acb433193db, and integration runs 3954 and 3955 succeeded. 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.