docs: register AeroSim test kickoff
Build and publish Corp v1 steering documentation / build (push) Successful in 32s

This commit is contained in:
2026-08-12 22:27:34 +00:00
parent d9df612315
commit 2d6b1cd795
9 changed files with 202 additions and 4 deletions
+1 -1
View File
@@ -8,6 +8,6 @@ sidebar_position: 2
| Date | Decision | Scope | Owner | Record |
|---|---|---|---|---|
| _No decisions recorded_ | — | — | — | — |
| 2026-08-12 | Authorize AeroSim test kickoff and begin provisioning | AeroSim | RootAtSkic | [AeroSim kickoff](/governance/decisions/aerosim-kickoff/) |
Every kickoff, pause, restart, material scope change, and shutdown requires a dated decision record with context, decision, rationale, accountable owner, and consequences.
@@ -0,0 +1,44 @@
---
title: AeroSim kickoff
---
# AeroSim kickoff — 2026-08-12
## Context
RootAtSkic authorized a real test run of the Corp v1 project-kickoff process for a browser-based flight simulator supporting several aircraft types and delegated the remaining project details to Hermes.
## Decision
Begin provisioning **AeroSim**, code `aerosim`, as a restricted Corp v1 project with RootAtSkic as sponsor and accountable lead.
The initial deliverable is a playable browser MVP for trainer, airliner, and fighter-style aircraft with shared controls, telemetry, and foundational scenarios.
## Authorized resources
- Three—and only three—same-project Discord channels under `corp-v1`.
- `corp-v1-aerosim` project organization.
- `corp-v1-aerosim-skills-code-agent` skills organization.
- Application and documentation repositories.
- Eight adopted project-scoped skills using suffix `--aerosim`.
- Corresponding organization teams.
- Three same-project cross-channel review jobs.
- Harbor non-secret variables and validation of secret-name presence only.
## Rationale
A real test project validates that the steering skill can create working, independently verified artifacts rather than only propose a lifecycle plan.
## Consequences and current state
Provisioning is intentionally recorded as partial rather than falsely marked complete:
- Both organizations, both teams, two project repositories, and eight adopted skill repositories exist.
- Application Actions run `2359` and documentation/Pages run `2354` succeeded.
- Discord channels and review jobs are pending because this execution context did not expose Discord administration tools.
- `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET` is absent. A channel member must enter it directly in the project organization's Gitea Actions settings; its value must never be sent to Hermes.
- RootAtSkic's exact Gitea username remains unresolved; human membership is pending rather than guessed.
## Owner
RootAtSkic
+2 -1
View File
@@ -8,6 +8,7 @@ sidebar_position: 1
| Member | Status | Roles | Teams | Active projects |
|---|---|---|---|---:|
| _No members registered_ | — | — | — | 0 |
| [RootAtSkic](/members/rootatskic/) | Active | AeroSim sponsor and lead | AeroSim Team | 1 |
| [Jarvis at SKIC](/members/jarvis-at-skic/) | Active | AeroSim technical member and code agent | AeroSim Team | 1 |
Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.
+16
View File
@@ -0,0 +1,16 @@
---
title: Jarvis at SKIC
sidebar_position: 2
---
# Jarvis at SKIC
| Field | Value |
|---|---|
| Status | Active |
| Governance roles | AeroSim technical member and executing code agent |
| Team | [AeroSim Team](/teams/aerosim/) |
| Project | [AeroSim](/projects/aerosim/) |
| Gitea | `jarvis-at-skic` — verified |
The executing Hermes identity has verified membership in both AeroSim Gitea organization teams. Discord channel access remains pending channel creation.
+17
View File
@@ -0,0 +1,17 @@
---
title: RootAtSkic
sidebar_position: 1
---
# RootAtSkic
| Field | Value |
|---|---|
| Status | Active |
| Governance roles | AeroSim sponsor and accountable lead |
| Team | [AeroSim Team](/teams/aerosim/) |
| Project | [AeroSim](/projects/aerosim/) |
| Discord | RootAtSkic; exact ID pending Discord administration access |
| Gitea | Exact username unresolved; membership pending |
No Discord or Gitea identifier was inferred or guessed.
+85
View File
@@ -0,0 +1,85 @@
---
title: AeroSim
sidebar_position: 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](/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 `14b5c0e8f25215d8bb4f41edcc0cdff4a87c342c`
- [Documentation repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation) — `test` at `87a001ee35653c33881066e880a0dff0f7d3d4ac`
- [Published documentation](https://pages.apps.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-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.
+1 -1
View File
@@ -8,7 +8,7 @@ sidebar_position: 1
| Project | Status | Sponsor | Lead | Team | Started | Closed |
|---|---|---|---|---|---|---|
| _No projects registered_ | — | — | — | — | — | — |
| [AeroSim](/projects/aerosim/) | Provisioning | RootAtSkic | RootAtSkic | [AeroSim Team](/teams/aerosim/) | 2026-08-12 | — |
## Required project record
+35
View File
@@ -0,0 +1,35 @@
---
title: AeroSim Team
sidebar_position: 1
---
# AeroSim Team
| Field | Value |
|---|---|
| Status | Provisioning |
| Lead | RootAtSkic |
| Verified technical member | `jarvis-at-skic` / Hermes code agent |
| Assigned project | [AeroSim](/projects/aerosim/) |
## Mandate
Deliver the AeroSim browser flight-simulation platform, its documentation, and the reusable project-specific engineering practices required to operate it.
## Responsibilities
- Product and delivery coordination.
- Flight-simulation architecture and shared flight model.
- Application, API, CI/CD, GitOps, and documentation delivery.
- Adoption and maintenance of the eight AeroSim project skills.
## Gitea access
- `aerosim-maintainers` in `corp-v1-aerosim` covers both project repositories.
- `aerosim-skill-maintainers` in `corp-v1-aerosim-skills-code-agent` covers all eight adopted skill repositories.
- `jarvis-at-skic` membership and effective repository assignments are verified.
- RootAtSkic's Gitea username remains unresolved and was not guessed.
## Communication
The three required same-project Discord channels are pending because Discord administration was unavailable in the kickoff execution context. No substitute or additional channels were created.
+1 -1
View File
@@ -8,6 +8,6 @@ sidebar_position: 1
| Team | Status | Lead | Members | Active projects |
|---|---|---|---:|---:|
| _No teams registered_ | — | — | 0 | 0 |
| [AeroSim Team](/teams/aerosim/) | Provisioning | RootAtSkic | 2 | 1 |
A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.