Skip to main content

AEROSIM-TS-175 — Replace Coastal Range documentation model

Project task

Replace Coastal Range with the approved documentation terrain model

The existing Coastal Range world renders the exact documentation model with consistent metre scale, bounds, spawn and collision representation.

AEROSIM-TS-175Canonical ID TASK-0175
Verified flow state
To Be Released
Owner
AeroSim Delivery
Component
Coastal Range terrain asset and world-space integration
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Intake the exact manifest-selected documentation Coastal Range GLB, preserve its appearance and bytes, and coherently replace the old runtime asset and metadata. Verify collision and height sampling against the new terrain. Preserve world identity, selection, other terrains, flight controls and physics. Do not regenerate geometry.

Implementation contract

Implementation artifacts

  • assets/manifests/terrain-coastal-range-v1.json
  • assets/runtime/aerosim-owned/worlds/terrain-coastal-range-v1.glb
  • applications/web/src/flight/world/
  • applications/web/src/flight/assets/

Inputs

  • https://discord.com/channels/1518726359512387766/1537227683191197807/1554830285286150144
  • https://discord.com/channels/1518726359512387766/1537227683191197807/1554872096369418241
  • Canonical model page: https://pages.apps.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation/engineering/3d-models/terrains/terrain-coastal-range-v1/
  • The board recovery explicitly authorizes reconciling this missing delivery record without repeated scope or model approval.

Outputs

  • Frozen source revision, complete consumed file inventory, checksums and byte sizes.
  • Manifest-bound new Coastal Range with consistent render, height/collision, spawn and world bounds.
  • Reviewed immutable development GitOps tuple handed to independent UAT.

Failure boundaries

  • Fail closed on asset identity mismatch, unsupported external resources or stale runtime references.
  • Reject inconsistent render/collision transforms or spawn below the terrain.
  • Do not claim synthetic scenery is surveyed or UAT accepted.

Excluded scope

  • No other-world geometry, controls, flight physics, production desired state or release DONE changes.
  • No Delivery browser, integration, E2E or acceptance execution.

Verification steps

  • Unit/static contracts for source identity, transforms, bounds, spawn, collision/height and unchanged world mappings.
  • Full unit, type, lint, build, asset-integrity, exact-head review and remote CI.
  • Immutable publication and reviewed template/rendered development deployment; Argo, pod image, source/chart and endpoint asset readback.
  • UAT verifies ordinary Coastal Range launch, airport/shoreline appearance, ground contact and terrain traversal.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: implementation and immutable development identity verified; reviewed application PR330, template PR85 and development PR62. UAT tuple and checklist posted and read back. Independent UAT acceptance and production release remain pending; not Done.

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.