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

[verified] governance: onboard Jenny across Corp v1
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-20 17:39:13 +00:00
parent fe473d9f83
commit 6170e09db6
12 changed files with 80 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/governance/project-lifecycle.md
+2 -2
View File
@@ -9,7 +9,7 @@ sidebar_position: 1
## Board authority
Only the five 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 six 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
@@ -25,7 +25,7 @@ Maintain current status, decisions, risks, milestones, and material scope change
### 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 that no Corp v1 scheduler job exists.
## 4. Paused