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

fix: update Corp v1 skill references
Build and publish Corp v1 Board portal / build (push) Successful in 39s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-04 12:55:03 +00:00
parent 666b6a8d25
commit fe228108af
22 changed files with 129 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/governance/project-lifecycle.md
+3 -3
View File
@@ -9,7 +9,7 @@ sidebar_position: 1
## Board authority
Only the four people listed in [Board Members](/board/) may approve a project kickoff, project closure, or a change to the global `corp-v1--main` governance skill. Approval must be explicit and attributable to a listed Discord ID. Agents and other members may prepare proposals and evidence but cannot approve these actions.
Only the four people listed in [Board Members](/board/) may approve a project kickoff, project closure, or a change to the global `corp-v1-main` governance skill. Approval must be explicit and attributable to a listed Discord ID. Agents and other members may prepare proposals and evidence but cannot approve these actions.
## 1. Proposed
@@ -21,7 +21,7 @@ Obtain explicit Board approval. Record the approving Board member, decision evid
## 3. Active
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`.
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
@@ -33,7 +33,7 @@ For an explicitly authorized Corp v1 system task, Hermes may use the Bitwarden-i
### 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.
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.
## 4. Paused