[verified] governance: onboard Jenny across Corp v1
Build and publish Corp v1 Board portal / build (pull_request) Successful in 35s
Build and publish Corp v1 Board portal / build (pull_request) Successful in 35s
This commit is contained in:
+3
-2
@@ -7,7 +7,7 @@ sidebar_position: 1
|
||||
|
||||
# Board Members
|
||||
|
||||
The Corp v1 Board has exactly five members:
|
||||
The Corp v1 Board has exactly six members:
|
||||
|
||||
| Discord member | Account | Board authority |
|
||||
|---|---|---|
|
||||
@@ -16,6 +16,7 @@ The Corp v1 Board has exactly five members:
|
||||
| `<@773109855497093191>` | MartynasP (`w4rl0ck_21`) | Start/close projects; approve `corp-v1--main` changes |
|
||||
| `<@364383883778850827>` | Eduard (`eduardanichess`) | Start/close projects; approve `corp-v1--main` changes |
|
||||
| `<@1483820991720329227>` | Linas (`linas_02251`) | Start/close projects; approve `corp-v1--main` changes |
|
||||
| `<@1540035254746882048>` | Jenny (`elprup16`) | Start/close projects; approve `corp-v1--main` changes |
|
||||
|
||||
Only these Board members may approve a project kickoff or project closure. Approval must be explicit and attributable to one of the Discord IDs above.
|
||||
|
||||
@@ -27,4 +28,4 @@ Only these Board members may approve changes to `corp-v1--main`. Other members a
|
||||
2. Obtain explicit Board approval before publishing the central reference change.
|
||||
3. Ask each affected project channel to review and synchronize its project-adopted channel skill (`corp-v1-channel-*--<code>`).
|
||||
4. Preserve project-specific decisions during synchronization and return conflicts to the Board instead of overwriting them.
|
||||
5. Verify the central commit, every project adoption commit, runtime skill copy, and attached synchronization job before recording completion.
|
||||
5. Verify the central commit, every project adoption commit, runtime skill copy, and absence of Corp v1 scheduler jobs before recording completion.
|
||||
|
||||
Reference in New Issue
Block a user