feat: establish Corp v1 steering documentation

docs/governance/decisions.md

@@ -0,0 +1,13 @@
+---
+title: Decision Log
+slug: /governance/decisions/
+sidebar_position: 2
+---
+
+# Decision Log
+
+| Date | Decision | Scope | Owner | Record |
+|---|---|---|---|---|
+| _No decisions recorded_ | — | — | — | — |
+
+Every kickoff, pause, restart, material scope change, and shutdown requires a dated decision record with context, decision, rationale, accountable owner, and consequences.

docs/governance/project-lifecycle.md

@@ -0,0 +1,31 @@
+---
+title: Project Lifecycle
+slug: /governance/project-lifecycle/
+sidebar_position: 1
+---
+
+# Project Lifecycle
+
+## 1. Proposed
+
+Capture the problem, intended outcome, sponsor, initial lead, constraints, dependencies, and rough effort.
+
+## 2. Approved
+
+Record the steering decision, committed scope, success measures, team, budget or capacity boundary, risks, and target dates.
+
+## 3. Active
+
+Maintain current status, decisions, risks, milestones, and material scope changes.
+
+## 4. Paused
+
+State the reason, preservation requirements, restart conditions, accountable owner, and review date.
+
+## 5. Shutting down
+
+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.

docs/index.md

@@ -0,0 +1,22 @@
+---
+id: index
+slug: /
+title: Corp v1 Steering Committee
+sidebar_position: 1
+---
+
+# Corp v1 Steering Committee
+
+This repository is the authoritative governance workspace for starting, steering, and shutting down Corp v1 projects.
+
+## Registries
+
+| Registry | Purpose |
+|---|---|
+| [Projects](./projects/index.md) | Portfolio status, ownership, lifecycle, and outcomes |
+| [Teams](./teams/index.md) | Team mandates, responsibilities, and project assignments |
+| [Members](./members/index.md) | Member identity, roles, and team membership |
+
+## 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.

docs/members/index.md

@@ -0,0 +1,13 @@
+---
+title: Members Registry
+slug: /members/
+sidebar_position: 1
+---
+
+# Members Registry
+
+| Member | Status | Roles | Teams | Active projects |
+|---|---|---|---|---:|
+| _No members registered_ | — | — | — | 0 |
+
+Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.

docs/projects/index.md

@@ -0,0 +1,15 @@
+---
+title: Projects Registry
+slug: /projects/
+sidebar_position: 1
+---
+
+# Projects Registry
+
+| Project | Status | Sponsor | Lead | Team | Started | Closed |
+|---|---|---|---|---|---|---|
+| _No projects registered_ | — | — | — | — | — | — |
+
+## Required project record
+
+Each project record must define purpose, measurable outcomes, scope, sponsor, accountable lead, assigned team, lifecycle status, dependencies, risks, kickoff decision, and shutdown decision where applicable.

docs/teams/index.md

@@ -0,0 +1,13 @@
+---
+title: Teams Registry
+slug: /teams/
+sidebar_position: 1
+---
+
+# Teams Registry
+
+| Team | Status | Lead | Members | Active projects |
+|---|---|---|---:|---:|
+| _No teams registered_ | — | — | 0 | 0 |
+
+A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.