docs: expand Board and AeroSim membership
Build and publish Corp v1 Board portal / build (push) Successful in 34s
Build and publish Corp v1 Board portal / build (push) Successful in 34s
This commit is contained in:
+2
-1
@@ -7,13 +7,14 @@ sidebar_position: 1
|
||||
|
||||
# Board Members
|
||||
|
||||
The Corp v1 Board has exactly three members:
|
||||
The Corp v1 Board has exactly four members:
|
||||
|
||||
| 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 |
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -8,6 +8,7 @@ sidebar_position: 2
|
||||
|
||||
| Date | Decision | Scope | Owner | Record |
|
||||
|---|---|---|---|---|
|
||||
| 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/) |
|
||||
| 2026-08-12 | Authorize AeroSim test kickoff and begin provisioning | AeroSim | RootAtSkic | [AeroSim kickoff](/governance/decisions/aerosim-kickoff/) |
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Board and AeroSim membership expansion"
|
||||
description: "Record the approved addition of Eduard to the Corp v1 Board and three human members to the AeroSim team."
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Board and AeroSim membership expansion
|
||||
|
||||
- **Date:** 2026-08-14
|
||||
- **Status:** Approved and applied where identities are verified
|
||||
- **Approved by:** RootAtSkic (`<@1518725627845283888>`)
|
||||
- **Evidence:** `corp-v1-board` message `1537790262590578699`
|
||||
- **Scope:** Corp v1 Board authority and AeroSim team membership
|
||||
|
||||
## Decision
|
||||
|
||||
1. Add Eduard (`<@364383883778850827>`, `eduardanichess`) to the Corp v1 Board.
|
||||
2. Add Panther Skeleton (`<@476287310627864587>`), MartynasP (`<@773109855497093191>`), and Eduard (`<@364383883778850827>`) to the AeroSim project team.
|
||||
3. Preserve RootAtSkic as AeroSim sponsor and accountable lead.
|
||||
4. Apply project access through the existing Discord channel permissions and Gitea organization teams rather than direct repository collaborators.
|
||||
|
||||
## Applied state
|
||||
|
||||
- Eduard is listed in `corp-v1--main` and the Board registry with authority to approve project kickoff, project closure, and changes to `corp-v1--main`.
|
||||
- Discord identity and effective channel access are verified for all requested members. Existing permission overwrites already covered `corp-v1-board` and all six AeroSim channels; no additional Discord mutation was required.
|
||||
- Gitea identity `martynas-pazusis` is verified and was added to `aerosim-maintainers` and `aerosim-skill-maintainers`.
|
||||
- No matching Gitea accounts could be resolved for Panther Skeleton or Eduard. Their Gitea team membership remains pending verified usernames or account creation; this does not change their approved human team status or verified Discord access.
|
||||
|
||||
## Consequences
|
||||
|
||||
- The Corp v1 Board now has four members.
|
||||
- The AeroSim team registry now has five members, including the Hermes code agent.
|
||||
- Panther Skeleton, MartynasP, and Eduard may exercise the human project-team gates defined by AeroSim documentation in the authorized project channels.
|
||||
- Repository write access remains incomplete for Panther Skeleton and Eduard until their Gitea identities are verified.
|
||||
@@ -9,7 +9,7 @@ sidebar_position: 1
|
||||
|
||||
## Board authority
|
||||
|
||||
Only the three 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 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.
|
||||
|
||||
## 1. Proposed
|
||||
|
||||
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Eduard"
|
||||
description: "Identify Eduard's Corp v1 Board and AeroSim project responsibilities and verified access state."
|
||||
sidebar_position: 5
|
||||
---
|
||||
|
||||
# Eduard
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Status | Active |
|
||||
| Discord | `<@364383883778850827>` — `eduardanichess` / Eduard |
|
||||
| Governance roles | Corp v1 Board member; AeroSim human team member |
|
||||
| Team | [AeroSim Team](/teams/aerosim/) |
|
||||
| Active projects | [AeroSim](/projects/aerosim/) |
|
||||
| Gitea | Pending a verified username or account |
|
||||
|
||||
Eduard has verified effective access to `corp-v1-board` and all six AeroSim channels. Board authority covers project kickoff, project closure, and approval of changes to `corp-v1--main`.
|
||||
|
||||
No matching Gitea account could be resolved on 2026-08-14. Membership in `aerosim-maintainers` and `aerosim-skill-maintainers` remains pending until the account identity is verified.
|
||||
@@ -10,5 +10,8 @@ sidebar_position: 1
|
||||
|---|---|---|---|---:|
|
||||
| [RootAtSkic](/members/rootatskic/) | Active | AeroSim sponsor and lead | AeroSim Team | 1 |
|
||||
| [Jarvis at SKIC](/members/jarvis-at-skic/) | Active | AeroSim technical member and code agent | AeroSim Team | 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 |
|
||||
|
||||
Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
title: "MartynasP"
|
||||
description: "Identify MartynasP's Corp v1 Board and AeroSim project responsibilities and verified access state."
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# MartynasP
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Status | Active |
|
||||
| Discord | `<@773109855497093191>` — `w4rl0ck_21` / MartynasP |
|
||||
| Governance roles | Corp v1 Board member; AeroSim human team member |
|
||||
| Team | [AeroSim Team](/teams/aerosim/) |
|
||||
| Active projects | [AeroSim](/projects/aerosim/) |
|
||||
| Gitea | `martynas-pazusis` — verified in both AeroSim organization teams |
|
||||
|
||||
MartynasP has verified effective access to `corp-v1-board` and all six AeroSim channels. The verified Gitea identity belongs to both `aerosim-maintainers` and `aerosim-skill-maintainers`, which cover the two project repositories and all thirteen adopted skill repositories. Board authority covers project kickoff, project closure, and approval of changes to `corp-v1--main`.
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Panther Skeleton"
|
||||
description: "Identify Panther Skeleton's Corp v1 Board and AeroSim project responsibilities and verified access state."
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Panther Skeleton
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Status | Active |
|
||||
| Discord | `<@476287310627864587>` — `pantherskeleton` / Panther Skeleton |
|
||||
| Governance roles | Corp v1 Board member; AeroSim human team member |
|
||||
| Team | [AeroSim Team](/teams/aerosim/) |
|
||||
| Active projects | [AeroSim](/projects/aerosim/) |
|
||||
| Gitea | Pending a verified username or account |
|
||||
|
||||
Panther Skeleton has verified effective access to `corp-v1-board` and all six AeroSim channels. Board authority covers project kickoff, project closure, and approval of changes to `corp-v1--main`.
|
||||
|
||||
No matching Gitea account could be resolved on 2026-08-14. Membership in `aerosim-maintainers` and `aerosim-skill-maintainers` remains pending until the account identity is verified.
|
||||
@@ -11,7 +11,7 @@ sidebar_position: 1
|
||||
| Status | Active — lifecycle alignment reviewed |
|
||||
| Started | 2026-08-12 |
|
||||
| Sponsor and accountable lead | RootAtSkic |
|
||||
| Initial technical member | `jarvis-at-skic` / Hermes code agent |
|
||||
| Team members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; `jarvis-at-skic` / Hermes code agent |
|
||||
| Team | [AeroSim Team](/teams/aerosim/) |
|
||||
|
||||
## Purpose
|
||||
@@ -63,7 +63,7 @@ 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`. RootAtSkic was resolved as Discord member `1518725627845283888`.
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
@@ -103,7 +103,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.
|
||||
- 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.
|
||||
- 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.
|
||||
@@ -112,3 +112,5 @@ Each repository records the central source branch and commit in `ADOPTION.md`. A
|
||||
## Outstanding governance decisions
|
||||
|
||||
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.
|
||||
|
||||
@@ -9,7 +9,7 @@ sidebar_position: 1
|
||||
|---|---|
|
||||
| Status | Active |
|
||||
| Lead | RootAtSkic |
|
||||
| Verified technical member | `jarvis-at-skic` / Hermes code agent |
|
||||
| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; `jarvis-at-skic` / Hermes code agent |
|
||||
| Assigned project | [AeroSim](/projects/aerosim/) |
|
||||
|
||||
## Mandate
|
||||
@@ -27,8 +27,9 @@ 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` and `root-at-skic` membership and effective repository assignments are verified in both teams.
|
||||
- `jarvis-at-skic`, `root-at-skic`, and `martynas-pazusis` membership and effective repository assignments are verified in both teams.
|
||||
- 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.
|
||||
|
||||
## Communication
|
||||
|
||||
Exactly six AeroSim channels exist under the `corp-v1` category: `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`. Hermes 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, and Hermes have verified effective access. Guidance messages, the pinned general introduction, and six isolated same-project hourly synchronization jobs are verified.
|
||||
|
||||
+1
-1
@@ -8,6 +8,6 @@ sidebar_position: 1
|
||||
|
||||
| Team | Status | Lead | Members | Active projects |
|
||||
|---|---|---|---:|---:|
|
||||
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 2 | 1 |
|
||||
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 5 | 1 |
|
||||
|
||||
A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.
|
||||
|
||||
Reference in New Issue
Block a user