Skip to main content

AEROSIM-TS-139

Project task

Onboard and render the three selected world scenes

Training Airfield, Coastal Range, and Mountain Valley each render the user-selected scene source as a visibly distinct, governed environment in the active flight viewport.

AEROSIM-TS-139Canonical ID TASK-0139
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Onboard and render the three selected world scenes
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Securely intake the four replacement self-contained GLBs supplied by RootAtSkic, render and objectively evaluate all four, select the best three for the approved world roles, and preserve only the embedded author/source/CC-BY metadata as supplied provenance. Map Mountainous Desert to training-airfield, Snowy Mountain Landscape to coastal-range, and Mountain Range 01 to mountain-valley. Keep Mountain Lake Terrain as an evaluation-only input and do not ship or register it. Deterministically optimize the selected source bytes into manifest-bound runtime GLBs while AeroSim-owned runway, water, collision, spawn, scale, origin, sky, horizon, and flight boundaries remain explicit.

Implementation contract

Implementation artifacts

  • corp-v1-aerosim/corp-v1-aerosim:assets/evaluations/task-0139-scene-selection.json
  • corp-v1-aerosim/corp-v1-aerosim:assets/source/terrain-training-airfield-v1.glb
  • corp-v1-aerosim/corp-v1-aerosim:assets/source/terrain-coastal-range-v1.glb
  • corp-v1-aerosim/corp-v1-aerosim:assets/source/terrain-mountain-valley-v1.glb
  • corp-v1-aerosim/corp-v1-aerosim:assets/runtime/terrain-training-airfield-v1.glb
  • corp-v1-aerosim/corp-v1-aerosim:assets/runtime/terrain-coastal-range-v1.glb
  • corp-v1-aerosim/corp-v1-aerosim:assets/runtime/terrain-mountain-valley-v1.glb
  • corp-v1-aerosim/corp-v1-aerosim:assets/manifests/terrain-training-airfield-v1.json
  • corp-v1-aerosim/corp-v1-aerosim:assets/manifests/terrain-coastal-range-v1.json
  • corp-v1-aerosim/corp-v1-aerosim:assets/manifests/terrain-mountain-valley-v1.json
  • corp-v1-aerosim/corp-v1-aerosim:packages/assets/scripts/intake-task-0139.mjs
  • corp-v1-aerosim/corp-v1-aerosim:packages/assets/scripts/optimize-task-0139.mjs
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/world/WorldTerrainModel.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/world/world-terrain-registry.ts
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/e2e/selected-world-scenes.browser.spec.ts

Inputs

  • RootAtSkic explicitly replaced the earlier scene sources with four uploaded GLBs and instructed Delivery to stop licence investigation and continue technical delivery.
  • All four uploads passed self-contained GLB 2.0 structural parsing with no external resource URI under Node 22.18.0, pnpm 10.15.1, and @gltf-transform 4.5.0.
  • The author, source, and CC-BY fields embedded in each supplied GLB are retained only as supplied provenance without broader interpretation.

Outputs

  • A four-candidate evaluation records exact source hashes, measured geometry, objective visual rationale, and the three selected world mappings.
  • The selected three source GLBs, deterministic optimized runtime GLBs, governed manifests, and production loader mappings ship without synthetic or wrong-world fallback.
  • AeroSim-owned runway, water, collision/height sampling, spawn, world scale, origin, boundary, lighting, sky, and horizon configuration remain separate from decorative imported geometry.
  • Three production-browser screenshots show the exact world, selected aircraft, scene attribution, sky/horizon, and runway or water where applicable.

Failure boundaries

  • Reject archives with unsafe paths, links, unexpected executable content, external resource references, unsupported formats, stale hashes, or incomplete texture dependencies before parser execution.
  • Reject a conversion that loses geometry, UVs, intended PBR appearance, correct normals, metre scale, stable origin, orientation, or required texture channels.
  • Reject runtime output above its approved bytes, triangles, vertices, texture count, texture dimensions, draw calls, GPU-memory, load-time, or frame-time budget.
  • Do not use the imported visual mesh as flight collision without a separately verified collider or height-sampling representation.

Excluded scope

  • Aircraft acquisition and conversion remain TASK-0146; aircraft camera visibility remains TASK-0140.
  • Do not copy Google Earth, Google Maps, marketplace preview renders, or any unlicensed imagery into runtime assets.

Verification steps

  • Verify exact upload hashes, regular-file and no-follow intake, GLB 2.0 structure, embedded resources, supplied metadata match, and parser/resource ceilings before source promotion.
  • Run deterministic optimization twice and require identical runtime bytes and manifests; validate every runtime GLB against byte, triangle, vertex, texture, draw-call, animation, and GPU-memory budgets.
  • Exercise exact and wrong-world mapping, tampered hash, malformed GLB, external URI, unsupported resource, abort, cleanup, and runtime-budget paths; fail closed without a fallback scene.
  • Run Home → Start Your Flight → Flight Setup → Pre-flight → Launch for all three world IDs through the production Nginx/browser path and verify world, catalogue, source revision, terrain asset, physics profile, and visible scene attribution.
  • Capture and visually inspect three attributable screenshots with the aircraft visible and the AeroSim-owned runway or water plus sky and horizon where applicable.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: Application PR #188 merged reviewed head d3745bbe5e912a6c01077487f853a06ea5a5e7c2 as integration revision 22a975cfafbf895e1d05a58f3363984d8a4e3ead. Candidate runs 5144 and 5145 passed; integration run 5147 and immutable image publication run 5146 passed. Three exact manifest-bound world scenes passed production-browser journeys and visual screenshot review. 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.