portal/docs/projects/aerosim.md

title, sidebar_position

title	sidebar_position
AeroSim	1

AeroSim

Field	Value
Code	aerosim
Status	Provisioning
Started	2026-08-12
Sponsor and accountable lead	RootAtSkic
Initial technical member	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 87a001ee35653c33881066e880a0dff0f7d3d4ac
• Published documentation — protected by the existing Keycloak access layer

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
• drawio-main--aerosim
• template-engine-copier--aerosim

Each repository records the central source branch and commit in ADOPTION.md.

Verification

• Application Actions run 2359: successful.
• Documentation Actions run 2354: successful, including Gondor Pages publication.
• 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.
• Skills-team access to all eight adopted skill repositories: verified.
• Harbor organization variables: verified.

Outstanding provisioning actions

1. Create exactly three Discord channels under corp-v1, add Hermes, pin project/skill guidance, and create the three isolated same-project review jobs. The current execution context did not expose Discord administration tools.
2. A channel member must add organization Actions secret HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET directly in Gitea. Its name is currently absent; no secret value was requested or accessed.
3. Resolve RootAtSkic's exact Gitea username before adding the human member to both organization teams. No username was guessed.
4. Replace the temporary documentation steering placeholder with this authoritative project-record URL in a follow-up documentation deployment.