Skip to main content

AEROSIM-TS-158

Project task

Replace autonomous flight motion with pilot-authoritative dynamics

A neutral aircraft remains in a bounded, trimmable state and ordinary keyboard commands produce directional aircraft responses instead of an autonomous climbing turn.

AEROSIM-TS-158Canonical ID TASK-0158
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — authoritative flight physics and pilot controls
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Bind the declared pitch, bank, yaw, and throttle control values to the one authoritative physics state consumed by rendering, HUD telemetry, cameras, warnings, and recovery. Establish a viable neutral trim for every governed aircraft class; prove opposite commands produce opposite signed motion effects; remove any scripted or default trajectory that overrules pilot input.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/physics/production-physics.ts
  • applications/web/src/flight/authoritative-flight-state.ts
  • applications/web/src/flight/SceneRoot.tsx
  • applications/web/e2e/pilot-control-authority.browser.spec.ts

Inputs

  • Release 1.0.0.2 production UAT executed 36/36 ordinary journeys and passed none.
  • The three-world control diagnostic observed neutral five-second heading changes of -10, -14, and -13 degrees with simultaneous aggressive climbs before pilot input.
  • RootAtSkic reported that the plane circles automatically and keyboard controls do not provide usable flight control in Discord message 1550551559899848705.
  • Three follow-up production recordings confirmed that neutral F-14 flight changed heading from 000 degrees to 341, 341, and 339 degrees while climbing from 39 feet to 193, 197, and 212 feet in the first eight seconds; vertical speed exceeded +7,600 feet per minute before pilot input.
  • RootAtSkic required explicit Tasks for the uncontrollable aircraft and every other observed defect in Discord message 1550583772309889217.

Outputs

  • One authoritative control-to-force/torque path shared by all governed aircraft.
  • Per-class neutral trim that does not enter a climbing turn without input.
  • Directional response evidence for W/S, A/D, Q/E, and R/F from visible HUD and rendered motion.

Failure boundaries

  • Fail when visible control values change but authoritative aircraft motion does not respond in the commanded direction.
  • Fail when neutral flight develops an uncommanded sustained turn, climb, descent, or automatic circuit.
  • Fail when rendering, HUD, cameras, or recovery consume a different state from physics.

Excluded scope

  • No new control scheme, aircraft asset, world asset, or camera mode.

Verification steps

  • Write failing neutral-trim and opposite-command trajectory tests before changing production physics.
  • Launch each aircraft class through ordinary production controls and measure signed heading, vertical-speed, altitude, and airspeed responses during and after each declared command.
  • Sustain neutral and commanded flight for at least 60 seconds without hidden state mutation or direct API setup.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: exact-head tests and ordinary production-browser trajectories establish bounded neutral flight, signed pilot-authoritative response, one authoritative state path, and immutable-image publication for TASK-0158. Release completion was verified on deployed revision dbba4a186a02cb4567c64f1c3400d38556aa1a25; human post-release acceptance remains PENDING.

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.