Introduce the Flight Physics Runtime

Overview

User capability

Establish Rapier and @react-three/rapier for deterministic physics

User

The AeroSim delivery team

What the user can do

Establish Rapier and @react-three/rapier for deterministic physics

Why the user benefits

The capability becomes an explicit, testable project boundary.

User need

The delivery team needs the AeroSim solution to establish Rapier and @react-three/rapier for deterministic physics.

In scope

Establish Rapier and @react-three/rapier for deterministic physics

• StatusProposed
• OwnerAeroSim Scope (proposed; not accepted)
• Parent EpicAEROSIM-EP-1
• Depends onAEROSIM-FT-45

Tasks

AEROSIM-TS-28Planning status: Done

Define the deterministic fixed-step simulation boundary

The browser flight runtime advances simulation through one documented fixed-step clock with explicit input, initial-state, and output contracts.

• ComponentWeb Application — deterministic flight runtime
• Depends onAEROSIM-TS-27
• RequirementsFR-0053, NFR-0007

AEROSIM-TS-29Planning status: Done

Integrate Rapier aircraft motion and collision state

Rapier and @react-three/rapier advance representative aircraft motion and collision state through the fixed-step boundary.

• ComponentWeb Application — Rapier physics adapter
• Depends onAEROSIM-TS-28
• RequirementsFR-0053, NFR-0007

AEROSIM-TS-30Planning status: Done

Add deterministic motion and collision regressions

Repeated runs from identical initial state and fixed inputs produce equivalent motion and collision results within declared tolerances.

• ComponentWeb Application — deterministic physics regression suite
• Depends onAEROSIM-TS-29
• RequirementsFR-0053, NFR-0007

Acceptance outcomes

1. 01

   Rapier advances aircraft and collision state through the documented deterministic simulation step.

2. 02

   Repeated fixed inputs and initial state pass motion and collision regression tests.

Functional requirements and measurable criteria

FR-0053

Introduce the Flight Physics Runtime

The system shall establish Rapier and @react-three/rapier for deterministic physics.

Acceptance 01

GivenAEROSIM-FT-46 is exercised within its governed scope under supported conditions

Whenthe primary capability path is completed

ThenRapier advances aircraft and collision state through the documented deterministic simulation step

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Acceptance 02

GivenAEROSIM-FT-46 is exercised within its governed scope under supported conditions

Whenthe continuation or repeat path is completed

ThenRepeated fixed inputs and initial state pass motion and collision regression tests

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Non-functional requirements

• NFR-0007 — Engineering reproducibility and supply-chain integrity

  Repeated validation from the same immutable inputs produces equivalent artifacts and rejects unlicensed, untraceable, invalid, or over-budget inputs.

Risks

• Risk

  Partial introduction could leave an ungoverned or duplicated technical boundary.

Original source and prototype evidence

• discord: Engineering Features grounded in the selected AeroSim technology stack.
• discord: Engineering Feature decomposition continuation.
• discord: RootAtSkic directed publication of the agreed Scope update.

Prototype and discovery boundary

Existing implementation is discovery evidence only; it establishes no current approval, acceptance, or release state.