governance: record Linas Board and AeroSim membership
Build and publish Corp v1 Board portal / build (pull_request) Successful in 33s
Build and publish Corp v1 Board portal / build (pull_request) Successful in 33s
This commit is contained in:
+2
-1
@@ -7,7 +7,7 @@ sidebar_position: 1
|
||||
|
||||
# Board Members
|
||||
|
||||
The Corp v1 Board has exactly four members:
|
||||
The Corp v1 Board has exactly five members:
|
||||
|
||||
| Discord member | Account | Board authority |
|
||||
|---|---|---|
|
||||
@@ -15,6 +15,7 @@ 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 |
|
||||
|
||||
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-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.
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -13,5 +13,6 @@ 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 |
|
||||
|
||||
Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.
|
||||
|
||||
@@ -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`.
|
||||
@@ -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; `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`. 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`), and Linas (`1483820991720329227`) across all six project channels. Linas has effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY`; no permission mutation was needed. The team update was announced in General as message `1538811290925928505`.
|
||||
|
||||
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 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.
|
||||
@@ -114,3 +114,5 @@ 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.
|
||||
|
||||
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.
|
||||
|
||||
@@ -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; `jarvis-at-skic` / Hermes code agent |
|
||||
| Assigned project | [AeroSim](/projects/aerosim/) |
|
||||
|
||||
## Mandate
|
||||
@@ -27,9 +27,10 @@ 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.
|
||||
|
||||
## 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, and Hermes have verified effective access. Linas's effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` permissions were verified in all six channels without a permission mutation. The membership update was announced in General as message `1538811290925928505`. 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 | 5 | 1 |
|
||||
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 6 | 1 |
|
||||
|
||||
A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.
|
||||
|
||||
Reference in New Issue
Block a user