Skip to main content

FR-0061

Functional requirement

Provide AeroSim-owned lightweight runtime geometry

StatusProposed

Requirement statement

The system shall provide deterministic, independently authored, lightweight aircraft and world GLBs that preserve governed production identities, anchors, landmarks, and interaction contracts within explicit runtime budgets.

Owner
AeroSim Architecture

Rationale

Current third-party aircraft and terrain assets include complexity not required by AeroSim; purpose-built runtime geometry can reduce browser cost while improving ownership and preserving required production behavior.

Acceptance criteria

Criterion 01

Given
the governed aircraft catalogue and production presentation contracts
When
AeroSim-owned aircraft GLBs are built and evaluated
Then
every required aircraft role remains recognizable and compatible with its scale, axes, anchors, moving parts, collision, controls, and production cameras while meeting agreed runtime budgets
Evidence
Reviewed creation records, deterministic manifests, measurements, and ordinary production-flight screenshots and recordings must verify the exact outcome.

Criterion 02

Given
the governed world catalogue and production world contracts
When
AeroSim-owned terrain and environmental GLBs are built and evaluated
Then
every required world remains distinct and preserves runway, water, mountain, horizon, spawn, scale, collision, height, and navigation cues while meeting agreed runtime budgets
Evidence
Reviewed creation records, deterministic manifests, measurements, and ordinary production-world and long-flight screenshots and recordings must verify the exact outcome.

Traceability

Allocated Features

Owning Tasks