[verified] governance: onboard Jenny across Corp v1

docs/governance/decisions.md

@@ -8,6 +8,7 @@ sidebar_position: 2
 
 | Date | Decision | Scope | Owner | Record |
 |---|---|---|---|---|
+| 2026-08-20 | Add Jenny to the Corp v1 Board and every active project | Corp v1 governance, AeroSim, and Maze Next Gen | RootAtSkic | [Jenny Board and project membership](/governance/decisions/jenny-board-and-project-membership/) |
 | 2026-08-17 | Authorize Maze Next Gen kickoff and begin provisioning | Maze Next Gen | RootAtSkic | [Maze Next Gen kickoff](/governance/decisions/mazeng-kickoff/) |
 | 2026-08-17 | Add Linas to the Corp v1 Board and AeroSim team | Corp v1 governance and AeroSim | RootAtSkic | [Linas Board and AeroSim membership](/governance/decisions/linas-board-and-aerosim-membership/) |
 | 2026-08-14 | Add Eduard to the Corp v1 Board and expand the AeroSim team | Corp v1 governance and AeroSim | RootAtSkic | [Board and AeroSim membership expansion](/governance/decisions/board-and-aerosim-membership-expansion/) |

docs/governance/decisions/jenny-board-and-project-membership.md

@@ -0,0 +1,36 @@
+---
+title: "Jenny Board and project membership"
+description: "Record the approved addition of Jenny to the Corp v1 Board and every active project."
+sidebar_position: 1
+---
+
+# Jenny Board and project membership
+
+- **Date:** 2026-08-20
+- **Status:** Discord access applied and verified; Gitea access pending first login
+- **Approved by:** RootAtSkic (`<@1518725627845283888>`)
+- **Approval evidence:** `corp-v1-board` channel `1537070875503886356`, message `1540045796152709180`
+- **Scope:** Corp v1 Board authority plus AeroSim and Maze Next Gen project membership for Jenny (`<@1540035254746882048>`)
+
+## Decision
+
+1. Add Jenny (`<@1540035254746882048>`, `elprup16`, display name Jenny) to the Corp v1 Board.
+2. Add Jenny to every active Corp v1 human project team: AeroSim and Maze Next Gen.
+3. Preserve RootAtSkic as sponsor and accountable lead for both projects.
+4. Defer Gitea organization-team access until Jenny signs in to Gitea at least once and her username is verified; do not guess an identity or add direct collaborators.
+5. Preserve every earlier governance decision as historical evidence.
+
+## Applied and verified state
+
+- Effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` permissions were verified in `corp-v1-board` and all twelve active-project channels.
+- Member-specific overwrites restore `VIEW_CHANNEL`; inherited guild permissions supply `SEND_MESSAGES` and `READ_MESSAGE_HISTORY`.
+- A fresh scheduler inventory found no Corp v1 project or channel jobs.
+- Gitea membership was intentionally not changed.
+
+## Consequences
+
+- Jenny may exercise Board authority attributable to immutable Discord ID `1540035254746882048`.
+- Jenny is a human team member of AeroSim and Maze Next Gen and may exercise each project's human approval gates.
+- The Corp v1 Board now has six members.
+- AeroSim now has six human members plus the Hermes code agent; Maze Next Gen now has two human members plus the Hermes code agent.
+- Repository access remains a visible follow-up: Jenny must first log in at `https://gitea.lego-cloud.eu/`.

docs/governance/project-lifecycle.md

@@ -9,7 +9,7 @@ sidebar_position: 1
 
 ## Board authority
 
-Only the five 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.
+Only the six 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
 
@@ -25,7 +25,7 @@ Maintain current status, decisions, risks, milestones, and material scope change
 
 ### 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.
+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 that no Corp v1 scheduler job exists.
 
 ## 4. Paused