131 lines
9.0 KiB
Markdown
131 lines
9.0 KiB
Markdown
---
|
|
title: AeroSim
|
|
sidebar_position: 1
|
|
---
|
|
|
|
# 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; Jone Tamulaite - Nong; `jarvis-at-skic` / Hermes code agent |
|
|
| Team | [AeroSim Team](/teams/aerosim/) |
|
|
|
|
## 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](https://gitea.lego-cloud.eu/corp-v1-aerosim)
|
|
- Skills organization: [corp-v1-aerosim-skills-code-agent](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent)
|
|
- [Application repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim) — `test` at `efbf3967548f1cbf5e06f97fa9d659535e35a7b4`
|
|
- [Documentation repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation) — `test` at `f686610a8b1b21825c66dc424f484fb2672933d7`
|
|
- [Published documentation](https://pages.apps.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation/) — protected by the existing Keycloak access layer
|
|
|
|
## Delivery progress checkpoint — 2026-09-03
|
|
|
|
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` | 8 / 114 (7.0%) | Wave 1 Tasks `TASK-0001`, `TASK-0008`, `TASK-0011`, and `TASK-0014` plus Wave 2 Tasks `TASK-0012`, `TASK-0015`, `TASK-0073`, and `TASK-0114` have reconciled canonical delivery evidence. The remaining 106 ReadyForDelivery Tasks have not reached this checkpoint. |
|
|
| Repository-verified implementation | 8 / 114 (7.0%) | The same eight Tasks are implemented at application `test` SHA `efbf3967548f1cbf5e06f97fa9d659535e35a7b4`; integrated publish task `1760` and validate task `1761` succeeded. This implementation measure is reported separately from canonical lifecycle and release state. |
|
|
| Released | 0 / 114 (0%) | No Release `1.0.0` artifact has been approved and released. `ToBeReleased` is not release authorization. |
|
|
|
|
Wave 2 is complete: its final application head is `efbf3967548f1cbf5e06f97fa9d659535e35a7b4`, and its canonical documentation was merged through PR #143 at documentation `test` SHA `f686610a8b1b21825c66dc424f484fb2672933d7`. Documentation exact-head build task `1762` and integrated build task `1763` succeeded, and the deployed release-readiness readback passed. Wave 3 is active: `TASK-0013`, `TASK-0016`, `TASK-0074`, and `TASK-0115` are claimed and in progress, but are not yet implemented or merged. The authoritative task-level lifecycle remains in the [AeroSim documentation](https://pages.apps.lego-cloud.eu/corp-v1-aerosim/corp-v1-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`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/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.
|
|
- Andrius, Dovydas, Giedrius K, and Jone Tamulaite - Nong 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.
|
|
- 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, Giedrius K, and Jone Tamulaite - Nong 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.
|