[verified] governance: onboard Jenny across Corp v1

docs/board/index.md

@@ -7,7 +7,7 @@ sidebar_position: 1
 
 # Board Members
 
-The Corp v1 Board has exactly four members:
+The Corp v1 Board has exactly six members:
 
 | Discord member | Account | Board authority |
 |---|---|---|
@@ -15,6 +15,8 @@ The Corp v1 Board has exactly four members:
 | `<@476287310627864587>` | Panther Skeleton (`pantherskeleton`) | Start/close projects; approve `corp-v1--main` changes |
 | `<@773109855497093191>` | MartynasP (`w4rl0ck_21`) | Start/close projects; approve `corp-v1--main` changes |
 | `<@364383883778850827>` | Eduard (`eduardanichess`) | Start/close projects; approve `corp-v1--main` changes |
+| `<@1483820991720329227>` | Linas (`linas_02251`) | Start/close projects; approve `corp-v1--main` changes |
+| `<@1540035254746882048>` | Jenny (`elprup16`) | 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.
 
@@ -26,4 +28,4 @@ Only these Board members may approve changes to `corp-v1--main`. Other members a
 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.
+5. Verify the central commit, every project adoption commit, runtime skill copy, and absence of Corp v1 scheduler jobs before recording completion.

docs/governance/decisions.md

@@ -8,7 +8,9 @@ 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/) |
 | 2026-08-14 | Establish the Corp v1 Board, main skill, portal, membership, and skill-change authority | Corp v1 governance | RootAtSkic | [Corp v1 Board migration](/governance/decisions/corp-v1-board-migration/) |
 | 2026-08-13 | Align managed projects to the six-channel Scope/Kanban lifecycle and hourly synchronization model | Corp v1 managed projects | RootAtSkic | [Managed-project six-channel alignment](/governance/decisions/managed-project-six-channel-alignment/) |

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/decisions/linas-board-and-aerosim-membership.md

@@ -0,0 +1,34 @@
+---
+title: "Linas Board and AeroSim membership"
+description: "Record the approved addition of Linas to the Corp v1 Board and AeroSim team."
+sidebar_position: 1
+---
+
+# Linas Board and AeroSim membership
+
+- **Date:** 2026-08-17
+- **Status:** Approved and applied; Gitea login activation pending
+- **Approved by:** RootAtSkic (`<@1518725627845283888>`)
+- **Approval evidence:** `corp-v1-board` channel `1537070875503886356`, message `1538808717301252116`
+- **Scope:** Corp v1 Board authority and AeroSim team membership for Linas (`<@1483820991720329227>`)
+
+## Decision
+
+1. Add Linas (`<@1483820991720329227>`, `linas_02251`, display name Linas) to the Corp v1 Board.
+2. Add Linas to the AeroSim human project team while preserving RootAtSkic as sponsor and accountable lead.
+3. Apply repository access through the existing organization teams rather than direct collaborators.
+4. Preserve every earlier governance decision as historical evidence; this dated record changes the current roster without rewriting the 2026-08-12 or 2026-08-14 decisions.
+
+## Applied and verified state
+
+- Effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` permissions were verified in `corp-v1-board` and all six AeroSim channels. Existing permissions already provided access, so no Discord permission mutation was made.
+- The Gitea mapping is unambiguous: `linas`, user ID `21`, full name Linas Ramanauskas.
+- `linas` is verified in `aerosim-maintainers` (team ID `23`), which covers both required repositories in `corp-v1-aerosim`.
+- `linas` is verified in `aerosim-skill-maintainers` (team ID `24`), which covers all thirteen adopted skill repositories in `corp-v1-aerosim-skills-code-agent`.
+- The membership update was announced in `corp-v1-aerosim-general` as message `1538811290925928505`.
+
+## Caveat and consequences
+
+- Linas may exercise the Board and AeroSim human approval gates attributable to immutable Discord ID `1483820991720329227`.
+- Gitea team access assignment is complete, but login activation remains pending: user ID `21` reports `active=false`.
+- The Corp v1 Board now has five members; the AeroSim registry has five human members plus the Hermes code agent.

docs/governance/project-lifecycle.md

@@ -9,7 +9,7 @@ sidebar_position: 1
 
 ## Board authority
 
-Only the four 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
 

docs/members/index.md

@@ -13,5 +13,7 @@ sidebar_position: 1
 | [Panther Skeleton](/members/panther-skeleton/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
 | [MartynasP](/members/martynasp/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
 | [Eduard](/members/eduard/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
+| [Linas](/members/linas/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
+| [Jenny](/members/jenny/) | Active | Board member; AeroSim and Maze Next Gen member | AeroSim Team; Maze Next Gen Team | 2 |
 
 Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.

docs/members/jenny.md

@@ -0,0 +1,19 @@
+---
+title: "Jenny"
+description: "Identify Jenny's Corp v1 Board and active-project responsibilities and access state."
+sidebar_position: 7
+---
+
+# Jenny
+
+| Field | Value |
+|---|---|
+| Discord | `<@1540035254746882048>` — `elprup16` / Jenny |
+| Governance roles | Corp v1 Board member; AeroSim and Maze Next Gen human team member |
+| Teams | [AeroSim Team](/teams/aerosim/); [Maze Next Gen Team](/teams/mazeng/) |
+| Active projects | [AeroSim](/projects/aerosim/); [Maze Next Gen](/projects/mazeng/) |
+| Gitea | Pending first login and verified username |
+
+On 2026-08-20, effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access was 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`.
+
+Jenny must sign in to [Gitea](https://gitea.lego-cloud.eu/) at least once before organization-team access can be granted. No Gitea username was guessed and no repository or team membership was provisioned.

docs/members/linas.md

@@ -0,0 +1,20 @@
+---
+title: "Linas"
+description: "Identify Linas's Corp v1 Board and AeroSim project responsibilities and verified access state."
+sidebar_position: 6
+---
+
+# Linas
+
+| Field | Value |
+|---|---|
+| Full name | Linas Ramanauskas |
+| Discord | `<@1483820991720329227>` — `linas_02251` / Linas |
+| Governance roles | Corp v1 Board member; AeroSim human team member |
+| Team | [AeroSim Team](/teams/aerosim/) |
+| Active projects | [AeroSim](/projects/aerosim/) |
+| Gitea | `linas` (user ID `21`) — verified in both AeroSim organization teams; account reports `active=false` |
+
+On 2026-08-17, effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access was verified in `corp-v1-board` and all six AeroSim channels. Existing effective permissions were sufficient, so no Discord permission mutation was made.
+
+The unambiguous Gitea identity `linas` belongs to `aerosim-maintainers` (team ID `23`) and `aerosim-skill-maintainers` (team ID `24`). Those teams cover both required project repositories and all thirteen adopted skill repositories. Access assignment is complete, but Gitea login activation remains pending because the account reports `active=false`.

docs/projects/aerosim.md

@@ -11,7 +11,7 @@ sidebar_position: 1
 | Status | Active — lifecycle alignment reviewed |
 | Started | 2026-08-12 |
 | Sponsor and accountable lead | RootAtSkic |
-| Team members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; `jarvis-at-skic` / Hermes code agent |
+| Team members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; `jarvis-at-skic` / Hermes code agent |
 | Team | [AeroSim Team](/teams/aerosim/) |
 
 ## Purpose
@@ -63,18 +63,9 @@ Exactly six same-project channels exist under category `corp-v1` (`1537070242335
 - `corp-v1-aerosim-delivery` — `1537227683191197807`
 - `corp-v1-aerosim-releases` — `1537388451501056081`
 
-Hermes bot `1526860732917088266` successfully read and posted project guidance. The general introduction is pinned as message `1537227685657444484`; Scope purpose guidance is message `1537544176621715506`; Kanban purpose guidance is message `1537548582003933326`; Releases purpose guidance is message `1537388452658815077`. Effective access is verified for RootAtSkic (`1518725627845283888`), Panther Skeleton (`476287310627864587`), MartynasP (`773109855497093191`), and Eduard (`364383883778850827`) across all six project channels.
+Hermes bot `1526860732917088266` successfully read and posted project guidance. The general introduction is pinned as message `1537227685657444484`; Scope purpose guidance is message `1537544176621715506`; Kanban purpose guidance is message `1537548582003933326`; Releases purpose guidance is message `1537388452658815077`. Effective access is verified for RootAtSkic (`1518725627845283888`), Panther Skeleton (`476287310627864587`), MartynasP (`773109855497093191`), Eduard (`364383883778850827`), Linas (`1483820991720329227`), and Jenny (`1540035254746882048`) across all six project channels. Jenny has effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY`. The Jenny team update was announced in General as message `1540048209152573550`.
 
-Six staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other five AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation:
+The current Corp v1 operating model prohibits project cronjobs and scheduler jobs. A fresh scheduler inventory on 2026-08-20 found no job targeting an AeroSim channel.
-
-- General: `6fc9c6a1328e`, `0 * * * *`, skill `corp-v1-channel-general--aerosim`, target `1537227679374508132`
-- Scope: `dd548489178e`, `10 * * * *`, skill `corp-v1-channel-scope--aerosim`, target `1537544173366943886`
-- Architecture: `c236b1e9642e`, `15 * * * *`, skill `corp-v1-channel-architecture--aerosim`, target `1537227680590733383`
-- Kanban: `73378876d226`, `20 * * * *`, skill `corp-v1-channel-kanban--aerosim`, target `1537548579856580739`
-- Delivery: `fdb061087f2f`, `30 * * * *`, skill `corp-v1-channel-delivery--aerosim`, target `1537227683191197807`
-- Releases: `9deaa76e0077`, `45 * * * *`, skill `corp-v1-channel-releases--aerosim`, target `1537388451501056081`
-
-All six jobs are enabled, explicitly constrained to the complete six-channel AeroSim boundary, and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.
 
 ## Adopted project skills
 
@@ -103,7 +94,7 @@ Each repository records the central source branch and commit in `ADOPTION.md`. A
 - Documentation lifecycle alignment commit `5f674525f6c8b5ce29fe2653350c6188fb97ea01` and Actions run `609`: successful.
 - Application tests: four passed across web, API, and shared flight core.
 - Application and documentation production builds: passed.
-- Project-team access to both project repositories: verified for `jarvis-at-skic`, `root-at-skic`, and `martynas-pazusis`; pending verified Gitea identities for Panther Skeleton and Eduard.
+- Project-team access to both project repositories: verified for `jarvis-at-skic`, `root-at-skic`, `martynas-pazusis`, and `linas`; pending verified Gitea identities for Panther Skeleton and Eduard. Linas's assignment is complete through team ID `23`, but login activation remains pending because Gitea user ID `21` reports `active=false`.
 - Skills-team organization contains all thirteen adopted skill repositories on default branch `test`: verified.
 - Harbor organization variable names and secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`: verified without reading secret values.
 - Product lifecycle, solution traceability, and release-readiness registries now exist in project documentation. No Epic or Feature was assigned human approval retrospectively.
@@ -113,4 +104,6 @@ Each repository records the central source branch and commit in `ADOPTION.md`. A
 
 A human team member must approve the desired branch-protection policy for both project `test` branches before protection is configured. No protection was added autonomously because required approvals and merge semantics are a governance decision.
 
-Panther Skeleton and Eduard must provide or create their Gitea usernames before they can be added to `aerosim-maintainers` and `aerosim-skill-maintainers`. Their Discord project access is already verified.
+Panther Skeleton, Eduard, and Jenny must provide or create their Gitea usernames before they can be added to `aerosim-maintainers` and `aerosim-skill-maintainers`. Jenny must first sign in to Gitea at least once. Their Discord project access is already verified.
+
+Linas is assigned to `aerosim-maintainers` (team ID `23`, covering both required project repositories) and `aerosim-skill-maintainers` (team ID `24`, covering all thirteen adopted skill repositories). The account owner or Gitea administrator must activate user ID `21`; until `active=false` is cleared, team assignment is complete but interactive login remains pending.

docs/projects/mazeng.md

@@ -11,7 +11,7 @@ sidebar_position: 2
 | Status | Active — Harbor gated |
 | Started | 2026-08-17 |
 | Sponsor and accountable lead | RootAtSkic |
-| Initial technical member | `jarvis-at-skic` / Hermes code agent |
+| Team members | RootAtSkic; Jenny; `jarvis-at-skic` / Hermes code agent |
 | Team | [Maze Next Gen Team](/teams/mazeng/) |
 
 ## Purpose
@@ -45,18 +45,11 @@ Exactly six channels exist under category `corp-v1` (`1537070242335821924`):
 - `corp-v1-mazeng-delivery` — `1539019973043683358`; purpose `1539019975203885068`; pinned skills `1539021530317463572`
 - `corp-v1-mazeng-releases` — `1539019976977948694`; purpose `1539019979590991963`; pinned skills `1539021536621756458`
 
-General introduction `1539019982682325132` and all six skill-guidance messages are pinned. Hermes read/post/pin operations succeeded in all channels. Harbor request message: `1539020766203617390`.
+General introduction `1539019982682325132` and all six skill-guidance messages are pinned. Hermes read/post/pin operations succeeded in all channels. Jenny (`1540035254746882048`) has verified effective view/send/history access across all six channels. The Jenny team update was announced in General as message `1540048213090771034`. Harbor request message: `1539020766203617390`.
 
-## Synchronization jobs
+## Project automation
 
-All six are enabled, hourly, staggered, exact-targeted, limited to the six Maze channels, and attach the mapped adopted skill:
+The current Corp v1 operating model prohibits project cronjobs and scheduler jobs. A fresh scheduler inventory on 2026-08-20 found no job targeting a Maze Next Gen channel.
-
-- General: `f5465bc1b05d`, `0 * * * *`, skill `corp-v1-channel-general--mazeng`, target `1539019955738116096`
-- Scope: `ab278de9e046`, `10 * * * *`, skill `corp-v1-channel-scope--mazeng`, target `1539019959135633580`
-- Architecture: `9c9e0206f05b`, `15 * * * *`, skill `corp-v1-channel-architecture--mazeng`, target `1539019963568758835`
-- Kanban: `e8de02062193`, `20 * * * *`, skill `corp-v1-channel-kanban--mazeng`, target `1539019969323466883`
-- Delivery: `11f63507301a`, `30 * * * *`, skill `corp-v1-channel-delivery--mazeng`, target `1539019973043683358`
-- Releases: `f04ab31a499e`, `45 * * * *`, skill `corp-v1-channel-releases--mazeng`, target `1539019976977948694`
 
 ## Adopted project skills
 
@@ -78,7 +71,7 @@ Global diagram source: [`drawio-main`](https://gitea.lego-cloud.eu/home-v1-skill
 
 ## Access and Harbor
 
-Team identifier `maze-next-gen-team` exists in both private organizations, includes all repositories, grants per-unit write access, and contains verified members `root-at-skic` and `jarvis-at-skic`. Thirty effective repository permission checks passed across fifteen repositories.
+Team identifier `maze-next-gen-team` exists in both private organizations, includes all repositories, grants per-unit write access, and contains verified members `root-at-skic` and `jarvis-at-skic`. Thirty effective repository permission checks passed across fifteen repositories. Jenny's Gitea access remains pending until she signs in at least once and supplies a verified username.
 
 Verified variables on `corp-v1-mazeng`:
 

docs/teams/aerosim.md

@@ -9,7 +9,7 @@ sidebar_position: 1
 |---|---|
 | Status | Active |
 | Lead | RootAtSkic |
-| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; `jarvis-at-skic` / Hermes code agent |
+| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; `jarvis-at-skic` / Hermes code agent |
 | Assigned project | [AeroSim](/projects/aerosim/) |
 
 ## Mandate
@@ -27,9 +27,11 @@ Deliver the AeroSim browser flight-simulation platform, its documentation, and t
 
 - `aerosim-maintainers` in `corp-v1-aerosim` covers both project repositories.
 - `aerosim-skill-maintainers` in `corp-v1-aerosim-skills-code-agent` covers all thirteen adopted skill repositories.
-- `jarvis-at-skic`, `root-at-skic`, and `martynas-pazusis` membership and effective repository assignments are verified in both teams.
+- `jarvis-at-skic`, `root-at-skic`, `martynas-pazusis`, and `linas` membership and repository assignments are verified in both teams.
+- Linas maps unambiguously to Gitea user ID `21` (`linas`, Linas Ramanauskas). Access assignment is complete, but login activation remains pending because the account reports `active=false`.
 - Panther Skeleton and Eduard have verified Discord identities and channel access, but no matching Gitea accounts could be resolved on 2026-08-14. Their Gitea team access remains pending verified usernames or account creation.
+- Jenny has verified Discord access. Gitea access is pending until she signs in to Gitea at least once and supplies a verified username; no username was guessed and no direct collaborator was added.
 
 ## Communication
 
-Exactly six AeroSim channels exist under the `corp-v1` category: `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`. RootAtSkic, Panther Skeleton, MartynasP, Eduard, and Hermes have verified effective access. Guidance messages, the pinned general introduction, and six isolated same-project hourly synchronization jobs are verified.
+Exactly six AeroSim channels exist under the `corp-v1` category: `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`. RootAtSkic, Panther Skeleton, MartynasP, Eduard, Linas, Jenny, and Hermes have verified effective access. Jenny's effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` permissions were verified in all six channels. The membership update was announced in General as message `1540048209152573550`. Corp v1 project scheduler jobs are prohibited by the current operating model.

docs/teams/index.md

@@ -8,7 +8,7 @@ sidebar_position: 1
 
 | Team | Status | Lead | Members | Active projects |
 |---|---|---|---:|---:|
-| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 5 | 1 |
+| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 7 | 1 |
-| [Maze Next Gen Team](/teams/mazeng/) | Active | RootAtSkic | 2 | 1 |
+| [Maze Next Gen Team](/teams/mazeng/) | Active | RootAtSkic | 3 | 1 |
 
 A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.

docs/teams/mazeng.md

@@ -9,7 +9,7 @@ sidebar_position: 2
 |---|---|
 | Status | Active |
 | Lead | RootAtSkic |
-| Technical member | `jarvis-at-skic` / Hermes code agent |
+| Members | RootAtSkic; Jenny; `jarvis-at-skic` / Hermes code agent |
 | Assigned project | [Maze Next Gen](/projects/mazeng/) |
 
 ## Mandate
@@ -18,11 +18,11 @@ Deliver the Maze Next Gen multi-cloud inventory and visualization platform, docu
 
 ## Gitea access
 
-`maze-next-gen-team` exists independently in `corp-v1-mazeng` and `corp-v1-mazeng-skills-code-agent`, includes all repositories, and contains `root-at-skic` and `jarvis-at-skic`. Effective write access is verified for both members across two project and thirteen skill repositories.
+`maze-next-gen-team` exists independently in `corp-v1-mazeng` and `corp-v1-mazeng-skills-code-agent`, includes all repositories, and contains `root-at-skic` and `jarvis-at-skic`. Effective write access is verified for both existing Gitea members across two project and thirteen skill repositories. Jenny's repository access is pending until she signs in to Gitea at least once and supplies a verified username.
 
 ## Communication
 
-Six exact Maze channels, purpose messages, pinned guidance, and six isolated staggered hourly synchronization jobs are verified.
+Six exact Maze channels and their purpose messages and pinned guidance are verified. Jenny has effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access in all six. The membership update was announced in General as message `1540048213090771034`. Corp v1 project scheduler jobs are prohibited by the current operating model.
 
 ## Remaining gate
 

scripts/verify-portal.mjs

@@ -26,7 +26,7 @@ assert.match(config, /projectName:\s*'portal'/, 'Docusaurus project name must be
 assert.doesNotMatch(config, /sterring-commitee/, 'legacy repository name must not remain in Docusaurus config');
 
 const board = read('docs/board/index.md');
-for (const memberId of ['1518725627845283888', '476287310627864587', '773109855497093191', '364383883778850827']) {
+for (const memberId of ['1518725627845283888', '476287310627864587', '773109855497093191', '364383883778850827', '1483820991720329227', '1540035254746882048']) {
   assert.ok(board.includes(memberId), `board page is missing Discord member ${memberId}`);
 }
 assert.match(board, /Only these Board members may approve a project kickoff or project closure/i);