governance: record Linas Board and AeroSim membership
Build and publish Corp v1 Board portal / build (pull_request) Successful in 33s

This commit is contained in:
2026-08-17 07:32:47 +00:00
parent f889072d59
commit c88a9ac220
10 changed files with 70 additions and 10 deletions
+1
View File
@@ -8,6 +8,7 @@ sidebar_position: 2
| Date | Decision | Scope | Owner | Record |
|---|---|---|---|---|
| 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/) |
@@ -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.
+1 -1
View File
@@ -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 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.
## 1. Proposed