docs: align AeroSim six-channel operations

2026-08-13 19:51:40 +00:00
parent d809093885
commit 261d8c0b49
5 changed files with 44 additions and 9 deletions
@@ -9,5 +9,6 @@ sidebar_position: 2
 | Date | Decision | Scope | Owner | Record |
 |---|---|---|---|---|
 | 2026-08-12 | Authorize AeroSim test kickoff and begin provisioning | AeroSim | RootAtSkic | [AeroSim kickoff](/governance/decisions/aerosim-kickoff/) |
 | 2026-08-13 | Align managed projects to the six-channel Scope/Kanban lifecycle and hourly synchronization model | Corp v1 managed projects | RootAtSkic | [Managed-project six-channel alignment](/governance/decisions/managed-project-six-channel-alignment/) |
 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,28 @@
 ---
 title: Managed-project six-channel alignment
 ---
 # Managed-project six-channel alignment — 2026-08-13
 ## Context
 Corp v1 lifecycle policy requires each managed project to operate six Discord workstreams—General, Scope, Architecture, Kanban, Delivery, and Releases—with one adopted project channel skill and one staggered hourly synchronization job per channel. Portfolio discovery found AeroSim as the only currently managed project and identified that its Kanban live channel and job were missing.
 ## Decision
 Align every currently managed Corp v1 project to the six-channel lifecycle. For AeroSim, create and verify `corp-v1-aerosim-kanban`, attach `corp-v1-channel-kanban--aerosim`, create its staggered hourly job, and update every existing AeroSim synchronization job to the exact six-channel same-project boundary.
 Human gates remain unchanged: only a human team member may approve an Epic or Feature for solution, approve a Feature for implementation, admit an exact task to Focus `InBacklog`, approve final version allocation, or request a release.
 ## Verified result
 - Managed-project inventory: AeroSim only.
 - Six exact AeroSim Discord channels exist under category `corp-v1`.
 - Kanban channel: `1537548579856580739`; purpose message: `1537548582003933326`.
 - Six enabled staggered hourly synchronization jobs exist; Kanban job: `73378876d226` at `20 * * * *`.
 - All six job prompts are constrained to the exact six AeroSim channel IDs and prohibit cross-project inspection.
 - All six adopted channel skills exist; the AeroSim skills team covers all thirteen mandatory skill repositories.
 ## Consequences
 Future project kickoffs and managed-project alignment reviews must verify the full six-channel, six-skill, six-job topology rather than treating a published reference skill as proof that live project infrastructure is synchronized.
@@ -13,4 +13,4 @@ sidebar_position: 2
 | Project | [AeroSim](/projects/aerosim/) |
 | Gitea | `jarvis-at-skic` — verified |
-The executing Hermes identity has verified membership in both AeroSim Gitea organization teams and verified read/post/pin access in all three AeroSim Discord channels as bot `1526860732917088266`.
+The executing Hermes identity has verified membership in both AeroSim Gitea organization teams and verified read/post access across all six AeroSim Discord channels as bot `1526860732917088266`; the required pinned General guidance remains verified.
@@ -54,23 +54,27 @@ A playable MVP covering a light trainer, commercial airliner, and fighter-style
 ## Discord
-Exactly four same-project channels exist under category `corp-v1` (`1537070242335821924`):
+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, posted, and pinned project guidance. The general introduction is pinned as message `1537227685657444484`. The releases purpose message is `1537388452658815077`. RootAtSkic was resolved as Discord member `1518725627845283888`.
+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`. RootAtSkic was resolved as Discord member `1518725627845283888`.
-Four staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other three AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation:
+Six staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other five AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation:
 - General: `6fc9c6a1328e`, `0 * * * *`, skill `corp-v1-channel-general--aerosim`, target `1537227679374508132`
 - Scope: `dd548489178e`, `10 * * * *`, skill `corp-v1-channel-scope--aerosim`, target `1537544173366943886`
 - Architecture: `c236b1e9642e`, `15 * * * *`, skill `corp-v1-channel-architecture--aerosim`, target `1537227680590733383`
 - Kanban: `73378876d226`, `20 * * * *`, skill `corp-v1-channel-kanban--aerosim`, target `1537548579856580739`
 - Delivery: `fdb061087f2f`, `30 * * * *`, skill `corp-v1-channel-delivery--aerosim`, target `1537227683191197807`
 - Releases: `9deaa76e0077`, `45 * * * *`, skill `corp-v1-channel-releases--aerosim`, target `1537388451501056081`
-All four jobs are enabled and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.
+All six jobs are enabled, explicitly constrained to the complete six-channel AeroSim boundary, and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.
 ## Adopted project skills
@@ -84,7 +88,9 @@ All use default branch `test` and are primary for AeroSim work:
 - `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`
@@ -98,7 +104,7 @@ Each repository records the central source branch and commit in `ADOPTION.md`. A
 - 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 organization contains all eleven adopted skill repositories on default branch `test`: verified.
+- 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.
@@ -21,14 +21,14 @@ Deliver the AeroSim browser flight-simulation platform, its documentation, and t
 - 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.
+- Adoption and maintenance of the thirteen mandatory 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.
+- `aerosim-skill-maintainers` in `corp-v1-aerosim-skills-code-agent` covers all thirteen adopted skill repositories.
 - `jarvis-at-skic` and `root-at-skic` membership and effective repository assignments are verified in both teams.
 ## Communication
-Exactly three AeroSim channels exist under the `corp-v1` category: `general`, `architecture`, and `delivery`. Hermes access, guidance messages, the pinned general introduction, and three isolated same-project review jobs are verified. No additional `corp-v1-aerosim-*` channel exists.
+Exactly six AeroSim channels exist under the `corp-v1` category: `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`. Hermes access, guidance messages, the pinned general introduction, and six isolated same-project hourly synchronization jobs are verified.