Skip to main content

AEROSIM-TS-152

Project task

Author one world-space and Coastal compositing contract

Terrain presentation, spawn, collision, aircraft presentation, and camera coordinates share one authored world-space contract, and Coastal Range renders correct water depth/transparency and visible content attribution.

AEROSIM-TS-152Canonical ID TASK-0152
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — governed terrain and flight world space
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Define one versioned world-space record per governed world covering origin, units, horizontal/vertical scale, terrain transform, spawn transform, collision transform, presentation bounds, camera bounds, water plane, render order, depth behavior, and attribution. Make production terrain, collision, spawn, aircraft presentation, and camera consumers use that record. Correct Coastal water transparency/depth ordering and the visible world-specific content/attribution without changing the selected world ID.

Implementation contract

Implementation artifacts

  • corp-v1-aerosim/corp-v1-aerosim:assets/manifests/terrain-*.json
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/terrain/WorldTerrainModel.tsx
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/world-terrain-registry.ts
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/src/flight/world-space-contract.ts
  • corp-v1-aerosim/corp-v1-aerosim:applications/web/test/flight/world-space-contract.browser.spec.ts

Inputs

  • RootAtSkic authorized Wave 33 correction work in Discord message 1549867630800666695 and then asked the exact completeness question in message 1549881095363760179; this admission supplies the missing repair Tasks without modifying the separately claimed TASK-0149.
  • Deployed application source ab085692e2ed70bdb6525044b4ca91cc48a27478 for product 1.0.0.1; release 1.0.0.1 remains deployed, human acceptance FAILED, production REJECTED, and a replacement release is required.
  • Ordinary-user UAT evidence: /opt/data/corp-v1-aerosim-releases/workspace/uat-1.0.0.1-training-airfield-rerun/report.md and report.json (12/12 failed), /opt/data/corp-v1-aerosim-releases/workspace/uat-1.0.0.1-coastal-range/uat-report.md and uat-report.json (12/12 failed), and /opt/data/corp-v1-aerosim-releases/workspace/uat-1.0.0.1-mountain-valley/report.md and report.json (12/12 failed). All three runs prohibit forced clicks, hidden-input interaction, DOM/state mutation, direct API setup, or other bypass.
  • Diagnosed root-cause records: /opt/data/cache/delegation/subagent-summary-0-20260916_203916_911368.txt, /opt/data/cache/delegation/subagent-summary-1-20260916_203916_911707.txt, /opt/data/cache/delegation/subagent-summary-2-20260916_203916_911857.txt.
  • Root-cause summary 0 lines 29-38: WorldTerrainModel independently scales decorative-only terrain while physics uses representative collider space; Coastal water intersects terrain with transparent depthWrite=true and no render ordering.
  • Root-cause summary 0 lines 45-48 and Training Airfield rerun report line 50 show hardcoded unrelated attribution/content. Coastal UAT shows turquoise water slicing mountains and snowy-mountain attribution across camera modes.

Outputs

  • One authored world-space record for each governed world, consumed by visual terrain, spawn, collision, presentation, and cameras.
  • Coastal water has explicit transparent depth/render ordering and cannot occlude or tint terrain incorrectly.
  • Visible attribution and content resolve only from the selected world manifest.

Failure boundaries

  • Fail when any consumer applies an independent scale/origin/elevation mapping, terrain remains decorative-only relative to collision, or spawn/camera/presentation coordinates cannot be converted through the authored contract.
  • Fail when Coastal water writes or orders depth incorrectly, cuts through terrain, exposes a void, or visible attribution/content does not match the selected world.

Excluded scope

  • No application implementation is performed by this admission change.
  • Do not rewrite TASK-0149, infer a router-retention defect, report working Menu Restart as failed, classify static STALL SPEED 140 KT specification text as an active warning, or broaden governed interaction scope beyond the exact interaction semantics stated here.

Verification steps

  • Tests first: add failing transform-parity, terrain/collision probe, Coastal depth-order, and attribution/content tests before changing production world composition.
  • Probe authored locations in all governed worlds and assert rendered and collision elevation, spawn, presentation bounds, and camera bounds agree within the existing governed tolerance.
  • Launch each world through ordinary visible browser controls and capture moving-flight pixel evidence, including Coastal terrain/water seams and world-specific attribution. No forced click, hidden input, direct registry/state mutation, API setup, or browser bypass is acceptance evidence.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: the governed world-space contract is consumed by production terrain, collision, spawn, presentation, and camera paths; Coastal water depth/render ordering and selected-world attribution are verified; ordinary visible-control moving-flight acceptance passed in all three worlds; exact-head and post-merge integration CI passed; and immutable Nebula and Singularity images were published and read back from Harbor. Replacement-release acceptance remains Release-owned.

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.