docs: register AeroSim test kickoff
Build and publish Corp v1 steering documentation / build (push) Successful in 32s
Build and publish Corp v1 steering documentation / build (push) Successful in 32s
This commit is contained in:
@@ -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
|
||||
Reference in New Issue
Block a user