Files
portal/docs/board/index.md
T
jarvis-at-skic 76e1174257
Build and publish Corp v1 Board portal / build (push) Successful in 50s
docs: onboard Jarvis across Corp v1
2026-09-05 11:43:00 +00:00

2.4 KiB

title, description, slug, sidebar_position
title description slug sidebar_position
Board Members Identify the only members authorized to start or close Corp v1 projects and approve changes to the Corp v1 main governance skill. / 1

Board Members

The Corp v1 Board has exactly eight members. Seven human members retain approval authority; Jarvis is the Board's executing code agent and does not substitute for an explicit human Board decision.

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
<@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
<@501954115690168321> Piotras (piotras0262) Start/close projects; approve corp-v1-main changes
<@1526860732917088266> Jarvis (jarvis-jr-at-skic-hermes) Board member and executing code agent; implements and verifies explicitly approved Board work

Only the seven human Board members may approve a project kickoff or project closure. Approval must be explicit and attributable to one of their Discord IDs above; Jarvis cannot approve its own execution.

Only the seven human Board members may approve changes to corp-v1-main. Jarvis and other agents may identify gaps, prepare proposals, and execute an approved change, but they must not originate approval or infer it from silence.

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, Discord access, and absence of Corp v1 synchronization schedulers before recording completion.