docs: align AeroSim six-channel operations

docs/governance/decisions/managed-project-six-channel-alignment.md

@@ -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.