portal/docs/projects/aerosim.md

title, sidebar_position

title	sidebar_position
AeroSim	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; jarvis-at-skic / Hermes 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 14b5c0e8f25215d8bb4f41edcc0cdff4a87c342c
• Documentation repository — test at 5f674525f6c8b5ce29fe2653350c6188fb97ea01
• Published documentation — protected by the existing Keycloak access layer

Discord

Exactly six same-project channels exist under category corp-v1 (1537070242335821924):

• corp-v1-aerosim-general — 1537227679374508132
• corp-v1-aerosim-scope — 1537544173366943886
• corp-v1-aerosim-architecture — 1537227680590733383
• 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 access is verified for RootAtSkic (1518725627845283888), Panther Skeleton (476287310627864587), MartynasP (773109855497093191), Eduard (364383883778850827), Linas (1483820991720329227), and Jenny (1540035254746882048) across all six project channels. Jenny has effective VIEW_CHANNEL, SEND_MESSAGES, and READ_MESSAGE_HISTORY. The Jenny team update was announced in General as message 1540048209152573550.

The current Corp v1 operating model prohibits project cronjobs and scheduler jobs. A fresh scheduler inventory on 2026-08-20 found no job targeting an AeroSim channel.

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 to both project repositories: verified for jarvis-at-skic, root-at-skic, martynas-pazusis, and linas; pending verified Gitea identities for Panther Skeleton and Eduard. Linas's assignment is complete through team ID 23, but login activation remains pending because Gitea user ID 21 reports active=false.
• Skills-team organization contains all thirteen adopted skill repositories on default branch test: 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, and Jenny must provide or create their Gitea usernames before they can be added to aerosim-maintainers and aerosim-skill-maintainers. Jenny must first sign in to Gitea at least once. Their Discord project access is already verified.

Linas is assigned to aerosim-maintainers (team ID 23, covering both required project repositories) and aerosim-skill-maintainers (team ID 24, covering all thirteen adopted skill repositories). The account owner or Gitea administrator must activate user ID 21; until active=false is cleared, team assignment is complete but interactive login remains pending.