Skip to main content

AEROSIM-TS-160

Project task

Repair production world identity and terrain composition

Training Airfield, Coastal Range, and Mountain Valley each render their selected identity with continuous usable terrain and no voids, black wedges, or mismatched world content.

AEROSIM-TS-160Canonical ID TASK-0160
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — production world identity and terrain composition
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Correct production world-to-asset mapping, terrain transforms, seams, depth ordering, presentation bounds, and recovery limits. Training Airfield must read as an airfield; Coastal Range must visibly contain coherent coastal/water composition; Mountain Valley must not expose empty or black frames.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/world-terrain-registry.ts
  • applications/web/src/flight/terrain/WorldTerrainModel.tsx
  • applications/web/src/flight/world-space-contract.ts
  • applications/web/e2e/production-world-identity.browser.spec.ts

Inputs

  • Release 1.0.0.2 UAT screenshots show mountainous desert content and large dark wedges under Training Airfield.
  • Coastal Range screenshots show mountain-only composition and black/empty frames in J04, J09, and J12.
  • Mountain Valley screenshots show black/empty frames in J03 and J07 plus severe terrain/camera clipping.
  • Follow-up production videos retain the same wrong world identity over approximately 52 seconds per world: Training Airfield lacks a readable airfield, Coastal Range lacks coherent coast/water composition, and Mountain Valley permits terrain intersection before attempt replacement.

Outputs

  • Exact selected-world identity, attribution, transforms, and presentation bounds.
  • Continuous rendered terrain and correct water/depth composition without voids or opaque polygon wedges.
  • World-specific recovery bounds that do not immediately force a low-altitude reset.

Failure boundaries

  • Fail when selected-world labels and visible content disagree.
  • Fail on any blank, black, void, opaque seam, terrain slice, or water/terrain intersection that makes flight unusable.
  • Fail when one world's asset or attribution appears in another world.

Excluded scope

  • No replacement asset may be selected without verified provenance, licence, and human visual review.

Verification steps

  • Add screenshot and pixel-difference regressions for each exact world before correction.
  • Run ordinary 60-second flight journeys in all four cameras for every world and inspect final screenshots.
  • Verify visual terrain, collision, spawn, camera bounds, and recovery bounds use the same authored world-space record.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: exact-head and exact-integration browser journeys show each selected production world with its governed identity, continuous usable terrain, correct coastal water composition, and zero black, empty, void, or opaque-wedge frames across all four cameras. 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.