Skip to main content

AEROSIM-TS-148

Project task

Apply production-scale world-boundary distances

A launched flight remains usable within the intended world area and reaches warning, hard-limit, recovery, and restart states only at governed metre distances.

AEROSIM-TS-148Canonical ID TASK-0148
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Active-flight world-boundary policy
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Replace the unit-ambiguous production values currently interpreted as 120, 180, and 20 metres with an explicit metre-valued world policy selected through Architecture review. Keep the existing knot-to-metre-per-second physics and boundary state machine, bind the policy to launched world configuration, and add regression coverage that rejects immediate critical state during ordinary flight without prescribing unsupported distance values in this Task.

Implementation contract

Implementation artifacts

  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/App.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/boundary/world-boundary-state-machine.ts
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/physics/representative-flight-runtime.ts
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/e2e/release-world-boundary.browser.spec.ts

Inputs

  • Human production acceptance rejected deployed Release 1.0.0.0 because ordinary flight reached a critical world-boundary state almost immediately after launch.
  • Root-cause inspection verified warningDistanceM 120, hardDistanceM 180, and returnHysteresisM 20 while the aircraft travels approximately 436 metres per second at 848 knots.
  • RootAtSkic directed creation of Wave 32 corrective Tasks and Delivery notification in Discord message 1549708626472607755.

Outputs

  • Each supported world declares explicit metre-valued warning distance, hard limit, and return hysteresis, with warning below hard limit and hysteresis positive and bounded.
  • From the canonical Training Airfield spawn using the production initial flight profile, active flight remains NOMINAL for at least 30 continuous seconds; evidence records elapsed time, speed profile, and maximum radial distance, and neither WARNING nor CRITICAL may occur.
  • Deterministic near-boundary tests still prove warning, hard-limit, hysteresis, recovery, termination, and restart behavior without waiting for a real-time long-distance flight.

Failure boundaries

  • Fail when policy values are unit-ambiguous, inconsistent across runtime and tests, or interpreted as metres while authored as kilometre-scale numbers.
  • Fail when the canonical Training Airfield acceptance trajectory reaches WARNING or CRITICAL during its first 30 continuous seconds without being initialized near a governed boundary.
  • Fail when a test treats reaching CRITICAL during normal production flight as success instead of positioning a deterministic fixture near the boundary.

Excluded scope

  • Do not alter the correct knot-to-metre-per-second conversion or replace the boundary state machine without evidence.
  • Do not broaden this correction into terrain collision, new world geometry, or later-release flight-physics scope.

Verification steps

  • Write a failing regression that reproduces the deployed approximately 0.41-second hard-limit crossing from the 180-metre policy.
  • Verify every supported world policy is explicit in metres and that warning distance is below hard limit while hysteresis is positive and bounded; retain the Architecture-reviewed values and evidence.
  • Launch Training Airfield from the canonical spawn through ordinary visible controls using the production initial flight profile; observe 30 continuous seconds, record elapsed time, speed profile, and maximum radial distance, and require NOMINAL throughout.
  • Use deterministic near-boundary initial states to verify warning, hard limit, recovery hysteresis, termination, and clean restart without weakening production thresholds.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: technical release closure for corrective Release 1.0.0.1: application PR #205 merged as ab085692e2ed70bdb6525044b4ca91cc48a27478; integration validation, immutable images, immutable chart 1.0.0+build.2, Harbor readback, GitOps PRs #15 and #25, Argo Synced/Healthy, exact running imageIDs, real Keycloak SSO, protected API/schema access, ordinary Training Airfield launch, more than 30 continuous seconds NOMINAL with no WARNING/CRITICAL, and deterministic boundary acceptance passed. Human post-release acceptance FAILED: RootAtSkic reported in Discord message 1549864663599284236, 'Do long user acceptance testing -> I tried and was not able to fly with any of configuration. It is terrible.' Release 1.0.0.1 is REJECTED for production and requires a replacement release.

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.