corp-v1/portal
2
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs: complete AeroSim kickoff registry
Build and publish Corp v1 steering documentation / build (push) Successful in 33s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-12 22:35:46 +00:00
parent 2d6b1cd795
commit cd25976a3f
7 changed files with 36 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/governance/decisions/aerosim-kickoff.md
+6 -4
View File
@@ -31,13 +31,15 @@ A real test project validates that the steering skill can create working, indepe
## Consequences and current state
Provisioning is intentionally recorded as partial rather than falsely marked complete:
The authorized kickoff resources are provisioned and verified:
- 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.
- Application Actions run `2359` and documentation/Pages runs `2354` and `2361` succeeded.
- Exactly three AeroSim Discord channels exist under `corp-v1`; Hermes access, guidance, pinned introduction, and three staggered same-project review jobs are verified.
- `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.
- RootAtSkic was resolved as `root-at-skic` through Gitea user search and added to both organization teams.
The project is Active, with Harbor-dependent image publication explicitly gated until the required organization secret name is present.
## Owner