Skip to main content

AEROSIM-TS-114

Project task

Encode the confirmed aircraft and parameters in the launch configuration

The immutable launch configuration contains exactly the confirmed aircraft model identifier and governed flight parameters.

AEROSIM-TS-114Canonical ID TASK-0114
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

Resolve the confirmed AircraftSnapshot to its current model asset and flight parameter set; validate required parameter names, finite numeric values, declared ranges, units, and parameterVersion; then freeze the exact model and coefficients into FlightLaunchConfiguration with sourceRevision.

Implementation contract

Implementation artifacts

  • applications/web/src/session/launch/aircraft-launch-configuration.ts
  • applications/web/src/aircraft/validate-flight-parameters.ts
  • applications/web/test/session/aircraft-launch-configuration.spec.ts

Inputs

  • A confirmed AircraftSnapshot, current catalogue entry, and referenced typed flight parameter set.
  • The complete pre-flight sourceRevision.

Outputs

  • An immutable launch aircraft snapshot containing aircraftId, modelAssetId, parameter set identity/version, normalized coefficients, units, and sourceRevision.

Failure boundaries

  • Missing identifier, stale version, model mapping mismatch, missing coefficient, non-finite value, wrong unit, or out-of-range coefficient returns invalid_aircraft_configuration and emits no launch configuration.
  • Later catalogue or form changes cannot mutate an issued snapshot.

Excluded scope

  • The task validates and freezes configuration but does not load the render model or start simulation.
  • It never substitutes default coefficients or a different aircraft.

Verification steps

  • Run applications/web/test/session/aircraft-launch-configuration.spec.ts and deep-compare the confirmed entry with the frozen model and parameter identities.
  • Inject every parameter validation failure and assert no launch configuration is emitted.
  • Change the catalogue and selection after issue; assert the existing launch snapshot remains unchanged and stale new launch is rejected.

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 #16 reviewed head 2fb202e70c042a37f6cdf6e9d95fa83aabe0ca4d, exact-head validation task 1758 succeeded, merged as efbf3967548f1cbf5e06f97fa9d659535e35a7b4; integrated Gitea Actions publish task 1760 and validate task 1761 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.