portal/docs/governance/decisions/corp-v1-board-migration.md

title, description, slug

title	description	slug
Establish the Corp v1 Board	Record the approved global migration from the steering committee resources to the Corp v1 Board, main skill, and portal.	/decisions/corp-v1-board-migration/

Establish the Corp v1 Board

• Date: 2026-08-14
• Status: Approved and implemented
• Approver: RootAtSkic (<@1518725627845283888>)
• Approval evidence: Discord message 1537750384875929620 in channel 1537070875503886356
• Scope: Global Corp v1 governance channel, main governance skill, portal repository and Pages deployment, Board membership, and channel-skill change flow

Decision

1. Replace the steering committee channel with the Corp v1 Board channel. Discord canonicalized the requested corp-v1--board text-channel name to corp-v1-board; the immutable channel ID remains 1537070875503886356.
2. Rename the global governance skill and repository to corp-v1-main.
3. Rename corp-v1/sterring-commitee to corp-v1/portal and deploy it at https://pages.apps.lego-cloud.eu/corp-v1/portal/.
4. Establish exactly these Board members:
   • RootAtSkic (<@1518725627845283888>)
   • Panther Skeleton (<@476287310627864587>)
   • MartynasP (<@773109855497093191>)
5. Only these Board members may approve a project kickoff, project closure, or a change to corp-v1-main.
6. Central corp-v1-channel-* reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted corp-v1-channel-*-<code> skill; synchronization must preserve project-specific decisions.

Consequences

• Governance decisions must cite the approving Board member's immutable Discord ID and evidence.
• The portal exposes a dedicated Board page and the Board-controlled lifecycle.
• The renamed repository preserves Git history.
• The Pages workflow publishes using the renamed corp-v1/portal repository path.