1.6 KiB
1.6 KiB
title, description, slug, sidebar_position
| title | description | slug | sidebar_position |
|---|---|---|---|
| Board Members | Identify the only members authorized to start or close Corp v1 projects and approve changes to the Corp v1 main governance skill. | / | 1 |
Board Members
The Corp v1 Board has exactly three members:
| Discord member | Account | Board authority |
|---|---|---|
<@1518725627845283888> |
RootAtSkic (root_at_skic) |
Start/close projects; approve corp-v1--main changes |
<@476287310627864587> |
Panther Skeleton (pantherskeleton) |
Start/close projects; approve corp-v1--main changes |
<@773109855497093191> |
MartynasP (w4rl0ck_21) |
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.
Only these Board members may approve changes to corp-v1--main. Other members and agents may identify gaps and prepare proposals, but they must not publish governance changes as approved.
Channel-skill change flow
- Propose a change to a central project-channel reference skill (
corp-v1-channel-*) to the Board. - Obtain explicit Board approval before publishing the central reference change.
- Ask each affected project channel to review and synchronize its project-adopted channel skill (
corp-v1-channel-*--<code>). - Preserve project-specific decisions during synchronization and return conflicts to the Board instead of overwriting them.
- Verify the central commit, every project adoption commit, runtime skill copy, and attached synchronization job before recording completion.