docs: onboard Jarvis across Corp v1

2026-09-05 11:43:00 +00:00
parent 6b024593c3
commit 76e1174257
18 changed files with 183 additions and 20 deletions
@@ -8,6 +8,7 @@ sidebar_position: 2

 | Date | Decision | Scope | Owner | Record |
 |---|---|---|---|---|
+| 2026-09-05 | Add Jarvis to the Corp v1 Board and every current project as executing code agent | Corp v1 governance, AeroSim, Maze Next Gen, E-Shop v1, 3D Architecture Wizzard, DPVP | RootAtSkic | [Jarvis Board and all-project membership](/governance/decisions/jarvis-board-all-project-membership/) |
 | 2026-08-27 | Authorize secret-safe use of the Bitwarden-injected shared Corp v1 SSO identity for approved system tasks | Corp v1 governance and all project channels | RootAtSkic | [Shared Corp v1 system SSO credentials](/governance/decisions/shared-system-sso-credentials/) |
 | 2026-08-27 | Separate each project's lifecycle channels into one dedicated Discord category | Corp v1 governance, AeroSim, Maze Next Gen, E-Shop v1 | RootAtSkic | [Dedicated Discord category per project](/governance/decisions/project-discord-category-separation/) |
 | 2026-08-27 | Establish the Corp v1 Guild improvement workspace, skill, Gitea source, and portal architecture representation | Corp v1 governance and operating-model improvement | RootAtSkic | [Corp v1 Guild establishment](/governance/decisions/corp-v1-guild-establishment/) |
@@ -0,0 +1,36 @@
+---
+title: Jarvis Board and all-project membership
+description: "Record the approval, access changes, verification, and consequences of onboarding Jarvis across Corp v1."
+---
+
+# Jarvis Board and all-project membership
+
+## Context
+
+Jarvis already served as an executing Hermes code agent in several Corp v1 projects, but the Board and project registries did not consistently record its role or access across every current project. DPVP also had a Discord workspace but no published portal project record or Gitea organization boundary.
+
+## Decision
+
+On 2026-09-05, RootAtSkic (`discord:1518725627845283888`) explicitly approved in Board message `1545759332845490208`:
+
+- adding Jarvis (`discord:1526860732917088266`, Gitea `jarvis-at-skic`, user ID `24`) as the eighth Corp v1 Board member and executing code agent;
+- adding Jarvis as a technical member/code agent of AeroSim, Maze Next Gen, E-Shop v1, 3D Architecture Wizzard, and DPVP;
+- verifying Board and all 35 project lifecycle-channel permissions;
+- assigning Jarvis through each project's project and skills/code-agent organization teams; and
+- publishing synchronized Board, member, team, and project records, including DPVP.
+
+Jarvis's Board membership is operational: it executes and verifies explicitly approved work. The seven human Board members retain approval authority, and Jarvis cannot approve its own execution or substitute for an explicit human decision.
+
+## Verification
+
+- Discord identity `1526860732917088266` is the guild member `jarvis-jr-at-skic-hermes` and has administrator permission.
+- Effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access passed for `corp-v1-board` and each of the 35 lifecycle channels.
+- Gitea `jarvis-at-skic` is active and verified in ten all-repository teams: `23`, `24`, `29`, `31`, `35`, `36`, `39`, `40`, `45`, and `47`.
+- Existing memberships and permissions were preserved; only missing Jarvis memberships and the absent DPVP organization/team boundaries were added.
+
+## Consequences
+
+1. The Board registry contains eight members while preserving human approval gates.
+2. Every current project identifies Jarvis as an executing code agent.
+3. DPVP now has private project and skills/code-agent organizations with all-repository teams, but its repositories, adopted skills, Harbor configuration, and deployed documentation remain kickoff gates.
+4. Secret values were neither accessed nor modified.