AeroSim focus
For a Task, READY_FOR_DELIVERY means it is already admitted to Focus and available for Delivery pickup. Use the Task Board to identify the current dependency wave; when Delivery capacity is available, Delivery must claim the next eligible Task and record its transition to IN_PROGRESS. No separate Focus-admission decision follows READY_FOR_DELIVERY.
Focus also shows canonical IN_BACKLOG, Task IN_PROGRESS, product IN_DELIVERY, and TO_BE_RELEASED work needed to preserve the governed delivery context.
- IN_BACKLOG
- READY_FOR_DELIVERY
- IN_PROGRESS
- IN_DELIVERY
- TO_BE_RELEASED
View accessible data table
| Canonical item | Type | Focus state | Status basis | Lifecycle | Owner | Parent | Dependencies | Target version | Open questions | Latest evidenced decision |
|---|---|---|---|---|---|---|---|---|---|---|
| AEROSIM-EP-1 — Establish the AeroSim Engineering Foundation | Epic | IN_DELIVERY | Required-child roll-up | Proposed | AeroSim Scope | None | None | Not allocated | None | 2026-10-01 |
| AEROSIM-EP-3 — Believable Aircraft and World Behaviour | Epic | TO_BE_RELEASED | Required-child roll-up | Proposed | AeroSim Scope | None | None | Not allocated | None | 2026-09-29 |
| AEROSIM-EP-4 — Complete a Free-Flight Session | Epic | IN_DELIVERY | Required-child roll-up | Proposed | AeroSim Scope | None | None | Not allocated | None | 2026-09-29 |
| AEROSIM-EP-5 — Configure and Launch a Flight | Epic | IN_DELIVERY | Required-child roll-up | Proposed | AeroSim Scope | None | None | Not allocated | None | 2026-09-27 |
| AEROSIM-FT-1 — Experience Aircraft Motion Produced by Flight Forces | Feature | TO_BE_RELEASED | Required-child roll-up | Proposed | AeroSim Scope | AEROSIM-EP-3 | None | Not allocated | None | 2026-09-29 |
| AEROSIM-FT-17 — Select the Initial Camera | Feature | TO_BE_RELEASED | Required-child roll-up | Proposed | AeroSim Scope | AEROSIM-EP-5 | AEROSIM-FT-12 (Proposed) | Not allocated | None | 2026-09-27 |
| AEROSIM-FT-4 — Understand Aircraft State and Control Response | Feature | IN_DELIVERY | Required-child roll-up | Proposed | AeroSim Scope | AEROSIM-EP-4 | AEROSIM-FT-3 (Proposed) | Not allocated | None | 2026-09-29 |
| AEROSIM-FT-45 — Introduce the 3D Rendering Runtime | Feature | TO_BE_RELEASED | Required-child roll-up | Proposed | AeroSim Scope | AEROSIM-EP-1 | AEROSIM-FT-41 (Proposed) | Not allocated | None | 2026-10-01 |
| AEROSIM-FT-47 — Introduce the Terrain Pipeline | Feature | TO_BE_RELEASED | Required-child roll-up | Proposed | AeroSim Scope | AEROSIM-EP-1 | AEROSIM-FT-45 (Proposed), AEROSIM-FT-46 (Proposed) | Not allocated | None | 2026-09-29 |
| AEROSIM-TS-171 — Remove redundant camera confirmation step | Task | TO_BE_RELEASED | Exact item evidence | ToBeReleased | AeroSim Architecture and Delivery | AEROSIM-FT-17 | AEROSIM-TS-136 (Done) | 1.0.0 | None | 2026-09-27 |
| AEROSIM-TS-172 — Correct Training Airfield UAT imagery seams and atmospheric continuity | Task | TO_BE_RELEASED | Exact item evidence | ToBeReleased | AeroSim Delivery | AEROSIM-FT-47 | AEROSIM-TS-160 (Done) | 1.0.0 | None | 2026-09-29 |
| AEROSIM-TS-173 — Correct hidden terminal flight state after automatic recovery | Task | TO_BE_RELEASED | Exact item evidence | ToBeReleased | AeroSim Delivery | AEROSIM-FT-1 | AEROSIM-TS-158 (Done) | 1.0.0 | None | 2026-09-29 |
| AEROSIM-TS-174 — Compact flight controls into the right-side HUD and match Camera to Menu | Task | TO_BE_RELEASED | Exact item evidence | ToBeReleased | AeroSim Delivery | AEROSIM-FT-4 | AEROSIM-TS-125 (Done) | 1.0.0 | None | 2026-09-29 |
| AEROSIM-TS-175 — Replace Coastal Range with the approved documentation terrain model | Task | TO_BE_RELEASED | Exact item evidence | ToBeReleased | AeroSim Delivery | AEROSIM-FT-45 | AEROSIM-TS-139 (Done) | 1.0.0 | None | 2026-10-01 |
The React Flow graph is the primary Focus view. It excludes IN_DESIGN and terminal records and builds lane membership, hierarchy edges, fallback rows, and the explicit empty state from one adapter. It never fabricates work to populate a lane.
Current admission
The exact verified READY_FOR_DELIVERY flow transition is the Focus admission record. Exact verifier-admitted Task flow drives Task status. Parent Feature and Epic status uses the deterministic required-child roll-up. The status value remains canonical, while Status basis distinguishes Exact item evidence from Required-child roll-up. All linked open question IDs remain binding approval conditions.
Release 1.0.0 Waves 33–35 are complete. Wave 33 Tasks AEROSIM-TS-149 through AEROSIM-TS-156, Wave 34 AEROSIM-TS-157, and Wave 35 AEROSIM-TS-158 through AEROSIM-TS-163 are DONE. The Wave 33–34 records were reconciled against the same cumulative deployed application revision that closed Wave 35; every earlier integration revision is an ancestor of that deployed revision. Human post-release acceptance remains recorded separately from technical Task closure.
No Release 1.0.0 Task is currently pickup-ready. Release 2.0 Wave 36 Tasks AEROSIM-TS-164 through AEROSIM-TS-167 remain IN_BACKLOG; they are not admitted Delivery work until an exact READY_FOR_DELIVERY transition exists.
The historical rejected-production findings that caused Waves 33–35 remain preserved in their Task and release evidence. Completion records do not erase the rejected release identities, UAT results, or corrective-release provenance.
Prerequisite evidence is verified before that transition is recorded: the Task must have a stable ID and parent, governed Architecture evidence, dependencies and conditions, owner/capability and sequencing evidence, and an authorized exact-task transition. After the transition exists, Delivery does not request or record another Focus-admission decision.
Task movement to IN_PROGRESS requires explicit canonical flow evidence backed by Delivery. Movement to TO_BE_RELEASED requires implementation and release-handoff evidence. Every explicit Task flow transition is an append-only flow_history event bound to the exact item and target state, trusted actor and authority, UTC decision date, conditions, evidence gate, durable event-specific evidence, previous-event hash, computed hash, and immutable baseline. A bare or forged flow_state fails validation.
Decision authority: RootAtSkic's AeroSim delegation.