AeroSim

Field	Value
Code	aerosim
Status	Active — lifecycle alignment reviewed
Started	2026-08-12
Sponsor and accountable lead	RootAtSkic
Team members	RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; Piotras; Andrius; Dovydas; Giedrius K; jarvis-at-skic / Hermes code agent; friday-at-skic / Friday code agent
Team	AeroSim Team

Purpose

Build a browser-based flight simulator supporting several aircraft classes with a shared, extensible flight model and scenario system.

Initial deliverable

A playable MVP covering a light trainer, commercial airliner, and fighter-style aircraft, with shared flight controls, live telemetry, basic safety warnings, and foundational scenarios.

Success measures

• A browser user can select and control all three aircraft classes.
• Shared flight behavior is implemented in a reusable typed package.
• Web and API applications build, test, and package independently.
• Architecture, user guidance, ways of working, and engineering standards are published.
• CI validates the monorepo and documentation on every change.

Scope

• Browser simulator cockpit and controls.
• Trainer, airliner, and fighter-style aircraft profiles.
• Shared flight-core package and API endpoints.
• Docker and Helm packaging.
• Documentation and architecture sources.

Exclusions for the first deliverable

• Certified training use.
• Real-world avionics fidelity claims.
• Multiplayer, global scenery streaming, and production deployment.

Resources

• Project organization: corp-v1-aerosim
• Skills organization: corp-v1-aerosim-skills-code-agent
• Application repository — test at 09628fbb828380fbe159be7530da26f4bbf02129
• Documentation repository — test at d8a45594c33efc3acbd1523955d4f235facc9a1f
• Published documentation — protected by the existing Keycloak access layer

Delivery progress checkpoint — 2026-09-07

Release 1.0.0 contains 114 Tasks. Progress is reported by lifecycle checkpoint rather than collapsing implementation and release into one percentage.

Measure	Progress	Meaning
Canonical ToBeReleased	49 / 114 (43.0%)	Canonical records place the Tasks in Waves 1–8 and 12–14 at the release-handoff state. This is not a release.
Repository-verified implementation pending reconciliation	6 / 114 (5.3%)	TASK-0048, TASK-0061, TASK-0065, TASK-0077, TASK-0083, and TASK-0111 are merged into the validated current application integration head, while their canonical records remain InProgress. This repository checkpoint does not replace canonical reconciliation.
Canonical InProgress	7 / 114 (6.1%)	Wave 15 Tasks are claimed as one Delivery ownership unit and remain under implementation.
Canonical ReadyForDelivery	58 / 114 (50.9%)	Unfinished Tasks in Waves 9–11 and 16–30 remain ready but unclaimed while Wave 15 is active.
Released	0 / 114 (0.0%)	No Release 1.0.0 artifact has been approved and released. ToBeReleased is not release authorization.

Wave 15 is active, and 6 of its 7 Tasks are repository-verified through merged application PRs #85, #89, #90, #95, #96, and #97. The current application integration head is 09628fbb828380fbe159be7530da26f4bbf02129; its integrated tasks 2718–2720 succeeded. TASK-0078 remains canonical InProgress, and its implementation PR #92 is closed without merge, so Wave 16 remains unclaimed. The canonical Wave 15 claim remains at documentation test SHA d8a45594c33efc3acbd1523955d4f235facc9a1f, verified by PR #155 exact-head build task 2581 and integrated build task 2582. The authoritative task-level lifecycle remains in the AeroSim documentation; this Board record is a dated portfolio checkpoint, not a second task database.

Discord

Exactly seven same-project channels exist in dedicated category corp-v1-aerosim (1542627633123299359), in lifecycle order:

• corp-v1-aerosim-general — 1537227679374508132
• corp-v1-aerosim-scope — 1537544173366943886
• corp-v1-aerosim-architecture — 1537227680590733383
• corp-v1-aerosim-ui-ux — 1541722108072169562
• corp-v1-aerosim-kanban — 1537548579856580739
• corp-v1-aerosim-delivery — 1537227683191197807
• corp-v1-aerosim-releases — 1537388451501056081

Hermes bot 1526860732917088266 successfully read and posted project guidance. The general introduction is pinned as message 1537227685657444484; Scope purpose guidance is message 1537544176621715506; Kanban purpose guidance is message 1537548582003933326; Releases purpose guidance is message 1537388452658815077. Effective read access was reverified across all seven project channels after the category migration; channel IDs and permission overwrites are unchanged.

Six staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other five AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation:

• General: 6fc9c6a1328e, 0 * * * *, skill corp-v1-channel-general-aerosim, target 1537227679374508132
• Scope: dd548489178e, 10 * * * *, skill corp-v1-channel-scope-aerosim, target 1537544173366943886
• Architecture: c236b1e9642e, 15 * * * *, skill corp-v1-channel-architecture-aerosim, target 1537227680590733383
• Kanban: 73378876d226, 20 * * * *, skill corp-v1-channel-kanban-aerosim, target 1537548579856580739
• Delivery: fdb061087f2f, 30 * * * *, skill corp-v1-channel-delivery-aerosim, target 1537227683191197807
• Releases: 9deaa76e0077, 45 * * * *, skill corp-v1-channel-releases-aerosim, target 1537388451501056081

All six jobs are enabled, explicitly constrained to the complete six-channel AeroSim boundary, and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.

Adopted project skills

All use default branch test and are primary for AeroSim work:

• development-branching-strategy-aerosim
• development-gitops-argo-cd-aerosim
• development-monorepo-pnpm-aerosim
• development-scripts-aerosim
• devsecops-ci-cd-gitea-aerosim
• documentation-docusaurus-aerosim
• template-engine-copier-aerosim
• corp-v1-channel-general-aerosim
• corp-v1-channel-scope-aerosim
• corp-v1-channel-architecture-aerosim
• corp-v1-channel-kanban-aerosim
• corp-v1-channel-delivery-aerosim
• corp-v1-channel-releases-aerosim

Each repository records the central source branch and commit in ADOPTION.md. Architecture and documentation work reference the global drawio-main skill.

Verification

• Application Actions run 2359: successful.
• Documentation Actions runs 2354 and 2361: successful, including Gondor Pages publication and the authoritative steering links.
• Documentation lifecycle alignment commit 5f674525f6c8b5ce29fe2653350c6188fb97ea01 and Actions run 609: successful.
• Application tests: four passed across web, API, and shared flight core.
• Application and documentation production builds: passed.
• Project-team access across four current project-organization repositories: verified for jarvis-at-skic, root-at-skic, martynas-pazusis, and piotras; pending verified Gitea identities for Panther Skeleton, Eduard, and Jenny.
• Jarvis Board/all-project onboarding was reverified on 2026-09-05: Discord view, send, and history access passes in all seven channels; Gitea team IDs 23 and 24 include jarvis-at-skic and all organization repositories.
• Andrius, Dovydas, and Giedrius K are recorded as AeroSim human team members from 2026-08-31. Effective General-channel view, send, and history access is verified; Gitea project-team and skills-team access remains pending verified account mappings.
• On 2026-09-28, RootAtSkic recorded Jone Tamulaite - Nong's departure from AeroSim and assigned MartynasP as the primary Scope owner. MartynasP was already an AeroSim member with verified membership in both AeroSim Gitea teams. Jone never had a verified Gitea mapping, so no Gitea team membership existed to revoke; Discord access removal requires fresh remote verification.
• Skills-team organization membership covers all fourteen current project-skill repositories for piotras: verified.
• Harbor organization variable names and secret name HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET: verified without reading secret values.
• Product lifecycle, solution traceability, and release-readiness registries now exist in project documentation. No Epic or Feature was assigned human approval retrospectively.
• Both application and documentation test branches currently have no branch-protection rule.

Outstanding governance decisions

A human team member must approve the desired branch-protection policy for both project test branches before protection is configured. No protection was added autonomously because required approvals and merge semantics are a governance decision.

Panther Skeleton, Eduard, Jenny, Andrius, Dovydas, and Giedrius K must provide or create their Gitea usernames before they can be added to aerosim-maintainers and aerosim-skill-maintainers. Piotras is mapped to Gitea account piotras and has verified membership in both teams, covering four current project repositories and fourteen project-skill repositories. Their recorded Discord project access is already verified.