feat: establish Corp v1 Board portal

docs/board/index.md

@@ -0,0 +1,28 @@
+---
+title: "Board Members"
+description: "Identify the only members authorized to start or close Corp v1 projects and approve changes to the Corp v1 main governance skill."
+slug: /
+sidebar_position: 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
+
+1. Propose a change to a central project-channel reference skill (`corp-v1-channel-*`) to the Board.
+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.

docs/governance/project-lifecycle.md

@@ -1,22 +1,31 @@
 ---
-title: Project Lifecycle
+title: "Project Lifecycle"
+description: "Apply the Board-controlled lifecycle for starting, operating, synchronizing, and closing Corp v1 projects."
 slug: /project-lifecycle/
 sidebar_position: 1
 ---
 
 # Project Lifecycle
 
+## Board authority
+
+Only the three 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
 
-Capture the problem, intended outcome, sponsor, initial lead, constraints, dependencies, and rough effort.
+Capture the problem, intended outcome, sponsor, initial lead, constraints, dependencies, rough effort, and complete provisioning proposal. No project resources may be provisioned yet.
 
 ## 2. Approved
 
-Record the steering decision, committed scope, success measures, team, budget or capacity boundary, risks, and target dates.
+Obtain explicit Board approval. Record the approving Board member, decision evidence, committed scope, success measures, team, budget or capacity boundary, risks, and target dates before provisioning.
 
 ## 3. Active
 
-Maintain current status, decisions, risks, milestones, and material scope changes.
+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`.
+
+### 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.
 
 ## 4. Paused
 
@@ -24,8 +33,8 @@ State the reason, preservation requirements, restart conditions, accountable own
 
 ## 5. Shutting down
 
-Stop new commitments, inventory deliverables and dependencies, transfer or archive ownership, revoke project-specific access, and communicate impact.
+Obtain explicit Board approval for the closure scope. Stop new commitments, inventory deliverables and dependencies, transfer or archive ownership, revoke project-specific access, and communicate impact.
 
 ## 6. Closed
 
-Record the shutdown decision, final outcome against success measures, retained artifacts, unresolved obligations, lessons learned, and closure date.
+Record the approving Board member and closure decision, final outcome against success measures, retained artifacts, unresolved obligations, lessons learned, and closure date.

docs/overview/index.md

@@ -1,13 +1,14 @@
 ---
 id: index
 slug: /overview/
-title: Corp v1 Steering Committee
+title: "Corp v1 Board"
+description: "Understand the authoritative Corp v1 governance workspace and its Board-controlled decisions."
 sidebar_position: 1
 ---
 
-# Corp v1 Steering Committee
+# Corp v1 Board
 
-This repository is the authoritative governance workspace for starting, steering, and shutting down Corp v1 projects.
+This repository is the authoritative governance workspace for starting, governing, and closing Corp v1 projects.
 
 ## Registries
 
@@ -16,7 +17,8 @@ This repository is the authoritative governance workspace for starting, steering
 | [Projects](/projects/) | Portfolio status, ownership, lifecycle, and outcomes |
 | [Teams](/teams/) | Team mandates, responsibilities, and project assignments |
 | [Members](/members/) | Member identity, roles, and team membership |
+| [Board](/board/) | The only members authorized to approve project kickoff, project closure, and `corp-v1--main` changes |
 
 ## Operating principle
 
-Every project has a named sponsor, accountable lead, team, explicit status, kickoff decision, and—when closed—a shutdown record with retained artifacts and lessons learned.
+Every project has a named sponsor, accountable lead, team, explicit status, Board-approved kickoff decision, and—when closed—a Board-approved closure record with retained artifacts and lessons learned.