Introduce the 3D Asset Pipeline

Overview

User capability

Establish governed glTF/GLB sourcing, licensing, provenance, and optimization

User

The AeroSim delivery team

What the user can do

Establish governed glTF/GLB sourcing, licensing, provenance, and optimization

Why the user benefits

The capability becomes an explicit, testable project boundary.

User need

The delivery team needs the AeroSim solution to establish governed glTF/GLB sourcing, licensing, provenance, and optimization.

In scope

Establish governed glTF/GLB sourcing, licensing, provenance, and optimization

• StatusProposed
• OwnerAeroSim Scope (proposed; not accepted)
• Parent EpicAEROSIM-EP-1
• Depends onAEROSIM-FT-45

Tasks

AEROSIM-TS-35Planning status: Done

Define the governed 3D asset manifest

Every runtime 3D asset can be described by a validated manifest containing source, license, provenance, format, optimization, and budget metadata.

• ComponentWeb Application / R3F flight scene — Shared asset pipeline — provenance and budget manifest
• Depends onAEROSIM-TS-27
• RequirementsFR-0055, NFR-0007

AEROSIM-TS-36Planning status: Done

Implement reproducible glTF and GLB optimization

Supported source assets are converted or optimized to deterministic runtime glTF/GLB artifacts with measured budget metadata.

• ComponentWeb Application / R3F flight scene — Shared asset pipeline — glTF/GLB optimizer
• Depends onAEROSIM-TS-35
• RequirementsFR-0055, NFR-0007

AEROSIM-TS-37Planning status: Done

Enforce asset provenance, format, and budgets

Automated validation admits only licensed, traceable, supported, and within-budget runtime assets.

• ComponentWeb Application / R3F flight scene — Shared asset pipeline — policy validator
• Depends onAEROSIM-TS-36
• RequirementsFR-0055, NFR-0007

AEROSIM-TS-38Planning status: Done

Verify governed asset loading in the flight scene

The Web Application loads a validated optimized asset through the governed manifest and cannot import an unregistered runtime asset.

• ComponentWeb Application — governed runtime asset loader
• Depends onAEROSIM-TS-37
• RequirementsFR-0055, NFR-0007

AEROSIM-TS-146Planning status: Done

Onboard the nine shortlisted aircraft models

AeroSim has three governed Trainer candidates, three governed Fighter candidates, and three governed Utility candidates available through its internal asset registry and aircraft catalogue instead of the synthetic one-triangle fixture.

• ComponentOnboard nine governed aircraft model candidates
• Depends onAEROSIM-TS-35, AEROSIM-TS-36, AEROSIM-TS-37, AEROSIM-TS-38
• RequirementsFR-0055

AEROSIM-TS-150Planning status: Done

Normalize all production aircraft presentation assets

Every one of the nine governed aircraft assets enters flight through one validated production presentation contract with deterministic centre, scale, forward/up axes, render anchor, collision anchor, and cockpit anchor metadata.

• ComponentWeb Application — production aircraft presentation contract
• Depends onAEROSIM-TS-146
• RequirementsFR-0055

Acceptance outcomes

1. 01

   Each runtime asset is optimized to glTF/GLB and has source, license, provenance, and budget metadata.

2. 02

   Validation rejects an unlicensed, untraceable, unsupported, or over-budget asset.

Functional requirements and measurable criteria

FR-0055

Introduce the 3D Asset Pipeline

The system shall establish governed glTF/GLB sourcing, licensing, provenance, and optimization.

Acceptance 01

GivenAEROSIM-FT-48 is exercised within its governed scope under supported conditions

Whenthe primary capability path is completed

ThenEach runtime asset is optimized to glTF/GLB and has source, license, provenance, and budget metadata

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Acceptance 02

GivenAEROSIM-FT-48 is exercised within its governed scope under supported conditions

Whenthe continuation or repeat path is completed

ThenValidation rejects an unlicensed, untraceable, unsupported, or over-budget asset

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Non-functional requirements

• NFR-0007 — Engineering reproducibility and supply-chain integrity

  Repeated validation from the same immutable inputs produces equivalent artifacts and rejects unlicensed, untraceable, invalid, or over-budget inputs.

Risks

• Risk

  Partial introduction could leave an ungoverned or duplicated technical boundary.

Original source and prototype evidence

• discord: Engineering Features grounded in the selected AeroSim technology stack.
• discord: Engineering Feature decomposition continuation.
• discord: RootAtSkic directed publication of the agreed Scope update.

Prototype and discovery boundary

Existing implementation is discovery evidence only; it establishes no current approval, acceptance, or release state.