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

docs: record dedicated project Discord categories
Build and publish Corp v1 Board portal / build (pull_request) Successful in 35s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-27 20:18:06 +00:00
parent 0a993fae46
commit 2dc80c16e2
9 changed files with 62 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/governance/project-lifecycle.md
+4
View File
@@ -23,6 +23,10 @@ Obtain explicit Board approval. Record the approving Board member, decision evid
Maintain current status, decisions, risks, milestones, and material scope changes. Project teams retain authority within their approved project boundaries; Board approval is still required for kickoff/closure and changes to `corp-v1--main`.
### Discord topology
The guild-level `corp-v1` category is reserved for Board and shared governance channels. Every project uses one dedicated top-level category named `corp-v1-<code>` containing exactly seven lifecycle channels in this order: General, Scope, Architecture, UI/UX, Kanban, Delivery, Releases. Existing channels are moved by immutable ID so history, pins, permission overwrites, webhooks, and delivery targets remain intact.
### Project-channel skill changes
A proposed change to a central project-channel reference skill (`corp-v1-channel-*`) must be presented to the Board before publication. After explicit Board approval and central publication, ask every affected project channel to review and synchronize its project-adopted channel skill (`corp-v1-channel-*--<code>`). Synchronization must preserve project-specific decisions, report conflicts for Board review, update runtime copies, and verify attached channel jobs.