Compare commits

...
Author SHA1 Message Date
jarvis-at-skic fcbed3e8ee Merge pull request 'governance: transition AeroSim Scope ownership' (#26) from governance/aerosim-scope-owner-transition-20260928 into main
Build and publish Corp v1 Board portal / build (push) Successful in 52s
2026-09-28 03:16:35 -07:00
jarvis-at-skic efb6115531 governance: transition AeroSim Scope ownership
Build and publish Corp v1 Board portal / build (pull_request) Successful in 52s
2026-09-28 10:07:03 +00:00
jarvis-at-skic 6fc3f9f74b docs: update AeroSim Wave 15 portfolio roll-up
Build and publish Corp v1 Board portal / build (push) Successful in 37s
Reviewed portfolio reconciliation with exact-head CI.
2026-09-06 21:42:01 -07:00
jarvis-at-skic 61aa7d6454 [verified] docs: update AeroSim Wave 15 roll-up
Build and publish Corp v1 Board portal / build (pull_request) Successful in 40s
2026-09-07 04:40:52 +00:00
jarvis-at-skic 5e2857e918 Merge pull request 'Governance: onboard Friday to portal and Discord workspaces' (#24) from governance/friday-portal-discord-onboarding into main
Build and publish Corp v1 Board portal / build (push) Successful in 40s
Record Friday portal and Discord onboarding
2026-09-05 04:52:03 -07:00
jarvis-at-skic cc3f461899 [verified] docs: record Friday portal and Discord onboarding
Build and publish Corp v1 Board portal / build (pull_request) Successful in 43s
2026-09-05 11:49:42 +00:00
jarvis-at-skic 76e1174257 docs: onboard Jarvis across Corp v1
Build and publish Corp v1 Board portal / build (push) Successful in 50s
2026-09-05 11:43:00 +00:00
jarvis-at-skic 6b024593c3 docs: record skill name separator migration
Build and publish Corp v1 Board portal / build (push) Successful in 36s
2026-09-04 13:13:46 +00:00
jarvis-at-skic 10f3f5e669 chore: trigger portal publication for final records
Build and publish Corp v1 Board portal / build (push) Successful in 36s
2026-09-04 13:07:09 +00:00
jarvis-at-skic 22fbce6f90 fix: update project skill suffix records
Build and publish Corp v1 Board portal / build (push) Successful in 38s
2026-09-04 13:04:27 +00:00
jarvis-at-skic fe228108af fix: update Corp v1 skill references
Build and publish Corp v1 Board portal / build (push) Successful in 39s
2026-09-04 12:55:03 +00:00
jarvis-at-skic 666b6a8d25 Merge pull request 'docs: reconcile AeroSim Wave 2 progress' (#23) from docs/aerosim-wave2-progress into main
Build and publish Corp v1 Board portal / build (push) Successful in 38s
2026-09-03 14:33:35 -07:00
jarvis-at-skic 42b876e82e [verified] docs: reconcile AeroSim Wave 2 progress
Build and publish Corp v1 Board portal / build (pull_request) Successful in 39s
2026-09-03 21:32:16 +00:00
jarvis-at-skic 62c647f516 Merge pull request 'ui: reorder top-level navigation' (#22)
Build and publish Corp v1 Board portal / build (push) Successful in 38s
2026-09-03 12:25:55 -07:00
jarvis-at-skic 90f3aa0c11 [verified] ui: reorder top-level navigation
Build and publish Corp v1 Board portal / build (pull_request) Successful in 38s
2026-09-03 19:24:34 +00:00
jarvis-at-skic 04e2b2ceee Merge pull request 'docs: report AeroSim delivery progress' (#21) from docs/aerosim-delivery-progress into main
Build and publish Corp v1 Board portal / build (push) Successful in 50s
2026-09-03 12:19:57 -07:00
jarvis-at-skic fc20f12128 [verified] docs: report AeroSim delivery progress
Build and publish Corp v1 Board portal / build (pull_request) Successful in 49s
2026-09-03 19:18:41 +00:00
jarvis-at-skic 1be8fcfd6d Governance: align AeroSim channel membership (#20)
Build and publish Corp v1 Board portal / build (push) Successful in 36s
Approved by RootAtSkic in AeroSim General message 1543962382978514964.
2026-08-31 05:40:58 -07:00
jarvis-at-skic 23ad72c038 governance: align AeroSim channel membership
Build and publish Corp v1 Board portal / build (pull_request) Successful in 36s
2026-08-31 12:39:14 +00:00
jarvis-at-skic 481e2b0ea8 docs: complete 3D Architecture Wizzard kickoff
Build and publish Corp v1 Board portal / build (push) Successful in 36s
2026-08-31 10:40:39 +00:00
jarvis-at-skic 7fcbccc1fb docs: record 3D Architecture Wizzard kickoff
Build and publish Corp v1 Board portal / build (push) Successful in 49s
2026-08-31 10:05:41 +00:00
jarvis-at-skic a7cedaaab1 docs: add Corp pilot Ways of Working onboarding
Build and publish Corp v1 Board portal / build (push) Successful in 36s
Publish the Board-requested onboarding guide and navigation.
2026-08-27 14:54:52 -07:00
jarvis-at-skic 9e6514de51 docs: add Corp pilot onboarding guide
Build and publish Corp v1 Board portal / build (pull_request) Successful in 36s
2026-08-27 21:53:44 +00:00
jarvis-at-skic 1226329a7a docs: record final shared SSO rollout refs
Build and publish Corp v1 Board portal / build (push) Successful in 35s
Record final central and adopted UI/UX refs after login-routing correction.
2026-08-27 13:58:57 -07:00
54 changed files with 1256 additions and 168 deletions
@@ -17,14 +17,14 @@ Corp v1 uses **two central portfolio workspaces** and **seven purpose-specific c
`corp-v1-guild` is the shared improvement workspace for RootAtSkic and Hermes. It correlates recurring friction across Corp v1 channels, skills, reference skills, repositories, and this portal; inventories the affected owners; and coordinates a verified rollout.
The Guild does not grant approval that belongs to the Board or a project channel. It routes product, architecture, design, flow, implementation, and release decisions back to their owning project workspace. Its authoritative operating skill is [`corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild).
The Guild does not grant approval that belongs to the Board or a project channel. It routes product, architecture, design, flow, implementation, and release decisions back to their owning project workspace. Its authoritative operating skill is [`corp-v1-guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-guild).
## Portfolio governance: `corp-v1-board`
`corp-v1-board` exists once for the whole Corp v1 pilot. It is the authoritative Discord workspace for decisions that change the portfolio operating model:
- approve project kickoffs, closures, and membership changes;
- approve changes to the global `corp-v1--main` governance skill;
- approve changes to the global `corp-v1-main` governance skill;
- approve central `corp-v1-channel-*` reference-skill changes;
- resolve conflicts that cannot be decided inside one project;
- review portfolio-level evidence and remaining gates.
@@ -51,7 +51,7 @@ The same Hermes agent operates across the pilot, but each Discord channel has it
1. **Shared identity and governance** — one agent follows the same Board-approved operating model.
2. **Focused context** — Scope discussion does not become Delivery execution, and one project's decisions do not silently become another project's decisions.
3. **Specialised behavior** — the mapped `corp-v1-channel-<channel>--<code>` skill defines the channel's responsibilities, approvals, evidence, and handoffs.
3. **Specialised behavior** — the mapped `corp-v1-channel-<channel>-<code>` skill defines the channel's responsibilities, approvals, evidence, and handoffs.
4. **Engineering depth on demand** — relevant project engineering skills are loaded alongside the channel skill for documentation, branching, monorepo work, CI/CD, GitOps, scripts, and templates.
5. **Durable evidence** — decisions and current state are written to Discord, Gitea, project documentation, and the Board portal rather than existing only in an agent session.
@@ -30,7 +30,7 @@ The corresponding skills team grants access to:
- seven adopted engineering-skill repositories;
- their complete supporting assets, scripts, templates, references, and preserved adoption history.
The global `drawio-main` and `corp-v1--glossary` remain shared references unless an explicit project decision adopts a local copy.
The global `drawio-main` and `corp-v1-glossary` remain shared references unless an explicit project decision adopts a local copy.
## Delivery evidence
@@ -19,9 +19,9 @@ The central sources live in [`home-v1-skills-code-agent`](https://gitea.lego-clo
| Skill | Purpose |
|---|---|
| [`corp-v1--main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main) | Board authority, project lifecycle, resource model, membership, adoption, publication, and verification rules. |
| [`corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild) | Cross-channel improvement intake, impact inventory, ownership routing, coordinated rollout, and convergence verification. |
| [`corp-v1--glossary`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--glossary) | Shared terminology and rules for keeping canonical definitions in project documentation. |
| [`corp-v1-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main) | Board authority, project lifecycle, resource model, membership, adoption, publication, and verification rules. |
| [`corp-v1-guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-guild) | Cross-channel improvement intake, impact inventory, ownership routing, coordinated rollout, and convergence verification. |
| [`corp-v1-glossary`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-glossary) | Shared terminology and rules for keeping canonical definitions in project documentation. |
| [`corp-v1-channel-general`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-general) | Onboarding, coordination, questions, and outcome broadcasts. |
| [`corp-v1-channel-scope`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-scope) | Ideas, Epics, Features, value, acceptance outcomes, and human solution approval. |
| [`corp-v1-channel-architecture`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-architecture) | Requirements, ADRs, interfaces, constraints, system design, and implementation Tasks. |
@@ -34,12 +34,12 @@ The central sources live in [`home-v1-skills-code-agent`](https://gitea.lego-clo
Every project owns fourteen adopted repositories in `corp-v1-<code>-skills-code-agent`:
- seven channel skills named `corp-v1-channel-<channel>--<code>`;
- seven engineering skills named `<source-skill>--<code>`.
- seven channel skills named `corp-v1-channel-<channel>-<code>`;
- seven engineering skills named `<source-skill>-<code>`.
A project adoption records the central source branch and commit, then adds the project code, repository links, environment namespace, approved authority, and operating lessons. Central updates are compared and adopted semantically; they never silently overwrite project-specific decisions or authorization overrides.
`corp-v1--guild` remains central because it coordinates improvements across projects. It is not copied as a fifteenth project skill and does not replace any mapped project channel skill.
`corp-v1-guild` remains central because it coordinates improvements across projects. It is not copied as a fifteenth project skill and does not replace any mapped project channel skill.
At runtime, a focused channel session loads its mapped project channel skill plus only the engineering or global skills needed for the current work.
+16 -11
View File
@@ -7,26 +7,31 @@ sidebar_position: 1
# Board Members
The Corp v1 Board has exactly seven 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 |
| `<@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 these Board members may approve a project kickoff or project closure. Approval must be explicit and attributable to one of the Discord IDs above.
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 these Board members may approve changes to `corp-v1--main`. Other members and agents may identify gaps and prepare proposals, but they must not publish governance changes as approved.
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.
## Operational agents
Friday Jr (`<@1542987400358404268>`, Discord account `friday-jr-at-skic-hermes`) has operational access to the Board workspace as a code agent. This access permits reading history, posting evidence, and supporting approved work; it does **not** make the service identity a Board member or grant human approval authority.
## 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>`).
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.
+2
View File
@@ -8,6 +8,8 @@ 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-09-05 | Onboard Friday Jr as a non-human Board-support and all-project code agent | Corp v1 governance and all five project Discord workspaces; provisioned Gitea projects | RootAtSkic | [Friday Jr Board-support and all-project agent access](/governance/decisions/friday-board-support-all-project-access/) |
| 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: 3D Architecture Wizzard kickoff
---
# 3D Architecture Wizzard kickoff — 2026-08-31
## Decision
Provision **3D Architecture Wizzard**, code `3darch`, as a public Corp v1 project. Linas (`discord:1483820991720329227`) is the accountable team lead and initial member.
RootAtSkic (`discord:1518725627845283888`) explicitly requested project setup in Board message `1543918340882436166` and approved the complete kickoff proposal in the same Board session. RootAtSkic explicitly retained the spelling **Wizzard**.
## Purpose
Create an interactive 3D application for exploring, designing, and communicating software and system architecture.
## Initial deliverable
A browser-based proof of concept that visualizes one architecture model in navigable 3D.
## Authorized resources
- Dedicated category `corp-v1-3darch` with exactly seven lifecycle channels in approved order.
- Project organization `corp-v1-3darch` and skills organization `corp-v1-3darch-skills-code-agent`.
- Application and documentation repositories.
- Seven adopted engineering skills and seven adopted channel skills.
- Project and skills organization teams for verified Gitea user `linas`.
- Required Harbor non-secret variables and secret-name-only validation.
- Global Draw.io and glossary references.
- No project cronjobs or scheduler jobs.
## Current state
Provisioned and remotely verified. Application `847c8291f100547ec9104743ab7d0d8761a5ec20` and documentation `73cf70f0f333c187b28821fb76a44c779bdfbbdb` have successful exact-head Actions; the documentation page body was read back through the Gondor operator route. Exactly seven project channels, two organizations, two teams, two project repositories, and fourteen adopted skills exist.
The project is **Active — lead activation pending**. Gitea user `linas` is assigned to both teams but remains inactive. The Harbor secret name is present; its value was neither requested nor accessed.
@@ -0,0 +1,14 @@
---
title: "AeroSim channel membership alignment"
description: "Record the approved onboarding of four channel-authorized people into the AeroSim team."
---
# AeroSim channel membership alignment
- **Approved by:** RootAtSkic (`<@1518725627845283888>`)
- **Approval evidence:** AeroSim General message `1543962382978514964`
- **Date:** 2026-08-31
Andrius (`<@204689314796273674>`, account `whyt6249`), Dovydas (`<@1543952051212656684>`, account `dovydaszelenkevicius`), Giedrius K (`<@1543940246071410706>`, account `giedriusk_62552`), and Jone Tamulaite - Nong (`<@1067100220321714278>`, account `jtamul`) are AeroSim human project members.
Each person has verified effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access to `corp-v1-aerosim-general`. Their Gitea identities remain unresolved, so membership in `aerosim-maintainers` and `aerosim-skill-maintainers` is pending verified usernames or account creation. No Gitea identity was inferred from display-name similarity.
+1 -1
View File
@@ -20,7 +20,7 @@ The initial deliverable is a playable browser MVP for trainer, airliner, and fig
- `corp-v1-aerosim` project organization.
- `corp-v1-aerosim-skills-code-agent` skills organization.
- Application and documentation repositories.
- Eight adopted project-scoped skills using suffix `--aerosim`.
- Eight adopted project-scoped skills using suffix `-aerosim`.
- Corresponding organization teams.
- Three same-project cross-channel review jobs.
- Harbor non-secret variables and validation of secret-name presence only.
@@ -0,0 +1,26 @@
---
title: AeroSim Scope Owner Transition
description: Record Jone Tamulaite - Nong's offboarding and MartynasP's appointment as primary AeroSim Scope owner.
---
# AeroSim Scope Owner Transition
- **Status:** Approved
- **Decision date:** 2026-09-28
- **Approver:** RootAtSkic (`discord:1518725627845283888`)
- **Evidence:** AeroSim Scope message `1554069052773900391`
- **Affected project:** [AeroSim](/projects/aerosim/)
## Decision
1. Jone Tamulaite - Nong (`discord:1067100220321714278`) leaves the AeroSim project and relinquishes the primary Scope-owner role.
2. MartynasP (`discord:773109855497093191`) succeeds Jone as primary AeroSim Scope owner.
3. MartynasP may make routine Epic and Feature lifecycle, priority, outcome, and `Approved for Solution` decisions under the existing AeroSim Scope authority contract.
4. RootAtSkic remains backup owner across all AeroSim domains.
5. Historical decisions made under the prior ownership assignment remain preserved; this decision changes current authority prospectively.
## Access consequences
- MartynasP was already an AeroSim team member and has a verified Gitea identity, `martynas-pazusis`, in both AeroSim organization teams; onboarding does not require duplicate team membership.
- Jone never had a verified Gitea mapping or membership in either AeroSim organization team, so there is no Gitea team membership to revoke.
- Jone's Discord project access must be removed and MartynasP's effective view, send, and history permissions across the current eight-channel project topology must be freshly verified before operational offboarding/onboarding is closed.
@@ -21,7 +21,7 @@ sidebar_position: 1
## 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`.
- 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 permission mutation was required.
- The applied team update was announced in `corp-v1-aerosim-general` as message `1537793704465801256`.
- Gitea identity `martynas-pazusis` is verified and was added to `aerosim-maintainers` and `aerosim-skill-maintainers`.
@@ -15,14 +15,14 @@ slug: /decisions/corp-v1-board-migration/
## Decision
1. Replace the steering committee channel with the Corp v1 Board channel. Discord canonicalized the requested `corp-v1--board` text-channel name to `corp-v1-board`; the immutable channel ID remains `1537070875503886356`.
2. Rename the global governance skill and repository to `corp-v1--main`.
2. Rename the global governance skill and repository to `corp-v1-main`.
3. Rename `corp-v1/sterring-commitee` to `corp-v1/portal` and deploy it at `https://pages.apps.lego-cloud.eu/corp-v1/portal/`.
4. Establish exactly these Board members:
- RootAtSkic (`<@1518725627845283888>`)
- Panther Skeleton (`<@476287310627864587>`)
- MartynasP (`<@773109855497093191>`)
5. Only these Board members may approve a project kickoff, project closure, or a change to `corp-v1--main`.
6. Central `corp-v1-channel-*` reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted `corp-v1-channel-*--<code>` skill; synchronization must preserve project-specific decisions.
5. Only these Board members may approve a project kickoff, project closure, or a change to `corp-v1-main`.
6. Central `corp-v1-channel-*` reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted `corp-v1-channel-*-<code>` skill; synchronization must preserve project-specific decisions.
## Consequences
@@ -11,21 +11,21 @@ On 2026-08-27, RootAtSkic (`discord:1518725627845283888`) established `corp-v1-g
The approved implementation includes:
- Discord channel `corp-v1-guild` (`1542596418215092264`) under the `corp-v1` category;
- central operating skill `corp-v1--guild`;
- private Gitea source repository [`home-v1-skills-code-agent/corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild) on default branch `test`;
- central operating skill `corp-v1-guild`;
- private Gitea source repository [`home-v1-skills-code-agent/corp-v1-guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-guild) on default branch `test`;
- runtime installation of the published skill;
- Guild guidance linked and pinned in the channel;
- Corp v1 portal architecture updates that distinguish Guild improvement coordination from Board governance and the seven project delivery channels.
## Evidence
The approving instruction is Discord message `1542596833266761748` in channel `1542596418215092264`. RootAtSkic requested a skill similar in durability to `corp-v1--main`, defined the channel's purpose as improvements across channels, their skills, and reference skills, and required both portal architecture and Gitea publication.
The approving instruction is Discord message `1542596833266761748` in channel `1542596418215092264`. RootAtSkic requested a skill similar in durability to `corp-v1-main`, defined the channel's purpose as improvements across channels, their skills, and reference skills, and required both portal architecture and Gitea publication.
## Authority boundary
The Guild coordinates improvement discovery, impact inventory, ownership routing, implementation, rollout, and verification. It does not replace:
- the Corp v1 Board for project lifecycle, membership, `corp-v1--main`, or central channel-reference approvals;
- the Corp v1 Board for project lifecycle, membership, `corp-v1-main`, or central channel-reference approvals;
- project Scope, Architecture, UI/UX, Kanban, Delivery, or Releases decisions;
- preserved project-local authorization overrides;
- repository validation, review, exact-head CI, deployed readback, or destructive-action safeguards.
@@ -33,7 +33,7 @@ Live PayPal payments, purchases, spending, vendor-account changes, legal/commerc
- Private project organization `corp-v1-eshopv1`.
- Private skills organization `corp-v1-eshopv1-skills-code-agent`.
- Application repository `corp-v1-eshopv1` and documentation repository `corp-v1-eshopv1-documentation`.
- Seven adopted engineering skills and seven adopted channel skills, all suffixed `--eshopv1`.
- Seven adopted engineering skills and seven adopted channel skills, all suffixed `-eshopv1`.
- Project and skills organization teams for RootAtSkic and `jarvis-at-skic`.
- One 30-minute bootstrap job delivered only to `corp-v1-eshopv1-general`.
@@ -0,0 +1,28 @@
---
title: "Friday Jr Board-support and all-project agent access"
description: "Record Friday Jr's operational access across Corp v1 without granting human decision authority."
---
# Friday Jr Board-support and all-project agent access
## Authority
- **Approved by:** RootAtSkic (`<@1518725627845283888>`)
- **Approval evidence:** Discord Board message `1545758343489130598`
- **Date:** 2026-09-05
## Decision
Onboard Discord service identity `<@1542987400358404268>` (`friday-jr-at-skic-hermes`) as an operational code agent in the Corp v1 Board workspace and every current project workspace: 3D Architecture Wizzard, AeroSim, DPVP, E-Shop v1, and Maze Next Gen.
This decision grants operational access only. Friday Jr is not added to the seven-person human Board roster and receives no authority to approve project lifecycle changes, human task readiness, designs, releases, spending, credentials, or governance changes.
## Verified access
- Discord role `friday-jr-v1-hermes` has Administrator. Fresh effective-permission evaluation verified view, send, and history access in the Board channel and all thirty-five lifecycle channels across the five project categories.
- Gitea account `friday-at-skic` (user ID `92`) is assigned through team `corp-v1-code-agents` and both project/skill teams for 3D Architecture Wizzard, AeroSim, DPVP, E-Shop v1, and Maze Next Gen.
- The eleven verified teams currently cover one governance repository, twelve project-organization repositories, and fifty-six project-skill repositories. DPVP's two new teams contain Friday but have no repositories yet.
## Outstanding activation
Gitea reports `friday-at-skic` as inactive and its own API token returns HTTP `403`. The executing account cannot administer users, so a Gitea administrator must activate Friday before operational repository access can be exercised. DPVP's Discord workspace, both organizations, and both team memberships are ready; repository coverage will begin when DPVP repositories are provisioned.
@@ -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.
@@ -10,7 +10,7 @@ Corp v1 lifecycle policy requires each managed project to operate six Discord wo
## Decision
Align every currently managed Corp v1 project to the six-channel lifecycle. For AeroSim, create and verify `corp-v1-aerosim-kanban`, attach `corp-v1-channel-kanban--aerosim`, create its staggered hourly job, and update every existing AeroSim synchronization job to the exact six-channel same-project boundary.
Align every currently managed Corp v1 project to the six-channel lifecycle. For AeroSim, create and verify `corp-v1-aerosim-kanban`, attach `corp-v1-channel-kanban-aerosim`, create its staggered hourly job, and update every existing AeroSim synchronization job to the exact six-channel same-project boundary.
Human gates remain unchanged: only a human team member may approve an Epic or Feature for solution, approve a Feature for implementation, admit an exact task to Focus `InBacklog`, approve final version allocation, or request a release.
+1 -1
View File
@@ -20,7 +20,7 @@ Approval was explicit from Board member `discord:1518725627845283888` in message
- `corp-v1-mazeng` project organization.
- `corp-v1-mazeng-skills-code-agent` skills organization.
- Application and documentation repositories.
- Seven adopted engineering skills and six adopted channel skills, all suffixed `--mazeng`.
- Seven adopted engineering skills and six adopted channel skills, all suffixed `-mazeng`.
- Six same-project staggered hourly synchronization jobs.
- Corresponding project and skills organization teams for RootAtSkic and `jarvis-at-skic`.
- Two approved non-secret Harbor organization variables and secret-name-only validation.
@@ -20,7 +20,7 @@ RootAtSkic (`discord:1518725627845283888`) approved one dedicated top-level Disc
## Implementation
The central [`corp-v1--main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main) skill was updated to version `4.3.0` and merged through PR [8](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main/pulls/8) at `785e57d6381f60a0caacefdedec791aa3b1fe2fd`.
The central [`corp-v1-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main) skill was updated to version `4.3.0` and merged through PR [8](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main/pulls/8) at `785e57d6381f60a0caacefdedec791aa3b1fe2fd`.
Three categories were created with the existing approved permission-overwrite model:
@@ -29,7 +29,7 @@ Credential values, Bitwarden object identifiers, and account metadata must not b
## Implementation and verification
The central `corp-v1--main` skill was updated to version `4.4.0` and merged through PR [9](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main/pulls/9) at `b11b0e521dab6b7a920337feed37c5a849d507bd`.
The central `corp-v1-main` skill was updated to version `4.4.0` and merged through PR [9](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-main/pulls/9) at `b11b0e521dab6b7a920337feed37c5a849d507bd`.
The same secret-safe login section was published central-first to all seven `corp-v1-channel-*` reference skills, then semantically adopted into all 21 project channel skills across AeroSim, Maze Next Gen, and E-Shop v1. Every project-local authorization override was hash-checked before and after adoption, project bindings and supporting files were preserved, and every pushed default ref and `SKILL.md` marker was read back. All 21 installed Hermes runtime packages were refreshed from the resulting project repositories. The exact repository, branch, commit, and override coverage is recorded in the [shared SSO skill rollout ledger](/governance/sso-skill-rollout/).
@@ -0,0 +1,34 @@
---
title: Skill name separator migration
sidebar_position: 13
---
# Skill name separator migration
- **Improvement ID:** `GUILD-IMP-20260904-skill-name-separators`
- **Status:** Complete
- **Approved by:** RootAtSkic (`discord:1518725627845283888`)
- **Approval evidence:** Discord message `1545414655609016450`
- **Date:** 2026-09-04
## Decision
Corp v1 skill names use single hyphens only. Consecutive ASCII hyphens are not permitted in skill frontmatter names, installed package folders, project-adopted skill repository names, cross-skill references, automation attachments, portal records, or active channel guidance.
Project qualification now follows these forms:
```text
<source-skill>-<project-code>
corp-v1-channel-<channel>-<project-code>
```
Central examples include `corp-v1-main`, `corp-v1-guild`, `corp-v1-glossary`, and `corp-v1-presentation`.
## Applied scope
- Renamed and remotely verified 59 existing Gitea skill repositories across central Corp v1 governance and the 3D Architecture, AeroSim, E-Shop v1, and Maze Next Gen projects.
- Published the previously local-only `corp-v1-presentation` package as `home-v1-skills-code-agent/corp-v1-presentation`.
- Updated central channel references, project adoption manifests, supporting files, the active Hermes runtime packages, scheduled-job attachments and prompts, and pinned Discord guidance.
- Preserved project authorization overrides, source provenance, repository history, and inactive historical workspaces.
Legacy Gitea URLs may resolve through Gitea's rename alias, but organization repository inventories and all canonical links use the new single-hyphen names.
+3 -3
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 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
@@ -21,7 +21,7 @@ Obtain explicit Board approval. Record the approving Board member, decision evid
## 3. Active
Maintain current status, decisions, risks, milestones, and material scope changes. Project teams retain authority within their approved project boundaries; Board approval is still required for kickoff/closure and changes to `corp-v1--main`.
Maintain current status, decisions, risks, milestones, and material scope changes. Project teams retain authority within their approved project boundaries; Board approval is still required for kickoff/closure and changes to `corp-v1-main`.
### Discord topology
@@ -33,7 +33,7 @@ For an explicitly authorized Corp v1 system task, Hermes may use the Bitwarden-i
### Project-channel skill changes
A proposed change to a central project-channel reference skill (`corp-v1-channel-*`) must be presented to the Board before publication. After explicit Board approval and central publication, ask every affected project channel to review and synchronize its project-adopted channel skill (`corp-v1-channel-*--<code>`). Synchronization must preserve project-specific decisions, report conflicts for Board review, update runtime copies, and verify attached channel jobs.
A proposed change to a central project-channel reference skill (`corp-v1-channel-*`) must be presented to the Board before publication. After explicit Board approval and central publication, ask every affected project channel to review and synchronize its project-adopted channel skill (`corp-v1-channel-*-<code>`). Synchronization must preserve project-specific decisions, report conflicts for Board review, update runtime copies, and verify attached channel jobs.
## 4. Paused
+21 -21
View File
@@ -15,27 +15,27 @@ This ledger records the Board-approved secret-name-only login guidance published
| Central reference | [corp-v1-channel-kanban](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-kanban) | `test` | `87a50a926a7256201ce1771aad7764898f24ff60` | 0 |
| Central reference | [corp-v1-channel-delivery](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-delivery) | `test` | `20cb78ce0942b35fe6528399c22764fbfb4cf06a` | 0 |
| Central reference | [corp-v1-channel-releases](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-releases) | `test` | `94d147880f6c957967d6612cbd846f9a2f2f6c00` | 0 |
| aerosim | [corp-v1-channel-general--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-general--aerosim) | `test` | `e50dc8878ebe74b6c58601204508e4723bb7803d` | 0 |
| aerosim | [corp-v1-channel-scope--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-scope--aerosim) | `test` | `0b6cee38a12803b4a7ceefe824e6a510ea35fec3` | 1 |
| aerosim | [corp-v1-channel-architecture--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-architecture--aerosim) | `test` | `c2c379ea6875d1b2c91cd6d02da588b8cf06bcb6` | 1 |
| aerosim | [corp-v1-channel-ui-ux--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-ui-ux--aerosim) | `test` | `26d786b310e86c87d70542a680367c768474d28e` | 1 |
| aerosim | [corp-v1-channel-kanban--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-kanban--aerosim) | `test` | `e75f81d559996e9cab97092bf94db33a324830d1` | 0 |
| aerosim | [corp-v1-channel-delivery--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-delivery--aerosim) | `test` | `af697f5d1ef708c66db3ab62fd1fa9094b7735a2` | 0 |
| aerosim | [corp-v1-channel-releases--aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-releases--aerosim) | `test` | `e85df7e82daa004bf0dc5a8db9ea09a99507583b` | 0 |
| mazeng | [corp-v1-channel-general--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-general--mazeng) | `test` | `12579704b8afad3af41b55b540ad21132e2ac299` | 1 |
| mazeng | [corp-v1-channel-scope--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-scope--mazeng) | `test` | `51ee9f4722a6ba5f9bbd13384ae8674690e070f9` | 1 |
| mazeng | [corp-v1-channel-architecture--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-architecture--mazeng) | `test` | `4c80704a0bd065accba49d523f6a83f51f8c1d2c` | 1 |
| mazeng | [corp-v1-channel-ui-ux--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-ui-ux--mazeng) | `test` | `547aabf245cd032dd82f95f3273c27753adbbd00` | 2 |
| mazeng | [corp-v1-channel-kanban--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-kanban--mazeng) | `test` | `a1dcadca90ccf18da54d415c87b47b77773730b9` | 1 |
| mazeng | [corp-v1-channel-delivery--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-delivery--mazeng) | `test` | `190de977a647446510375aff1bf3192beb41f444` | 1 |
| mazeng | [corp-v1-channel-releases--mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-releases--mazeng) | `test` | `eddc0f9d788c28134775a70e02606a0ded326933` | 1 |
| eshopv1 | [corp-v1-channel-general--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-general--eshopv1) | `test` | `e2d6b628dbdd409cb3901384419ae69db8de256b` | 1 |
| eshopv1 | [corp-v1-channel-scope--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-scope--eshopv1) | `test` | `0b185c233a10d004a47f80b5d408cab582bbe058` | 1 |
| eshopv1 | [corp-v1-channel-architecture--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-architecture--eshopv1) | `test` | `9fcab760c09263b4432bf8a4a8028a22e4ca5532` | 1 |
| eshopv1 | [corp-v1-channel-ui-ux--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-ui-ux--eshopv1) | `test` | `42e3f4bea7f526020f9abd66fd453104c4879935` | 1 |
| eshopv1 | [corp-v1-channel-kanban--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-kanban--eshopv1) | `test` | `4c96798bfe678c97c8f820000a424fbd50a74e53` | 1 |
| eshopv1 | [corp-v1-channel-delivery--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-delivery--eshopv1) | `test` | `5562b81fb3e8ad6fbc0d02039d58deaf64adbf53` | 1 |
| eshopv1 | [corp-v1-channel-releases--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-releases--eshopv1) | `test` | `77dbd2841337bd24b642b08329bcc338d2cb44f6` | 1 |
| aerosim | [corp-v1-channel-general-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-general-aerosim) | `test` | `e50dc8878ebe74b6c58601204508e4723bb7803d` | 0 |
| aerosim | [corp-v1-channel-scope-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-scope-aerosim) | `test` | `0b6cee38a12803b4a7ceefe824e6a510ea35fec3` | 1 |
| aerosim | [corp-v1-channel-architecture-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-architecture-aerosim) | `test` | `c2c379ea6875d1b2c91cd6d02da588b8cf06bcb6` | 1 |
| aerosim | [corp-v1-channel-ui-ux-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-ui-ux-aerosim) | `test` | `26d786b310e86c87d70542a680367c768474d28e` | 1 |
| aerosim | [corp-v1-channel-kanban-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-kanban-aerosim) | `test` | `e75f81d559996e9cab97092bf94db33a324830d1` | 0 |
| aerosim | [corp-v1-channel-delivery-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-delivery-aerosim) | `test` | `af697f5d1ef708c66db3ab62fd1fa9094b7735a2` | 0 |
| aerosim | [corp-v1-channel-releases-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-releases-aerosim) | `test` | `e85df7e82daa004bf0dc5a8db9ea09a99507583b` | 0 |
| mazeng | [corp-v1-channel-general-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-general-mazeng) | `test` | `12579704b8afad3af41b55b540ad21132e2ac299` | 1 |
| mazeng | [corp-v1-channel-scope-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-scope-mazeng) | `test` | `51ee9f4722a6ba5f9bbd13384ae8674690e070f9` | 1 |
| mazeng | [corp-v1-channel-architecture-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-architecture-mazeng) | `test` | `4c80704a0bd065accba49d523f6a83f51f8c1d2c` | 1 |
| mazeng | [corp-v1-channel-ui-ux-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-ui-ux-mazeng) | `test` | `547aabf245cd032dd82f95f3273c27753adbbd00` | 2 |
| mazeng | [corp-v1-channel-kanban-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-kanban-mazeng) | `test` | `a1dcadca90ccf18da54d415c87b47b77773730b9` | 1 |
| mazeng | [corp-v1-channel-delivery-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-delivery-mazeng) | `test` | `190de977a647446510375aff1bf3192beb41f444` | 1 |
| mazeng | [corp-v1-channel-releases-mazeng](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-releases-mazeng) | `test` | `eddc0f9d788c28134775a70e02606a0ded326933` | 1 |
| eshopv1 | [corp-v1-channel-general-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-general-eshopv1) | `test` | `e2d6b628dbdd409cb3901384419ae69db8de256b` | 1 |
| eshopv1 | [corp-v1-channel-scope-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-scope-eshopv1) | `test` | `0b185c233a10d004a47f80b5d408cab582bbe058` | 1 |
| eshopv1 | [corp-v1-channel-architecture-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-architecture-eshopv1) | `test` | `9fcab760c09263b4432bf8a4a8028a22e4ca5532` | 1 |
| eshopv1 | [corp-v1-channel-ui-ux-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-ui-ux-eshopv1) | `test` | `42e3f4bea7f526020f9abd66fd453104c4879935` | 1 |
| eshopv1 | [corp-v1-channel-kanban-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-kanban-eshopv1) | `test` | `4c96798bfe678c97c8f820000a424fbd50a74e53` | 1 |
| eshopv1 | [corp-v1-channel-delivery-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-delivery-eshopv1) | `test` | `5562b81fb3e8ad6fbc0d02039d58deaf64adbf53` | 1 |
| eshopv1 | [corp-v1-channel-releases-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-releases-eshopv1) | `test` | `77dbd2841337bd24b642b08329bcc338d2cb44f6` | 1 |
## Coverage
+19
View File
@@ -0,0 +1,19 @@
---
title: "Andrius"
description: "Identify Andrius's AeroSim project membership and verified access state."
---
# Andrius
| Field | Value |
|---|---|
| Status | Active |
| Discord | `<@204689314796273674>` — `whyt6249` / Andrius |
| Governance roles | AeroSim human team member |
| Team | [AeroSim Team](/teams/aerosim/) |
| Active projects | [AeroSim](/projects/aerosim/) |
| Gitea | Pending a verified username or account |
Andrius has verified effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access to the AeroSim General channel. Gitea searches did not establish an unambiguous account mapping, so membership in `aerosim-maintainers` and `aerosim-skill-maintainers` remains pending.
The membership alignment was approved by RootAtSkic (`discord:1518725627845283888`) in AeroSim General message `1543962382978514964` on 2026-08-31.
+19
View File
@@ -0,0 +1,19 @@
---
title: "Dovydas"
description: "Identify Dovydas's AeroSim project membership and verified access state."
---
# Dovydas
| Field | Value |
|---|---|
| Status | Active |
| Discord | `<@1543952051212656684>` — `dovydaszelenkevicius` / Dovydas |
| Governance roles | AeroSim human team member |
| Team | [AeroSim Team](/teams/aerosim/) |
| Active projects | [AeroSim](/projects/aerosim/) |
| Gitea | Pending a verified username or account |
Dovydas has verified effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access to the AeroSim General channel. No matching Gitea account was resolved, so membership in `aerosim-maintainers` and `aerosim-skill-maintainers` remains pending.
The membership alignment was approved by RootAtSkic (`discord:1518725627845283888`) in AeroSim General message `1543962382978514964` on 2026-08-31.
+1 -1
View File
@@ -15,6 +15,6 @@ sidebar_position: 5
| 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`.
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.
+20
View File
@@ -0,0 +1,20 @@
---
title: Friday Jr at SKIC
sidebar_position: 3
---
# Friday Jr at SKIC
| Field | Value |
|---|---|
| Status | Discord and team assignment complete; Gitea account activation pending |
| Discord | `<@1542987400358404268>` — `friday-jr-at-skic-hermes` |
| Role | Board-support and all-project code agent; not a human member, owner, approver, or Board decision-maker |
| Projects | 3D Architecture Wizzard; AeroSim; E-Shop v1; Maze Next Gen; DPVP Discord workspace |
| Gitea | `friday-at-skic` (user ID `92`) — team memberships verified; account reports inactive and its token receives HTTP `403` |
The Discord identity holds the `friday-jr-v1-hermes` administrator role. Fresh effective-permission calculation verified `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` in `corp-v1-board` and every lifecycle channel across all five project categories.
The Gitea account is assigned through the Corp portal code-agent team and both project/skill teams for 3D Architecture Wizzard, AeroSim, DPVP, E-Shop v1, and Maze Next Gen. Those eleven teams currently cover one governance repository, twelve project-organization repositories, and fifty-six project-skill repositories. The new DPVP teams contain Friday but currently cover no repositories because DPVP repository provisioning is still pending. A Gitea administrator must activate `friday-at-skic` before the account can use its own API token or sign in.
RootAtSkic (`discord:1518725627845283888`) approved the onboarding in Board message `1545758343489130598` on 2026-09-05. The approval grants operational access only and does not alter the seven-person human Board roster.
+19
View File
@@ -0,0 +1,19 @@
---
title: "Giedrius K"
description: "Identify Giedrius K's AeroSim project membership and verified access state."
---
# Giedrius K
| Field | Value |
|---|---|
| Status | Active |
| Discord | `<@1543940246071410706>` — `giedriusk_62552` / Giedrius K |
| Governance roles | AeroSim human team member |
| Team | [AeroSim Team](/teams/aerosim/) |
| Active projects | [AeroSim](/projects/aerosim/) |
| Gitea | Pending a verified username or account |
Giedrius K has verified effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access to the AeroSim General channel. No matching Gitea account was resolved, so membership in `aerosim-maintainers` and `aerosim-skill-maintainers` remains pending.
The membership alignment was approved by RootAtSkic (`discord:1518725627845283888`) in AeroSim General message `1543962382978514964` on 2026-08-31.
+7 -2
View File
@@ -9,12 +9,17 @@ sidebar_position: 1
| Member | Status | Roles | Teams | Active projects |
|---|---|---|---|---:|
| [RootAtSkic](/members/rootatskic/) | Active | AeroSim and Maze Next Gen sponsor and lead | AeroSim Team; Maze Next Gen Team | 2 |
| [Jarvis at SKIC](/members/jarvis-at-skic/) | Active | AeroSim and Maze Next Gen technical member and code agent | AeroSim Team; Maze Next Gen Team | 2 |
| [Jarvis at SKIC](/members/jarvis-at-skic/) | Active | Board member; executing code agent; all-project technical member | AeroSim; Maze Next Gen; E-Shop v1; 3D Architecture Wizzard; DPVP | 5 |
| [Friday Jr at SKIC](/members/friday-at-skic/) | Access provisioned; Gitea activation pending | Board-support and all-project code agent; no human decision authority | 3D Architecture Wizzard; AeroSim; E-Shop v1; Maze Next Gen; DPVP Discord workspace | 5 |
| [Panther Skeleton](/members/panther-skeleton/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
| [MartynasP](/members/martynasp/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
| [MartynasP](/members/martynasp/) | Active | Board member; AeroSim primary Scope owner | 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 |
| [Jenny](/members/jenny/) | Active | Board member; AeroSim and Maze Next Gen member | AeroSim Team; Maze Next Gen Team | 2 |
| [Piotras](/members/piotras/) | Active | Board member; AeroSim and Maze Next Gen member | AeroSim Team; Maze Next Gen Team | 2 |
| [Andrius](/members/andrius/) | Active | AeroSim member | AeroSim Team | 1 |
| [Dovydas](/members/dovydas/) | Active | AeroSim member | AeroSim Team | 1 |
| [Giedrius K](/members/giedrius-k/) | Active | AeroSim member | AeroSim Team | 1 |
| [Jone Tamulaite - Nong](/members/jone-tamulaite-nong/) | Offboarded from AeroSim | Former AeroSim Scope owner | None | 0 |
Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.
+8 -5
View File
@@ -8,9 +8,12 @@ sidebar_position: 2
| Field | Value |
|---|---|
| Status | Active |
| Governance roles | AeroSim, Maze Next Gen, and E-Shop v1 technical member and executing code agent |
| Teams | [AeroSim Team](/teams/aerosim/); [Maze Next Gen Team](/teams/mazeng/); [E-Shop v1 Team](/teams/eshopv1/) |
| Projects | [AeroSim](/projects/aerosim/); [Maze Next Gen](/projects/mazeng/); [E-Shop v1](/projects/eshopv1/) |
| Gitea | `jarvis-at-skic` — verified |
| Discord | `<@1526860732917088266>` — `jarvis-jr-at-skic-hermes` |
| Governance roles | Corp v1 Board member and executing code agent; technical member of every current project |
| Teams | [AeroSim](/teams/aerosim/); [Maze Next Gen](/teams/mazeng/); [E-Shop v1](/teams/eshopv1/); [3D Architecture Wizzard](/teams/3darch/); [DPVP](/teams/dpvp/) |
| Projects | [AeroSim](/projects/aerosim/); [Maze Next Gen](/projects/mazeng/); [E-Shop v1](/projects/eshopv1/); [3D Architecture Wizzard](/projects/3darch/); [DPVP](/projects/dpvp/) |
| Gitea | `jarvis-at-skic` (user ID `24`) — active and verified in all ten project/skills teams |
The executing Hermes identity has verified membership in both AeroSim, Maze Next Gen, and E-Shop v1 Gitea organization teams. It also has verified read/history/post/pin behavior across all seven E-Shop v1 Discord channels as bot `1526860732917088266`.
RootAtSkic approved Jarvis's Board and all-project onboarding in Board message `1545759332845490208` on 2026-09-05. Effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access is verified for `corp-v1-board` and all 35 lifecycle channels through the bot's administrator role. Gitea team membership is verified in each project's project and skills/code-agent organization; all teams include all current and future organization repositories.
Jarvis participates as the Board's executing code agent. Human Board approval remains required for approval-gated governance decisions; Jarvis does not approve its own execution.
+19
View File
@@ -0,0 +1,19 @@
---
title: "Jone Tamulaite - Nong"
description: "Record Jone Tamulaite - Nong's former AeroSim project membership and offboarding state."
---
# Jone Tamulaite - Nong
| Field | Value |
|---|---|
| Status | Offboarded from AeroSim on 2026-09-28 |
| Discord | `<@1067100220321714278>` — `jtamul` / Jone Tamulaite - Nong |
| Governance roles | Former AeroSim human team member and primary Scope owner |
| Team | None |
| Active projects | None |
| Gitea | No verified AeroSim account mapping; no team membership existed to revoke |
RootAtSkic recorded Jone Tamulaite - Nong's departure from AeroSim in Scope message `1554069052773900391` on 2026-09-28. MartynasP (`discord:773109855497093191`) succeeded her as primary Scope owner. Jone never had a verified Gitea mapping or membership in `aerosim-maintainers` or `aerosim-skill-maintainers`; Discord project-access removal remains subject to fresh remote verification.
The original membership alignment was approved by RootAtSkic (`discord:1518725627845283888`) in AeroSim General message `1543962382978514964` on 2026-08-31 and is preserved as historical evidence.
+2 -2
View File
@@ -9,9 +9,9 @@ description: "Identify Linas's Corp v1 Board and AeroSim responsibilities and ve
|---|---|
| Status | Active |
| Discord | `<@1483820991720329227>` — `linas_02251` / Linas |
| Governance roles | Corp v1 Board member; AeroSim human team member |
| Governance roles | Corp v1 Board member; AeroSim human team member; 3D Architecture Wizzard team lead |
| Gitea | `linas` — assigned; login activation pending |
Linas has verified Discord access to the Board and AeroSim channels and is assigned to both AeroSim Gitea organization teams.
Linas has verified Discord access to the Board and AeroSim channels and is assigned to both AeroSim Gitea organization teams and both 3D Architecture Wizzard teams. The `linas` account remains inactive, so effective 3D Architecture Wizzard Gitea access is pending activation.
The membership change was approved by RootAtSkic (`discord:1518725627845283888`) in Board message `1538808717301252116` on 2026-08-17.
+2 -2
View File
@@ -10,9 +10,9 @@ sidebar_position: 4
|---|---|
| Status | Active |
| Discord | `<@773109855497093191>` — `w4rl0ck_21` / MartynasP |
| Governance roles | Corp v1 Board member; AeroSim human team member |
| Governance roles | Corp v1 Board member; AeroSim human team member; primary AeroSim Scope owner |
| 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`.
RootAtSkic assigned MartynasP as AeroSim's primary Scope owner in Scope message `1554069052773900391` on 2026-09-28, succeeding Jone Tamulaite - Nong. This authority covers routine Epic and Feature lifecycle, priority, outcome, and `Approved for Solution` decisions under the AeroSim Scope contract. MartynasP's verified Gitea identity already belongs to both `aerosim-maintainers` and `aerosim-skill-maintainers`; fresh effective Discord access verification across the current eight-channel topology remains part of transition closure. Board authority continues to cover project kickoff, project closure, and approval of changes to `corp-v1-main`.
+1 -1
View File
@@ -15,6 +15,6 @@ sidebar_position: 3
| 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`.
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.
+1 -1
View File
@@ -17,7 +17,7 @@ This repository is the authoritative governance workspace for starting, governin
| [Projects](/projects/) | Portfolio status, ownership, lifecycle, and outcomes |
| [Teams](/teams/) | Team mandates, responsibilities, and project assignments |
| [Members](/members/) | Member identity, roles, and team membership |
| [Board](/board/) | The only members authorized to approve project kickoff, project closure, and `corp-v1--main` changes |
| [Board](/board/) | The only members authorized to approve project kickoff, project closure, and `corp-v1-main` changes |
## Operating principle
+88
View File
@@ -0,0 +1,88 @@
---
title: 3D Architecture Wizzard
sidebar_position: 4
---
# 3D Architecture Wizzard
| Field | Value |
|---|---|
| Code | `3darch` |
| Status | Active — lead activation pending |
| Started | 2026-08-31 |
| Sponsor | RootAtSkic |
| Accountable lead | Linas |
| Initial members | Linas; `jarvis-at-skic` / Hermes executing code agent |
| Operational code agent | `friday-at-skic` / Friday Jr; Gitea activation pending |
| Team | [3D Architecture Wizzard Team](/teams/3darch/) |
| Visibility | Public |
## Purpose
Create an interactive 3D application for exploring, designing, and communicating software and system architecture.
## Initial deliverable
A browser-based proof of concept that visualizes one architecture model in navigable 3D.
## Resources
- Project organization: [corp-v1-3darch](https://gitea.lego-cloud.eu/corp-v1-3darch)
- Skills organization: [corp-v1-3darch-skills-code-agent](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent)
- [Application repository](https://gitea.lego-cloud.eu/corp-v1-3darch/corp-v1-3darch) — `test` at `847c8291f100547ec9104743ab7d0d8761a5ec20`
- [Documentation repository](https://gitea.lego-cloud.eu/corp-v1-3darch/corp-v1-3darch-documentation) — `test` at `73cf70f0f333c187b28821fb76a44c779bdfbbdb`
- [Published documentation](https://pages.apps.lego-cloud.eu/corp-v1-3darch/corp-v1-3darch-documentation/)
- Global [Draw.io](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/drawio-main) and [glossary governance](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-glossary) references.
## Discord
Dedicated category `corp-v1-3darch` (`1543925242832101387`) contains exactly seven channels in lifecycle order:
- `corp-v1-3darch-general` — `1543925245755392051`
- `corp-v1-3darch-scope` — `1543925247361814568`
- `corp-v1-3darch-architecture` — `1543925248917770251`
- `corp-v1-3darch-ui-ux` — `1543925251191349260`
- `corp-v1-3darch-kanban` — `1543925252474798100`
- `corp-v1-3darch-delivery` — `1543925253502406749`
- `corp-v1-3darch-releases` — `1543925255523803146`
Hermes bot `1526860732917088266` posted purpose guidance in every channel, pinned the general introduction, and pinned the mapped project-skill guidance in every channel. No project scheduler job exists.
## Adopted project skills
All fourteen repositories are public, use default branch `test`, retain source history and assets, record immutable central source commits, and are assigned to the skills team:
- [`development-branching-strategy-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/development-branching-strategy-3darch) — source `test` / `636aba2b9e0957705fc874f07b310a4be9916f1c`, adopted `d0653755bda8104213e1e5aa3ce293a4a99ee8b3`
- [`development-gitops-argo-cd-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/development-gitops-argo-cd-3darch) — source `test` / `510b2bb590118362804d6036cbbf37db72dc21d0`, adopted `f4dd556573380363129bc9843b71d2630f2db393`
- [`development-monorepo-pnpm-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/development-monorepo-pnpm-3darch) — source `test` / `ff69bcca2fb3b673297230710a74c70410fd1996`, adopted `d6c800285f3393dd653350b6b7e3923e9d4c03e8`
- [`development-scripts-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/development-scripts-3darch) — source `test` / `5960d5e74713e6b95a403962f479b2b97cb76286`, adopted `ffdb143782833225fa3519e0108256e36c221e16`
- [`devsecops-ci-cd-gitea-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/devsecops-ci-cd-gitea-3darch) — source `test` / `8f46c3faa5ba074b8a48971b87365e0d3e2a4c40`, adopted `2fa1db97207685555f7a03cf26765db89d10cf6f`
- [`documentation-docusaurus-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/documentation-docusaurus-3darch) — source `test` / `f810f8c92005e5d55b08700b67fd34a37be435bc`, adopted `aaa49271748024b4ca97a015fb33a1847d5287ec`
- [`template-engine-copier-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/template-engine-copier-3darch) — source `test` / `97991021fff9e1f73202a82d29eea496ea0eb7aa`, adopted `73e4b53ee916269fe3c5d481e0d05bab0176711e`
- [`corp-v1-channel-general-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-general-3darch) — source `test` / `a5e79c24dd4ec1fa0d1a3258ecc184d9808daa62`, adopted `1fff9bf1c9fbfe2693601a0e46c7de4c82c50298`
- [`corp-v1-channel-scope-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-scope-3darch) — source `test` / `1916761e471535356bff38e2239aeb4d8fcd232d`, adopted `83d98aed66ac569ea8edfb18c9da4548942c0f1a`
- [`corp-v1-channel-architecture-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-architecture-3darch) — source `test` / `c7620c804a0de210f35fc829a38a53e44d40bfd8`, adopted `31c62cedcc89f6b9f2ebba5a2c76ca4ae3111e6e`
- [`corp-v1-channel-ui-ux-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-ui-ux-3darch) — source `test` / `de8c40cf43e08a63ca0be38a4b4404fbe2427885`, adopted `7a5dd48846ffce24be9c2541f00c7022faa56975`
- [`corp-v1-channel-kanban-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-kanban-3darch) — source `test` / `87a50a926a7256201ce1771aad7764898f24ff60`, adopted `8c1e7fd3a749993f477566c249b8ba9111f5705c`
- [`corp-v1-channel-delivery-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-delivery-3darch) — source `test` / `20cb78ce0942b35fe6528399c22764fbfb4cf06a`, adopted `2945874b0475901facef3bf6b4c36a845975ccc3`
- [`corp-v1-channel-releases-3darch`](https://gitea.lego-cloud.eu/corp-v1-3darch-skills-code-agent/corp-v1-channel-releases-3darch) — source `test` / `94d147880f6c957967d6612cbd846f9a2f2f6c00`, adopted `ced7e30deb06aa933d4a10cc232ecc05d700f274`
## Verification
- Application exact-head Actions: `1621` (success) at `847c8291f100547ec9104743ab7d0d8761a5ec20`.
- Documentation exact-head Actions: `1619` (success) at `73cf70f0f333c187b28821fb76a44c779bdfbbdb`.
- Documentation page body was read back through the Gondor operator path with the project title and initial-deliverable markers.
- Project team `3darch-maintainers` (`39`) covers both project repositories.
- Skills team `3darch-skill-maintainers` (`40`) covers all fourteen project-skill repositories.
- Jarvis (`jarvis-at-skic`, user ID `24`) is verified in both teams; Discord view, send, and history access is verified across all seven project channels.
- Gitea account `linas` is assigned to both teams, but its account remains inactive; effective human Gitea access is not claimed.
- Both required non-secret Harbor variables are configured. The organization secret name is present; its value was never requested or accessed.
- Board portal kickoff record was published and verified by exact-head Actions and deployed body readback.
## Outstanding gate
Linas must activate/sign in to Gitea account `linas`; team membership is already assigned.
## Approval
RootAtSkic (`discord:1518725627845283888`) requested setup in Board message `1543918340882436166` and approved the complete proposal in the same Board session, retaining the spelling **3D Architecture Wizzard**.
+40 -23
View File
@@ -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; Linas; Jenny; Piotras; `jarvis-at-skic` / Hermes code agent |
| Team members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; Piotras; Andrius; Dovydas; Giedrius K; `jarvis-at-skic` / Hermes code agent; `friday-at-skic` / Friday code agent |
| Team | [AeroSim Team](/teams/aerosim/) |
## Purpose
@@ -48,10 +48,24 @@ A playable MVP covering a light trainer, commercial airliner, and fighter-style
- Project organization: [corp-v1-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim)
- Skills organization: [corp-v1-aerosim-skills-code-agent](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent)
- [Application repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim) — `test` at `14b5c0e8f25215d8bb4f41edcc0cdff4a87c342c`
- [Documentation repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation) — `test` at `5f674525f6c8b5ce29fe2653350c6188fb97ea01`
- [Application repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim) — `test` at `09628fbb828380fbe159be7530da26f4bbf02129`
- [Documentation repository](https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation) — `test` at `d8a45594c33efc3acbd1523955d4f235facc9a1f`
- [Published documentation](https://pages.apps.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation/) — protected by the existing Keycloak access layer
## Delivery progress checkpoint — 2026-09-07
Release `1.0.0` contains 114 Tasks. Progress is reported by lifecycle checkpoint rather than collapsing implementation and release into one percentage.
| Measure | Progress | Meaning |
|---|---:|---|
| Canonical `ToBeReleased` | 49 / 114 (43.0%) | Canonical records place the Tasks in Waves 1–8 and 12–14 at the release-handoff state. This is not a release. |
| Repository-verified implementation pending reconciliation | 6 / 114 (5.3%) | `TASK-0048`, `TASK-0061`, `TASK-0065`, `TASK-0077`, `TASK-0083`, and `TASK-0111` are merged into the validated current application integration head, while their canonical records remain `InProgress`. This repository checkpoint does not replace canonical reconciliation. |
| Canonical `InProgress` | 7 / 114 (6.1%) | Wave 15 Tasks are claimed as one Delivery ownership unit and remain under implementation. |
| Canonical `ReadyForDelivery` | 58 / 114 (50.9%) | Unfinished Tasks in Waves 9–11 and 16–30 remain ready but unclaimed while Wave 15 is active. |
| Released | 0 / 114 (0.0%) | No Release `1.0.0` artifact has been approved and released. `ToBeReleased` is not release authorization. |
Wave 15 is active, and 6 of its 7 Tasks are repository-verified through merged application PRs #85, #89, #90, #95, #96, and #97. The current application integration head is `09628fbb828380fbe159be7530da26f4bbf02129`; its integrated tasks `2718`–`2720` succeeded. `TASK-0078` remains canonical `InProgress`, and its implementation PR #92 is closed without merge, so Wave 16 remains unclaimed. The canonical Wave 15 claim remains at documentation `test` SHA `d8a45594c33efc3acbd1523955d4f235facc9a1f`, verified by PR #155 exact-head build task `2581` and integrated build task `2582`. The authoritative task-level lifecycle remains in the [AeroSim documentation](https://pages.apps.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim-documentation/); this Board record is a dated portfolio checkpoint, not a second task database.
## Discord
Exactly seven same-project channels exist in dedicated category `corp-v1-aerosim` (`1542627633123299359`), in lifecycle order:
@@ -68,12 +82,12 @@ Hermes bot `1526860732917088266` successfully read and posted project guidance.
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:
- General: `6fc9c6a1328e`, `0 * * * *`, skill `corp-v1-channel-general--aerosim`, target `1537227679374508132`
- Scope: `dd548489178e`, `10 * * * *`, skill `corp-v1-channel-scope--aerosim`, target `1537544173366943886`
- Architecture: `c236b1e9642e`, `15 * * * *`, skill `corp-v1-channel-architecture--aerosim`, target `1537227680590733383`
- Kanban: `73378876d226`, `20 * * * *`, skill `corp-v1-channel-kanban--aerosim`, target `1537548579856580739`
- Delivery: `fdb061087f2f`, `30 * * * *`, skill `corp-v1-channel-delivery--aerosim`, target `1537227683191197807`
- Releases: `9deaa76e0077`, `45 * * * *`, skill `corp-v1-channel-releases--aerosim`, target `1537388451501056081`
- General: `6fc9c6a1328e`, `0 * * * *`, skill `corp-v1-channel-general-aerosim`, target `1537227679374508132`
- Scope: `dd548489178e`, `10 * * * *`, skill `corp-v1-channel-scope-aerosim`, target `1537544173366943886`
- Architecture: `c236b1e9642e`, `15 * * * *`, skill `corp-v1-channel-architecture-aerosim`, target `1537227680590733383`
- Kanban: `73378876d226`, `20 * * * *`, skill `corp-v1-channel-kanban-aerosim`, target `1537548579856580739`
- Delivery: `fdb061087f2f`, `30 * * * *`, skill `corp-v1-channel-delivery-aerosim`, target `1537227683191197807`
- Releases: `9deaa76e0077`, `45 * * * *`, skill `corp-v1-channel-releases-aerosim`, target `1537388451501056081`
All six jobs are enabled, explicitly constrained to the complete six-channel AeroSim boundary, and restricted from cross-project inspection and approval-required, destructive, secret-bearing, or high-impact autonomous actions.
@@ -81,19 +95,19 @@ All six jobs are enabled, explicitly constrained to the complete six-channel Aer
All use default branch `test` and are primary for AeroSim work:
- `development-branching-strategy--aerosim`
- `development-gitops-argo-cd--aerosim`
- `development-monorepo-pnpm--aerosim`
- `development-scripts--aerosim`
- `devsecops-ci-cd-gitea--aerosim`
- `documentation-docusaurus--aerosim`
- `template-engine-copier--aerosim`
- `corp-v1-channel-general--aerosim`
- `corp-v1-channel-scope--aerosim`
- `corp-v1-channel-architecture--aerosim`
- `corp-v1-channel-kanban--aerosim`
- `corp-v1-channel-delivery--aerosim`
- `corp-v1-channel-releases--aerosim`
- `development-branching-strategy-aerosim`
- `development-gitops-argo-cd-aerosim`
- `development-monorepo-pnpm-aerosim`
- `development-scripts-aerosim`
- `devsecops-ci-cd-gitea-aerosim`
- `documentation-docusaurus-aerosim`
- `template-engine-copier-aerosim`
- `corp-v1-channel-general-aerosim`
- `corp-v1-channel-scope-aerosim`
- `corp-v1-channel-architecture-aerosim`
- `corp-v1-channel-kanban-aerosim`
- `corp-v1-channel-delivery-aerosim`
- `corp-v1-channel-releases-aerosim`
Each repository records the central source branch and commit in `ADOPTION.md`. Architecture and documentation work reference the global [`drawio-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/drawio-main) skill.
@@ -105,6 +119,9 @@ Each repository records the central source branch and commit in `ADOPTION.md`. A
- Application tests: four passed across web, API, and shared flight core.
- Application and documentation production builds: passed.
- Project-team access across four current project-organization repositories: verified for `jarvis-at-skic`, `root-at-skic`, `martynas-pazusis`, and `piotras`; pending verified Gitea identities for Panther Skeleton, Eduard, and Jenny.
- Jarvis Board/all-project onboarding was reverified on 2026-09-05: Discord view, send, and history access passes in all seven channels; Gitea team IDs `23` and `24` include `jarvis-at-skic` and all organization repositories.
- Andrius, Dovydas, and Giedrius K are recorded as AeroSim human team members from 2026-08-31. Effective General-channel view, send, and history access is verified; Gitea project-team and skills-team access remains pending verified account mappings.
- On 2026-09-28, RootAtSkic recorded Jone Tamulaite - Nong's departure from AeroSim and assigned MartynasP as the primary Scope owner. MartynasP was already an AeroSim member with verified membership in both AeroSim Gitea teams. Jone never had a verified Gitea mapping, so no Gitea team membership existed to revoke; Discord access removal requires fresh remote verification.
- Skills-team organization membership covers all fourteen current project-skill repositories for `piotras`: 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,4 +131,4 @@ 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, Eduard, and Jenny must provide or create their Gitea usernames before they can be added to `aerosim-maintainers` and `aerosim-skill-maintainers`. Piotras is mapped to Gitea account `piotras` and has verified membership in both teams, covering four current project repositories and fourteen project-skill repositories. Their Discord project access is already verified.
Panther Skeleton, Eduard, Jenny, Andrius, Dovydas, and Giedrius K must provide or create their Gitea usernames before they can be added to `aerosim-maintainers` and `aerosim-skill-maintainers`. Piotras is mapped to Gitea account `piotras` and has verified membership in both teams, covering four current project repositories and fourteen project-skill repositories. Their recorded Discord project access is already verified.
+60
View File
@@ -0,0 +1,60 @@
---
title: Debesijos paslaugų valdymo platforma
sidebar_position: 5
description: "Track the DPVP kickoff, team, access, resources, and remaining provisioning gates."
---
# Debesijos paslaugų valdymo platforma
| Field | Value |
|---|---|
| Code | `dpvp` |
| Status | Kickoff in progress — repositories, adopted skills, and deployed documentation pending |
| Started | 2026-09-02 |
| Sponsor and accountable lead | RootAtSkic |
| Members | RootAtSkic; Linas; `jarvis-at-skic` / Hermes executing code agent; `friday-at-skic` / Friday code agent |
| Team | [DPVP Team](/teams/dpvp/) |
| Visibility | Restricted |
## Purpose
Guide the VSSA Operator through governed cloud-service organization and project lifecycle management, with Jira as the system of record for originating, assigning, and approving organization and project changes.
## Initial deliverable
Deployed project documentation and an architecture baseline for the VSSA Operator organization/project onboarding journey, without a placeholder application.
## Discord
Dedicated category `corp-v1-dpvp` (`1544621887844388965`) contains exactly seven lifecycle channels:
1. `corp-v1-dpvp-general` — `1544621890994184224`
2. `corp-v1-dpvp-scope` — `1544621895159255040`
3. `corp-v1-dpvp-architecture` — `1544621899370340362`
4. `corp-v1-dpvp-ui-ux` — `1544621902142771250`
5. `corp-v1-dpvp-kanban` — `1544621905494016080`
6. `corp-v1-dpvp-delivery` — `1544621909176746005`
7. `corp-v1-dpvp-releases` — `1544621912385130556`
Jarvis (`discord:1526860732917088266`) has verified effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access in every channel through its administrator role. Purpose guidance exists in all seven channels, and the General introduction is pinned as message `1544622184582877245`.
## Gitea
- Project organization: [corp-v1-dpvp](https://gitea.lego-cloud.eu/corp-v1-dpvp) — private; created and verified 2026-09-05.
- Skills/code-agent organization: [corp-v1-dpvp-skills-code-agent](https://gitea.lego-cloud.eu/corp-v1-dpvp-skills-code-agent) — private; created and verified 2026-09-05.
- Project team: `dpvp-maintainers` (`45`) — includes all repositories; `jarvis-at-skic` verified.
- Skills team: `dpvp-skill-maintainers` (`47`) — includes all repositories; `jarvis-at-skic` verified.
- Friday's Gitea account `friday-at-skic` is verified in both teams. The teams currently cover no repositories, and Friday's account activation remains pending.
## Approval
RootAtSkic requested the DPVP kickoff in Board message `1544616064162463854`; the dedicated Discord workspace was subsequently provisioned. RootAtSkic approved Jarvis's Board and all-project membership in Board message `1545759332845490208` on 2026-09-05.
## Outstanding gates
1. Create and assign the two required DPVP project repositories.
2. Adopt and verify the fourteen project-scoped skill repositories.
3. Configure the approved non-secret Harbor variables and validate only the required secret name's presence.
4. Build, publish, and read back the DPVP documentation site.
5. Complete project documentation and application kickoff acceptance without creating a placeholder application.
6. Add RootAtSkic and Linas to both Gitea teams after confirming the intended team permissions and Linas account activation state.
+16 -15
View File
@@ -12,6 +12,7 @@ sidebar_position: 3
| Started | 2026-08-26 |
| Sponsor and accountable lead | RootAtSkic |
| Technical member | `jarvis-at-skic` / Hermes code agent |
| Additional code agent | `friday-at-skic` / Friday Jr; Gitea activation pending |
| Team | [E-Shop v1 Team](/teams/eshopv1/) |
## Purpose and initial deliverable
@@ -53,24 +54,24 @@ All repositories are private, use default branch `test`, retain complete source
| Adopted skill | Central source SHA | Adopted SHA |
|---|---|---|
| [development-branching-strategy--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-branching-strategy--eshopv1) | `636aba2b9e0957705fc874f07b310a4be9916f1c` | `6255c8811ca5bbf2607c4c36980a0347c3a5ee67` |
| [development-gitops-argo-cd--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-gitops-argo-cd--eshopv1) | `510b2bb590118362804d6036cbbf37db72dc21d0` | `add186a9910a915aee20124855440aa9dfdb4f9f` |
| [development-monorepo-pnpm--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-monorepo-pnpm--eshopv1) | `ff69bcca2fb3b673297230710a74c70410fd1996` | `489570b877af6b89f995a02646b161ddf79f85dd` |
| [development-scripts--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-scripts--eshopv1) | `5960d5e74713e6b95a403962f479b2b97cb76286` | `69c364ea595b0b1a35738847cca2d03f8cd14d56` |
| [devsecops-ci-cd-gitea--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/devsecops-ci-cd-gitea--eshopv1) | `8f46c3faa5ba074b8a48971b87365e0d3e2a4c40` | `5b66f8a0084743ce079da667e3c97b07febc6a20` |
| [documentation-docusaurus--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/documentation-docusaurus--eshopv1) | `f810f8c92005e5d55b08700b67fd34a37be435bc` | `c2f8d50d4ffd97c854f0cb06fadfa664c9947861` |
| [template-engine-copier--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/template-engine-copier--eshopv1) | `97991021fff9e1f73202a82d29eea496ea0eb7aa` | `6a38a58997eb278736648b163d4f3f89015acf16` |
| [corp-v1-channel-general--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-general--eshopv1) | `7137f18319b9716468485b68b99b4297a721c94f` | `e307890e65bf48280c0b798559c4925581ff1505` |
| [corp-v1-channel-scope--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-scope--eshopv1) | `729e7ff936ed99f7d1ee203defc02f3f1ce64085` | `8df61e824d6e28b53a26a63802d9c7ae45393896` |
| [corp-v1-channel-architecture--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-architecture--eshopv1) | `f9bef3bee6a59c74803e3aef5b26fdc61894f0ee` | `9c1cd5b238ebe53ed46d40985f70d57077a3c7f0` |
| [corp-v1-channel-ui-ux--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-ui-ux--eshopv1) | `2039d7e3f7ac3ec14064ead52c8a53ac233f519c` | `55d79260f8fdc72c547f4de928bb7effa5ca9c34` |
| [corp-v1-channel-kanban--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-kanban--eshopv1) | `73d8af5f18463ed55b510f1cc8a66e2f882b5552` | `fff4ace0c184c750e1e4d7ed0e7a806b78f8a075` |
| [corp-v1-channel-delivery--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-delivery--eshopv1) | `b629921b6f58c0f36de7d1f39a13ba14c25baab2` | `456297285484f4bfe2c43ba64e67e17af4edd89e` |
| [corp-v1-channel-releases--eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-releases--eshopv1) | `12891cf409378777eac72fbde9541b3c117e82aa` | `f2d2bfb78044dbc3cedc8bc998412e19234c78aa` |
| [development-branching-strategy-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-branching-strategy-eshopv1) | `636aba2b9e0957705fc874f07b310a4be9916f1c` | `6255c8811ca5bbf2607c4c36980a0347c3a5ee67` |
| [development-gitops-argo-cd-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-gitops-argo-cd-eshopv1) | `510b2bb590118362804d6036cbbf37db72dc21d0` | `add186a9910a915aee20124855440aa9dfdb4f9f` |
| [development-monorepo-pnpm-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-monorepo-pnpm-eshopv1) | `ff69bcca2fb3b673297230710a74c70410fd1996` | `489570b877af6b89f995a02646b161ddf79f85dd` |
| [development-scripts-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/development-scripts-eshopv1) | `5960d5e74713e6b95a403962f479b2b97cb76286` | `69c364ea595b0b1a35738847cca2d03f8cd14d56` |
| [devsecops-ci-cd-gitea-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/devsecops-ci-cd-gitea-eshopv1) | `8f46c3faa5ba074b8a48971b87365e0d3e2a4c40` | `5b66f8a0084743ce079da667e3c97b07febc6a20` |
| [documentation-docusaurus-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/documentation-docusaurus-eshopv1) | `f810f8c92005e5d55b08700b67fd34a37be435bc` | `c2f8d50d4ffd97c854f0cb06fadfa664c9947861` |
| [template-engine-copier-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/template-engine-copier-eshopv1) | `97991021fff9e1f73202a82d29eea496ea0eb7aa` | `6a38a58997eb278736648b163d4f3f89015acf16` |
| [corp-v1-channel-general-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-general-eshopv1) | `7137f18319b9716468485b68b99b4297a721c94f` | `e307890e65bf48280c0b798559c4925581ff1505` |
| [corp-v1-channel-scope-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-scope-eshopv1) | `729e7ff936ed99f7d1ee203defc02f3f1ce64085` | `8df61e824d6e28b53a26a63802d9c7ae45393896` |
| [corp-v1-channel-architecture-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-architecture-eshopv1) | `f9bef3bee6a59c74803e3aef5b26fdc61894f0ee` | `9c1cd5b238ebe53ed46d40985f70d57077a3c7f0` |
| [corp-v1-channel-ui-ux-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-ui-ux-eshopv1) | `2039d7e3f7ac3ec14064ead52c8a53ac233f519c` | `55d79260f8fdc72c547f4de928bb7effa5ca9c34` |
| [corp-v1-channel-kanban-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-kanban-eshopv1) | `73d8af5f18463ed55b510f1cc8a66e2f882b5552` | `fff4ace0c184c750e1e4d7ed0e7a806b78f8a075` |
| [corp-v1-channel-delivery-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-delivery-eshopv1) | `b629921b6f58c0f36de7d1f39a13ba14c25baab2` | `456297285484f4bfe2c43ba64e67e17af4edd89e` |
| [corp-v1-channel-releases-eshopv1](https://gitea.lego-cloud.eu/corp-v1-eshopv1-skills-code-agent/corp-v1-channel-releases-eshopv1) | `12891cf409378777eac72fbde9541b3c117e82aa` | `f2d2bfb78044dbc3cedc8bc998412e19234c78aa` |
## Access, automation, and Harbor
`e-shop-v1-team` exists independently in both organizations, includes all repositories, grants per-unit write access, and contains verified users `root-at-skic` and `jarvis-at-skic`.
`e-shop-v1-team` exists independently in both organizations, includes all repositories, grants per-unit write access, and contains verified users `root-at-skic` and `jarvis-at-skic`. Jarvis is verified through team IDs `35` and `36`, covering four project-organization repositories and fourteen project-skill repositories; Discord view, send, and history access passes across all seven lifecycle channels.
Scheduler job `d6505c6ac0da` is the single approved 30-minute General job. It uses frozen high-watermarks, scans only the seven E-Shop channels, attaches all fourteen adopted skills, delivers only to General, and pauses on the first human message. RootAtSkic explicitly renewed foreground continuation and requested that the job be returned to service in Board message `1542470702525980672` on 2026-08-27.
+2
View File
@@ -11,6 +11,8 @@ sidebar_position: 1
| [AeroSim](/projects/aerosim/) | Active — Harbor gated | RootAtSkic | RootAtSkic | [AeroSim Team](/teams/aerosim/) | 2026-08-12 | — |
| [Maze Next Gen](/projects/mazeng/) | Active — Harbor gated | RootAtSkic | RootAtSkic | [Maze Next Gen Team](/teams/mazeng/) | 2026-08-17 | — |
| [E-Shop v1](/projects/eshopv1/) | Active — application deployment gated | RootAtSkic | RootAtSkic | [E-Shop v1 Team](/teams/eshopv1/) | 2026-08-26 | — |
| [3D Architecture Wizzard](/projects/3darch/) | Active — lead activation pending | RootAtSkic | Linas | [3D Architecture Wizzard Team](/teams/3darch/) | 2026-08-31 | — |
| [Debesijos paslaugų valdymo platforma](/projects/dpvp/) | Kickoff in progress — repositories and documentation pending | RootAtSkic | RootAtSkic | [DPVP Team](/teams/dpvp/) | 2026-09-02 | — |
## Required project record
+21 -20
View File
@@ -12,6 +12,7 @@ sidebar_position: 2
| Started | 2026-08-17 |
| Sponsor and accountable lead | RootAtSkic |
| Initial technical member | `jarvis-at-skic` / Hermes code agent |
| Additional code agent | `friday-at-skic` / Friday Jr; Gitea activation pending |
| Human team members | RootAtSkic; Jenny; Piotras |
| Team | [Maze Next Gen Team](/teams/mazeng/) |
@@ -53,34 +54,34 @@ General introduction `1539019982682325132` and the recorded skill-guidance messa
All six are enabled, hourly, staggered, exact-targeted, limited to the six Maze channels, and attach the mapped adopted skill:
- General: `f5465bc1b05d`, `0 * * * *`, skill `corp-v1-channel-general--mazeng`, target `1539019955738116096`
- Scope: `ab278de9e046`, `10 * * * *`, skill `corp-v1-channel-scope--mazeng`, target `1539019959135633580`
- Architecture: `9c9e0206f05b`, `15 * * * *`, skill `corp-v1-channel-architecture--mazeng`, target `1539019963568758835`
- Kanban: `e8de02062193`, `20 * * * *`, skill `corp-v1-channel-kanban--mazeng`, target `1539019969323466883`
- Delivery: `11f63507301a`, `30 * * * *`, skill `corp-v1-channel-delivery--mazeng`, target `1539019973043683358`
- Releases: `f04ab31a499e`, `45 * * * *`, skill `corp-v1-channel-releases--mazeng`, target `1539019976977948694`
- General: `f5465bc1b05d`, `0 * * * *`, skill `corp-v1-channel-general-mazeng`, target `1539019955738116096`
- Scope: `ab278de9e046`, `10 * * * *`, skill `corp-v1-channel-scope-mazeng`, target `1539019959135633580`
- Architecture: `9c9e0206f05b`, `15 * * * *`, skill `corp-v1-channel-architecture-mazeng`, target `1539019963568758835`
- Kanban: `e8de02062193`, `20 * * * *`, skill `corp-v1-channel-kanban-mazeng`, target `1539019969323466883`
- Delivery: `11f63507301a`, `30 * * * *`, skill `corp-v1-channel-delivery-mazeng`, target `1539019973043683358`
- Releases: `f04ab31a499e`, `45 * * * *`, skill `corp-v1-channel-releases-mazeng`, target `1539019976977948694`
## Adopted project skills
- [`development-branching-strategy--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-branching-strategy--mazeng) — source `test` `636aba2b9e0957705fc874f07b310a4be9916f1c`; adopted `test` `c952824066f3e1440bdc1144097cef44b1f4b084`
- [`development-gitops-argo-cd--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-gitops-argo-cd--mazeng) — source `test` `510b2bb590118362804d6036cbbf37db72dc21d0`; adopted `test` `2faf48eeaef2e9f62dcc8903736d54cc4b7851e5`
- [`development-monorepo-pnpm--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-monorepo-pnpm--mazeng) — source `test` `ff69bcca2fb3b673297230710a74c70410fd1996`; adopted `test` `e55e354d33603c0d62a67a58352c0ed863884ceb`
- [`development-scripts--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-scripts--mazeng) — source `test` `5960d5e74713e6b95a403962f479b2b97cb76286`; adopted `test` `04df15a8739ba9ccbbbe21a0015322644aee2b91`
- [`devsecops-ci-cd-gitea--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/devsecops-ci-cd-gitea--mazeng) — source `test` `8f46c3faa5ba074b8a48971b87365e0d3e2a4c40`; adopted `test` `9b663f59eaff284248b9abc009a520dbf4b10919`
- [`documentation-docusaurus--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/documentation-docusaurus--mazeng) — source `test` `f810f8c92005e5d55b08700b67fd34a37be435bc`; adopted `test` `63ac1e8c8a81516cb14b27615cce6970828e8f48`
- [`template-engine-copier--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/template-engine-copier--mazeng) — source `test` `97991021fff9e1f73202a82d29eea496ea0eb7aa`; adopted `test` `41ef4de05c27067b995167014c030744243cfa14`
- [`corp-v1-channel-general--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-general--mazeng) — source `test` `6d15b02f081f8adc534230a04d11d1ad3a74d40f`; adopted `test` `a60a30c63eeb7afb6cdf6d083d9a200e46a17590`
- [`corp-v1-channel-scope--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-scope--mazeng) — source `test` `b9f9148c7c0558f8125e6d0125520708cf56d05f`; adopted `test` `35fbe7936e90486883fa3f839c883a0c887a71d4`
- [`corp-v1-channel-architecture--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-architecture--mazeng) — source `test` `f29cf0e56b81ea16c7e760ad31690619a6196ce5`; adopted `test` `df20e7627cf0c7f8e3f7b6b293667199661d92ca`
- [`corp-v1-channel-kanban--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-kanban--mazeng) — source `test` `91ef9af76b7f00f6addc9a0f48d162bb0e7d511b`; adopted `test` `cecf06d9f5a6a886a183d8f36867cf8de933f218`
- [`corp-v1-channel-delivery--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-delivery--mazeng) — source `test` `b201a502ce67f2e8e1fb72d81ab54970648d90f6`; adopted `test` `0b022af9b776fe799afd8e01901dd5ea6a90e1f8`
- [`corp-v1-channel-releases--mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-releases--mazeng) — source `test` `50c933b0553acc83799b38aa8d1077313c7b7f79`; adopted `test` `47433ff46f9f4b2bf9c0e5086e74e4ee7cb9b632`
- [`development-branching-strategy-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-branching-strategy-mazeng) — source `test` `636aba2b9e0957705fc874f07b310a4be9916f1c`; adopted `test` `c952824066f3e1440bdc1144097cef44b1f4b084`
- [`development-gitops-argo-cd-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-gitops-argo-cd-mazeng) — source `test` `510b2bb590118362804d6036cbbf37db72dc21d0`; adopted `test` `2faf48eeaef2e9f62dcc8903736d54cc4b7851e5`
- [`development-monorepo-pnpm-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-monorepo-pnpm-mazeng) — source `test` `ff69bcca2fb3b673297230710a74c70410fd1996`; adopted `test` `e55e354d33603c0d62a67a58352c0ed863884ceb`
- [`development-scripts-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/development-scripts-mazeng) — source `test` `5960d5e74713e6b95a403962f479b2b97cb76286`; adopted `test` `04df15a8739ba9ccbbbe21a0015322644aee2b91`
- [`devsecops-ci-cd-gitea-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/devsecops-ci-cd-gitea-mazeng) — source `test` `8f46c3faa5ba074b8a48971b87365e0d3e2a4c40`; adopted `test` `9b663f59eaff284248b9abc009a520dbf4b10919`
- [`documentation-docusaurus-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/documentation-docusaurus-mazeng) — source `test` `f810f8c92005e5d55b08700b67fd34a37be435bc`; adopted `test` `63ac1e8c8a81516cb14b27615cce6970828e8f48`
- [`template-engine-copier-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/template-engine-copier-mazeng) — source `test` `97991021fff9e1f73202a82d29eea496ea0eb7aa`; adopted `test` `41ef4de05c27067b995167014c030744243cfa14`
- [`corp-v1-channel-general-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-general-mazeng) — source `test` `6d15b02f081f8adc534230a04d11d1ad3a74d40f`; adopted `test` `a60a30c63eeb7afb6cdf6d083d9a200e46a17590`
- [`corp-v1-channel-scope-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-scope-mazeng) — source `test` `b9f9148c7c0558f8125e6d0125520708cf56d05f`; adopted `test` `35fbe7936e90486883fa3f839c883a0c887a71d4`
- [`corp-v1-channel-architecture-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-architecture-mazeng) — source `test` `f29cf0e56b81ea16c7e760ad31690619a6196ce5`; adopted `test` `df20e7627cf0c7f8e3f7b6b293667199661d92ca`
- [`corp-v1-channel-kanban-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-kanban-mazeng) — source `test` `91ef9af76b7f00f6addc9a0f48d162bb0e7d511b`; adopted `test` `cecf06d9f5a6a886a183d8f36867cf8de933f218`
- [`corp-v1-channel-delivery-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-delivery-mazeng) — source `test` `b201a502ce67f2e8e1fb72d81ab54970648d90f6`; adopted `test` `0b022af9b776fe799afd8e01901dd5ea6a90e1f8`
- [`corp-v1-channel-releases-mazeng`](https://gitea.lego-cloud.eu/corp-v1-mazeng-skills-code-agent/corp-v1-channel-releases-mazeng) — source `test` `50c933b0553acc83799b38aa8d1077313c7b7f79`; adopted `test` `47433ff46f9f4b2bf9c0e5086e74e4ee7cb9b632`
Global diagram source: [`drawio-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/drawio-main); no Maze copy exists. All thirteen adopted repositories have default branch `test`, preserved source provenance, project-scoped peer links, verified team access, and no Actions workflow configured.
## Access and Harbor
Team identifier `maze-next-gen-team` exists in both private organizations, includes all repositories, grants per-unit write access, and contains verified members `root-at-skic`, `jarvis-at-skic`, and `piotras`. Piotras's membership is verified across two project repositories and fourteen project-skill repositories. Jenny has verified Discord project access; her Gitea membership remains pending a verified account mapping.
Team identifier `maze-next-gen-team` exists in both private organizations, includes all repositories, grants per-unit write access, and contains verified members `root-at-skic`, `jarvis-at-skic`, and `piotras`. Jarvis's membership is verified through team IDs `29` and `31`, covering two project repositories and fourteen project-skill repositories; Discord view, send, and history access passes across all seven lifecycle channels. Piotras's membership is also verified. Jenny has verified Discord project access; her Gitea membership remains pending a verified account mapping.
Verified variables on `corp-v1-mazeng`:
+33
View File
@@ -0,0 +1,33 @@
---
title: 3D Architecture Wizzard Team
sidebar_position: 4
---
# 3D Architecture Wizzard Team
| Field | Value |
|---|---|
| Status | Active — Gitea lead activation pending |
| Lead | Linas |
| Members | Linas; `jarvis-at-skic` / Hermes executing code agent; `friday-at-skic` / Friday code agent |
| Assigned project | [3D Architecture Wizzard](/projects/3darch/) |
## Mandate
Deliver the 3D Architecture Wizzard browser experience, its documentation, and the project-specific engineering practices required to operate it.
## Responsibilities
- Product and delivery coordination.
- Interactive 3D architecture visualization and model contracts.
- Application, CI/CD, GitOps, and documentation delivery.
- Adoption and maintenance of the fourteen mandatory project skills.
## Access
- Discord: `<@1483820991720329227>` — `linas_02251`; seven project channels provisioned and verified.
- Gitea: `linas` (user ID `21`) is assigned to both project teams, covering two project repositories and fourteen skill repositories.
- Gitea: `jarvis-at-skic` (user ID `24`) is verified in `3darch-maintainers` (`39`) and `3darch-skill-maintainers` (`40`); both teams include all organization repositories.
- Discord: Jarvis has verified view, send, and history access across all seven lifecycle channels.
- Gitea reports the account inactive, so effective login/write access remains pending activation.
- Friday's Gitea account `friday-at-skic` is assigned to `3darch-maintainers` and `3darch-skill-maintainers`, covering two project repositories and fourteen skill repositories. The account itself remains inactive, so operational login/API use is pending administrator activation.
+5 -1
View File
@@ -9,7 +9,7 @@ sidebar_position: 1
|---|---|
| Status | Active |
| Lead | RootAtSkic |
| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; Piotras; `jarvis-at-skic` / Hermes code agent |
| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; Piotras; Andrius; Dovydas; Giedrius K; `jarvis-at-skic` / Hermes code agent; `friday-at-skic` / Friday code agent |
| Assigned project | [AeroSim](/projects/aerosim/) |
## Mandate
@@ -28,8 +28,12 @@ Deliver the AeroSim browser flight-simulation platform, its documentation, and t
- `aerosim-maintainers` in `corp-v1-aerosim` covers four current project-organization repositories.
- `aerosim-skill-maintainers` in `corp-v1-aerosim-skills-code-agent` covers all fourteen adopted skill repositories.
- `jarvis-at-skic`, `root-at-skic`, `martynas-pazusis`, and `piotras` membership and effective repository assignments are verified in both teams.
- Jarvis's all-project onboarding was reverified on 2026-09-05: team IDs `23` and `24` include `jarvis-at-skic`, while Discord view, send, and history access passes across all seven lifecycle channels.
- `friday-at-skic` membership is verified in both teams, covering four project repositories and fourteen skill repositories. The account reports inactive, so its own login/API use remains pending administrator activation.
- Piotras maps to Gitea account `piotras` and has verified membership in `aerosim-maintainers` and `aerosim-skill-maintainers`, covering four current project repositories and fourteen project-skill repositories.
- Panther Skeleton, Eduard, and Jenny have verified Discord identities and project access, but no matching Gitea accounts could be resolved. Their Gitea team access remains pending verified usernames or account creation.
- Andrius, Dovydas, and Giedrius K have verified effective Discord access to the AeroSim General channel. Their Gitea team access remains pending verified usernames or account creation; no account mapping was inferred from names alone.
- Jone Tamulaite - Nong left AeroSim on 2026-09-28. MartynasP succeeded her as primary Scope owner and retains the already verified `aerosim-maintainers` and `aerosim-skill-maintainers` memberships.
## Communication
+30
View File
@@ -0,0 +1,30 @@
---
title: DPVP Team
sidebar_position: 5
description: "Identify the DPVP team, mandate, verified access, and remaining kickoff gates."
---
# DPVP Team
| Field | Value |
|---|---|
| Status | Kickoff in progress |
| Lead | RootAtSkic |
| Members | RootAtSkic; Linas; `jarvis-at-skic` / Hermes executing code agent; `friday-at-skic` / Friday code agent |
| Assigned project | [Debesijos paslaugų valdymo platforma](/projects/dpvp/) |
## Mandate
Deliver the governed DPVP experience for VSSA Operator organization and project onboarding, its architecture baseline, documentation, and project-scoped engineering practices.
## Access
- Discord: all seven DPVP lifecycle channels exist; Jarvis view, send, and history permissions are verified.
- Gitea project team: `dpvp-maintainers` (`45`) in `corp-v1-dpvp`; includes all repositories and contains verified user `jarvis-at-skic`.
- Gitea skills team: `dpvp-skill-maintainers` (`47`) in `corp-v1-dpvp-skills-code-agent`; includes all repositories and contains verified user `jarvis-at-skic`.
- Both teams also contain verified Gitea user `friday-at-skic`; they currently cover no repositories, and Friday's account remains inactive pending administrator activation.
- RootAtSkic and Linas Gitea team assignment remains part of the incomplete DPVP kickoff; this membership change did not alter their access.
## Communication
Use the exact lifecycle order: General, Scope, Architecture, UI/UX, Kanban, Delivery, and Releases. Jira originates, assigns, and approves organization/project changes; the portal guides the VSSA Operator and records verified outcomes.
+2 -2
View File
@@ -9,7 +9,7 @@ sidebar_position: 3
|---|---|
| Status | Active |
| Lead | RootAtSkic |
| Members | RootAtSkic; `jarvis-at-skic` / Hermes code agent |
| Members | RootAtSkic; `jarvis-at-skic` / Hermes code agent; `friday-at-skic` / Friday code agent |
| Assigned project | [E-Shop v1](/projects/eshopv1/) |
## Mandate
@@ -18,7 +18,7 @@ Deliver the governed E-Shop v1 toothbrush-commerce MVP, its source-evidence cata
## Gitea access
`e-shop-v1-team` exists independently in `corp-v1-eshopv1` and `corp-v1-eshopv1-skills-code-agent`. Both teams include all repositories, grant per-unit write access, and contain verified users `root-at-skic` and `jarvis-at-skic`.
`e-shop-v1-team` exists independently in `corp-v1-eshopv1` (team `35`) and `corp-v1-eshopv1-skills-code-agent` (team `36`). Both teams include all repositories and grant per-unit write access. Membership for `root-at-skic`, `jarvis-at-skic`, and `friday-at-skic` is verified. Jarvis's Discord view, send, and history access passes across all seven lifecycle channels. Friday's assignments cover four project repositories and fourteen skill repositories, but its inactive account still requires administrator activation before operational login/API use.
## Communication and autonomy
+5 -3
View File
@@ -8,8 +8,10 @@ sidebar_position: 1
| Team | Status | Lead | Members | Active projects |
|---|---|---|---:|---:|
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 8 | 1 |
| [Maze Next Gen Team](/teams/mazeng/) | Active | RootAtSkic | 4 | 1 |
| [E-Shop v1 Team](/teams/eshopv1/) | Active | RootAtSkic | 2 | 1 |
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 13 | 1 |
| [Maze Next Gen Team](/teams/mazeng/) | Active | RootAtSkic | 5 | 1 |
| [E-Shop v1 Team](/teams/eshopv1/) | Active | RootAtSkic | 3 | 1 |
| [3D Architecture Wizzard Team](/teams/3darch/) | Active — Gitea account activation pending | Linas | 3 | 1 |
| [DPVP Team](/teams/dpvp/) | Kickoff in progress | RootAtSkic | 4 | 1 |
A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.
+2 -2
View File
@@ -9,7 +9,7 @@ sidebar_position: 2
|---|---|
| Status | Active |
| Lead | RootAtSkic |
| Members | RootAtSkic; Jenny; Piotras; `jarvis-at-skic` / Hermes code agent |
| Members | RootAtSkic; Jenny; Piotras; `jarvis-at-skic` / Hermes code agent; `friday-at-skic` / Friday code agent |
| Assigned project | [Maze Next Gen](/projects/mazeng/) |
## Mandate
@@ -18,7 +18,7 @@ Deliver the Maze Next Gen multi-cloud inventory and visualization platform, docu
## Gitea access
`maze-next-gen-team` exists independently in `corp-v1-mazeng` and `corp-v1-mazeng-skills-code-agent`, includes all repositories, and contains `root-at-skic`, `jarvis-at-skic`, and `piotras`. Piotras's verified memberships cover two project repositories and fourteen project-skill repositories. Jenny has verified Discord access, but her Gitea team access remains pending a verified username or account creation; no identity was guessed.
`maze-next-gen-team` exists independently in `corp-v1-mazeng` (team `29`) and `corp-v1-mazeng-skills-code-agent` (team `31`), includes all repositories, and contains `root-at-skic`, `jarvis-at-skic`, `piotras`, and `friday-at-skic`. Jarvis's, Piotras's, and Friday's verified memberships each cover two project repositories and fourteen project-skill repositories; Jarvis's Discord view, send, and history access passes across all seven lifecycle channels. Friday's inactive Gitea account still requires administrator activation before operational login/API use. Jenny has verified Discord access, but her Gitea team access remains pending a verified username or account creation; no identity was guessed.
## Communication
+23
View File
@@ -0,0 +1,23 @@
---
title: "Ways of Working"
description: "Use the shared operating practices for participating safely and effectively in the Corp v1 pilot."
slug: /
sidebar_position: 1
---
# Ways of Working
Corp v1 is a governed AI-assisted delivery pilot. People set outcomes, authority, and constraints; Hermes helps turn those decisions into traceable designs, code, documentation, releases, and operated evidence.
Use this area to understand how to join the pilot, where work belongs, how decisions become delivery, and which evidence is required before something is called complete.
## Start here
1. Read [Onboarding](./onboarding) before contributing.
2. Find your project in the [project registry](/projects/).
3. Confirm your responsibilities in the [team](/teams/) and [member](/members/) registries.
4. Follow the [project lifecycle](/governance/project-lifecycle/) and the authority recorded for your project.
## Core principle
Keep conversation, decisions, implementation, deployment, and runtime proof connected—but do not treat them as the same thing. An approved idea is not implemented work; a merged change is not a deployed change; a healthy runtime is not release or product acceptance.
+117
View File
@@ -0,0 +1,117 @@
---
title: "Onboarding"
description: "Join the Corp v1 pilot with the right access, context, channel routing, authority, security practices, and evidence expectations."
sidebar_position: 1
---
# Onboarding
Use this page when joining the Corp v1 pilot or entering a project for the first time. You should finish with the right access, a clear role, and enough context to contribute without bypassing project governance.
## What the pilot is
Corp v1 tests whether one AI agent can support several focused project workstreams while people retain explicit authority and durable oversight. The pilot currently includes:
- [AeroSim](/projects/aerosim/)
- [Maze Next Gen](/projects/mazeng/)
- [E-Shop v1](/projects/eshopv1/)
The [Board](/board/) governs project kickoff, closure, and changes to the main Corp v1 operating model. Each project has its own sponsor, team, approved scope, repositories, documentation, Discord category, and preserved authority decisions.
## Your first 20 minutes
1. **Confirm your identity and role.** Check the [member registry](/members/) and your [team record](/teams/). If either is wrong, raise it before taking ownership of work.
2. **Open the project record.** Read its purpose, initial deliverable, current status, resources, and outstanding gates in the [project registry](/projects/).
3. **Open the project documentation.** It is the durable source for scope, architecture, design, Kanban state, ways of working, engineering guidance, and release evidence.
4. **Verify Discord access.** Every project has one dedicated `corp-v1-<code>` category with seven lifecycle channels. Confirm that you can see the channels needed for your role and read their pinned guidance.
5. **Verify Gitea access.** Confirm access to the project and skills organizations through the appropriate teams. Do not request direct repository access when team membership is the intended route.
6. **Choose one current outcome.** Start from an existing Epic, Feature, task, issue, design package, or release gate. Do not create parallel records because an item is difficult to find.
## Use the seven channels correctly
Work moves through this shared lifecycle:
```text
General → Scope → Architecture → UI/UX → Kanban → Delivery → Releases
```
| Channel | Use it for |
|---|---|
| **General** | Project-wide direction, coordination, questions, outcomes, and cross-channel issues |
| **Scope** | Ideas, Epics, Features, value, acceptance outcomes, and product decisions |
| **Architecture** | Solution design, interfaces, constraints, risks, and implementation task definitions |
| **UI/UX** | User journeys, Penpot designs, responsive behavior, accessibility, and implementation handoff |
| **Kanban** | Flow visibility, task admission, sequencing, dependencies, and blockers |
| **Delivery** | Implementation, tests, reviews, CI, build health, and delivery evidence |
| **Releases** | Version readiness, changelogs, deployment approval, rollout, rollback, and runtime verification |
Post in the channel that owns the decision or artifact. Cross-link evidence instead of copying whole conversations between channels. Keep one project’s information inside that project’s seven-channel boundary unless a Board-level concern requires escalation.
## Understand authority
- **Board authority** covers project kickoff, project closure, and changes to `corp-v1-main`.
- **Project-team authority** covers decisions inside the project’s approved boundary.
- **Hermes authority** is project-specific. It may range from preparing proposals to full delegated delivery and merge authority. Use the preserved project record and channel skill; never infer authority from activity, silence, CI success, or an agent statement.
- **Explicit gates remain explicit.** A decision must identify the item, actor, conditions, and evidence. Delegation changes who may decide; it does not remove security, quality, traceability, or validation gates.
When authority is unclear, stop at a reversible proposal and ask in the owning channel.
## Know what “done” means
Keep these states separate:
1. **Approved** — an authorized person or delegate accepted the exact scope or decision.
2. **Implemented** — source changes exist and passed the required local/review checks.
3. **Merged** — the reviewed change is integrated into the repository’s default branch.
4. **Deployed / runtime verified** — the intended immutable revision is running and has passed live readback or acceptance checks.
5. **Released / accepted** — the project’s release authority approved the version and required outcomes.
Always state the highest level actually proven and link the evidence. Do not use “live” as a shortcut for release approval or product maturity.
## Security and credentials
- Never paste passwords, tokens, API keys, connection strings, secret values, or Bitwarden object metadata into Discord, issues, repositories, prompts, screenshots, or documentation.
- Use the approved SSO and secret-injection paths. A credential being available does not authorize unrelated access, account administration, spending, or destructive work.
- Record secret **names and readiness only** when governance requires it.
- Report suspected exposure immediately in the owning project and follow the approved rotation path.
- Treat private project repositories, project-channel history, and customer or operational data as project-bound information.
## How to make a useful contribution
A useful contribution is small enough to review and complete, but durable enough to help the next person:
- start from a stable item or create a clearly marked proposal;
- cite the source message, decision, requirement, design, issue, or runtime observation;
- work in the owning channel and canonical repository;
- preserve project naming, branch, testing, and documentation conventions;
- run the required validation and match CI to the exact commit;
- read back remote and deployed state before claiming completion;
- report the outcome, evidence, remaining gates, owner, and next action concisely.
If a task crosses channels, finish the source-owned result and hand off one clear requested action with evidence and unresolved risks.
## Where truth lives
| Information | Authoritative location |
|---|---|
| Portfolio governance, Board decisions, teams, and project registry | This Corp v1 portal |
| Product scope and project delivery records | Project documentation repository and deployed documentation |
| Source, reviews, commits, CI, and releases | Project Gitea repositories |
| Discussion, approvals, coordination, and handoffs | Exact project Discord channels and message IDs |
| Deployment and runtime state | GitOps source, Argo CD, workload state, and live acceptance evidence |
| Editable interface design | Project-owned Penpot files linked from project records |
No single status message replaces these sources. Reconcile them when they disagree.
## Onboarding complete
You are ready to contribute when you can answer:
- Which project and outcome am I supporting?
- What is my role and decision authority?
- Which channel owns my next action?
- Where is the canonical record?
- What evidence is required before I call it complete?
- Which security or release gates still apply?
If any answer is missing, ask in the project’s **General** channel and link the record you already checked.
+5 -2
View File
@@ -39,6 +39,7 @@ const config: Config = {
['@docusaurus/plugin-content-docs', {...docsCommon, id: 'projects', path: 'docs/projects', routeBasePath: 'projects', sidebarPath: './sidebars/projects.ts'}],
['@docusaurus/plugin-content-docs', {...docsCommon, id: 'teams', path: 'docs/teams', routeBasePath: 'teams', sidebarPath: './sidebars/teams.ts'}],
['@docusaurus/plugin-content-docs', {...docsCommon, id: 'members', path: 'docs/members', routeBasePath: 'members', sidebarPath: './sidebars/members.ts'}],
['@docusaurus/plugin-content-docs', {...docsCommon, id: 'ways-of-working', path: 'docs/ways-of-working', routeBasePath: 'ways-of-working', sidebarPath: './sidebars/ways-of-working.ts'}],
['@docusaurus/plugin-content-docs', {...docsCommon, id: 'board', path: 'docs/board', routeBasePath: 'board', sidebarPath: './sidebars/board.ts'}],
['@docusaurus/plugin-content-docs', {...docsCommon, id: 'governance', path: 'docs/governance', routeBasePath: 'governance', sidebarPath: './sidebars/governance.ts'}],
],
@@ -49,7 +50,7 @@ const config: Config = {
indexDocs: true,
indexBlog: false,
indexPages: true,
docsRouteBasePath: ['/', 'architecture-high-level', 'projects', 'teams', 'members', 'board', 'governance'],
docsRouteBasePath: ['/', 'architecture-high-level', 'projects', 'teams', 'members', 'ways-of-working', 'board', 'governance'],
language: ['en'],
highlightSearchTermsOnTargetPage: true,
explicitSearchResultPath: true,
@@ -62,11 +63,12 @@ const config: Config = {
navbar: {
title: 'CORP V1 / BOARD',
items: [
{type: 'docSidebar', sidebarId: 'boardSidebar', docsPluginId: 'board', label: 'Board', position: 'left'},
{type: 'docSidebar', sidebarId: 'projectsSidebar', docsPluginId: 'projects', label: 'Projects', position: 'left'},
{type: 'docSidebar', sidebarId: 'teamsSidebar', docsPluginId: 'teams', label: 'Teams', position: 'left'},
{type: 'docSidebar', sidebarId: 'membersSidebar', docsPluginId: 'members', label: 'Members', position: 'left'},
{type: 'docSidebar', sidebarId: 'boardSidebar', docsPluginId: 'board', label: 'Board', position: 'left'},
{type: 'docSidebar', sidebarId: 'governanceSidebar', docsPluginId: 'governance', label: 'Governance', position: 'left'},
{type: 'docSidebar', sidebarId: 'waysOfWorkingSidebar', docsPluginId: 'ways-of-working', label: 'Ways of Working', position: 'left'},
{type: 'docSidebar', sidebarId: 'architectureHighLevelSidebar', docsPluginId: 'architecture-high-level', label: 'Architecture', position: 'left'},
{href: 'https://gitea.lego-cloud.eu/corp-v1/portal', label: 'Gitea ↗', position: 'right'},
],
@@ -76,6 +78,7 @@ const config: Config = {
links: [{title: 'Registry', items: [
{label: 'Architecture', to: '/architecture-high-level/context/'},
{label: 'Projects', to: '/projects/'},
{label: 'Ways of Working', to: '/ways-of-working/'},
{label: 'Teams', to: '/teams/'},
{label: 'Members', to: '/members/'},
{label: 'Board', to: '/board/'},
+6
View File
@@ -50,5 +50,11 @@
},
"engines": {
"node": ">=20.0"
},
"pnpm": {
"overrides": {
"fast-uri": "3.1.6",
"serialize-javascript": "7.0.3"
}
}
}
+14 -18
View File
@@ -4,6 +4,10 @@ settings:
autoInstallPeers: true
excludeLinksFromLockfile: false
overrides:
fast-uri: 3.1.6
serialize-javascript: 7.0.3
importers:
.:
@@ -3061,8 +3065,8 @@ packages:
fast-json-stable-stringify@2.1.0:
resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==}
fast-uri@3.1.5:
resolution: {integrity: sha512-gHwA1O9LDIcKunMKhObS/HimwtehO1nPUECKAu5TpKgaO19fcWEl4bliWe1jWxVFvIXztJjjQ4L8XQ1EU9f7Jw==}
fast-uri@3.1.6:
resolution: {integrity: sha512-7Ical1vFEMr0onbVzEDIreM22I4khW+fzyQPwvAFWBp1iwdshSZRsL4jjRvPG9JP1uiqMHRto+YU6R2/CzDz5Q==}
fast-xml-builder@1.3.1:
resolution: {integrity: sha512-pIM/1n3ntFXKYrUZwW7QCK0gAW7XY+wzj1YMIV3tLDvPj/V+zTGJK5e3/4WJfwj0qWw2ElNXiTixda/R+3YSug==}
@@ -4763,9 +4767,6 @@ packages:
resolution: {integrity: sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==}
engines: {node: '>=10'}
randombytes@2.1.0:
resolution: {integrity: sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==}
range-parser@1.2.0:
resolution: {integrity: sha512-kA5WQoNVo4t9lNx2kQNFCxKeBl5IbbSNBl1M/tLkw9WCn+hxNBAW5Qh8gdhs63CJnhjJ2zQWFoqPJP2sK1AV5A==}
engines: {node: '>= 0.6'}
@@ -5035,8 +5036,9 @@ packages:
resolution: {integrity: sha512-VMbMxbDeehAxpOtWJXlcUS5E8iXh6QmN+BkRX1GARS3wRaXEEgzCcB10gTQazO42tpNIya8xIyNx8fll1OFPrg==}
engines: {node: '>= 0.8.0'}
serialize-javascript@6.0.2:
resolution: {integrity: sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==}
serialize-javascript@7.0.3:
resolution: {integrity: sha512-h+cZ/XXarqDgCjo+YSyQU/ulDEESGGf8AMK9pPNmhNSl/FzPl6L8pMp1leca5z6NuG6tvV/auC8/43tmovowww==}
engines: {node: '>=20.0.0'}
serve-handler@6.1.7:
resolution: {integrity: sha512-CinAq1xWb0vR3twAv9evEU8cNWkXCb9kd5ePAHUKJBkOsUpR1wt/CvGdeca7vqumL1U5cSaeVQ6zZMxiJ3yWsg==}
@@ -8904,7 +8906,7 @@ snapshots:
ajv@8.20.0:
dependencies:
fast-deep-equal: 3.1.3
fast-uri: 3.1.5
fast-uri: 3.1.6
json-schema-traverse: 1.0.0
require-from-string: 2.0.2
@@ -9337,7 +9339,7 @@ snapshots:
globby: 13.2.2
normalize-path: 3.0.0
schema-utils: 4.3.3
serialize-javascript: 6.0.2
serialize-javascript: 7.0.3
webpack: 5.109.2(@swc/core@1.15.47)(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.26))(html-minifier-terser@7.2.0)(postcss@8.5.26)
core-js-compat@3.50.0:
@@ -9404,7 +9406,7 @@ snapshots:
jest-worker: 29.7.0
postcss: 8.5.26
schema-utils: 4.3.3
serialize-javascript: 6.0.2
serialize-javascript: 7.0.3
webpack: 5.109.2(@swc/core@1.15.47)(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.26))(html-minifier-terser@7.2.0)(postcss@8.5.26)
optionalDependencies:
clean-css: 5.3.3
@@ -9847,7 +9849,7 @@ snapshots:
fast-json-stable-stringify@2.1.0: {}
fast-uri@3.1.5: {}
fast-uri@3.1.6: {}
fast-xml-builder@1.3.1:
dependencies:
@@ -11890,10 +11892,6 @@ snapshots:
quick-lru@5.1.1: {}
randombytes@2.1.0:
dependencies:
safe-buffer: 5.2.1
range-parser@1.2.0: {}
range-parser@1.2.1: {}
@@ -12247,9 +12245,7 @@ snapshots:
transitivePeerDependencies:
- supports-color
serialize-javascript@6.0.2:
dependencies:
randombytes: 2.1.0
serialize-javascript@7.0.3: {}
serve-handler@6.1.7:
dependencies:
+375 -9
View File
@@ -21,16 +21,29 @@ for (const section of ['projects', 'teams', 'members', 'board', 'governance']) {
assert.match(config, new RegExp(`sidebarId:\\s*'${section}Sidebar'`), `${section} navbar item does not target its dedicated sidebar`);
assert.ok(existsSync(join(root, `sidebars/${section}.ts`)), `${section} sidebar file is missing`);
}
assert.match(config, /id:\s*'ways-of-working'/, 'Ways of Working docs plugin is missing');
assert.match(config, /sidebarId:\s*'waysOfWorkingSidebar'/, 'Ways of Working navbar item does not target its dedicated sidebar');
assert.ok(existsSync(join(root, 'sidebars/ways-of-working.ts')), 'Ways of Working sidebar file is missing');
assert.ok(existsSync(join(root, 'docs/ways-of-working/index.md')), 'Ways of Working entry page is missing');
assert.ok(existsSync(join(root, 'docs/ways-of-working/onboarding.md')), 'Onboarding page is missing');
assert.match(config, /id:\s*'architecture-high-level'/, 'Architecture High Level docs plugin is missing');
assert.match(config, /sidebarId:\s*'architectureHighLevelSidebar'/, 'Architecture High Level navbar item does not target its dedicated sidebar');
assert.match(config, /label:\s*'Architecture'/, 'Architecture navbar label is missing');
assert.doesNotMatch(config, /label:\s*'Architecture High Level'/, 'legacy Architecture High Level menu label must not remain');
assert.ok(existsSync(join(root, 'sidebars/architecture-high-level.ts')), 'Architecture High Level sidebar file is missing');
const expectedLeftNavLabels = ['Projects', 'Teams', 'Members', 'Board', 'Governance', 'Architecture'];
const expectedLeftNavLabels = ['Board', 'Projects', 'Teams', 'Members', 'Governance', 'Ways of Working', 'Architecture'];
const leftNavLabels = [...config.matchAll(/\{type:\s*'docSidebar',[^\n]+label:\s*'([^']+)',\s*position:\s*'left'\}/g)]
.map((match) => match[1]);
assert.deepEqual(leftNavLabels, expectedLeftNavLabels, 'Architecture must be the final left-side menu item');
assert.deepEqual(leftNavLabels, expectedLeftNavLabels, 'Top-level navigation must follow the approved Board-first order');
const waysOfWorkingSidebar = read('sidebars/ways-of-working.ts');
assert.match(waysOfWorkingSidebar, /link:\s*\{type:\s*'doc',\s*id:\s*'index'\}/, 'Ways of Working must link to its entry page');
assert.match(waysOfWorkingSidebar, /items:\s*\[\{type:\s*'doc',\s*id:\s*'onboarding',\s*label:\s*'Onboarding'\}\]/, 'Onboarding must be the first child page');
const onboarding = read('docs/ways-of-working/onboarding.md');
for (const term of ['Your first 20 minutes', 'Use the seven channels correctly', 'Understand authority', 'Know what “done” means', 'Security and credentials', 'Onboarding complete']) {
assert.ok(onboarding.includes(term), `Onboarding is missing: ${term}`);
}
assert.match(config, /baseUrl:\s*'\/corp-v1\/portal\/'/, 'Pages base URL must follow the renamed repository');
assert.match(config, /projectName:\s*'portal'/, 'Docusaurus project name must be portal');
@@ -38,11 +51,364 @@ assert.doesNotMatch(config, /sterring-commitee/, 'legacy repository name must no
assert.doesNotMatch(config, /Pilot Model|docs\/pilot|routeBasePath:\s*'pilot'/, 'legacy Pilot Model navigation must not remain');
const board = read('docs/board/index.md');
for (const memberId of ['1518725627845283888', '476287310627864587', '773109855497093191', '364383883778850827']) {
for (const memberId of [
'1518725627845283888',
'476287310627864587',
'773109855497093191',
'364383883778850827',
'1483820991720329227',
'1540035254746882048',
'501954115690168321',
'1526860732917088266',
]) {
assert.ok(board.includes(memberId), `board page is missing Discord member ${memberId}`);
}
assert.match(board, /Only these Board members may approve a project kickoff or project closure/i);
assert.match(board, /Only these Board members may approve changes to `corp-v1--main`/i);
assert.match(board, /exactly eight members/i);
assert.match(board, /Only the seven human Board members may approve a project kickoff or project closure/i);
assert.match(board, /Only the seven human Board members may approve changes to `corp-v1-main`/i);
assert.match(board, /Jarvis .*Board member and executing code agent/i);
for (const path of [
'docs/projects/dpvp.md',
'docs/teams/dpvp.md',
'docs/governance/decisions/jarvis-board-all-project-membership.md',
]) {
assert.ok(existsSync(join(root, path)), `${path} is missing`);
}
const jarvisMember = read('docs/members/jarvis-at-skic.md');
for (const marker of ['Board member and executing code agent', 'all 35 lifecycle channels', 'all ten project/skills teams']) {
assert.ok(jarvisMember.includes(marker), `Jarvis member record is missing: ${marker}`);
}
const dpvpProject = read('docs/projects/dpvp.md');
for (const marker of ['corp-v1-dpvp', 'dpvp-maintainers', 'dpvp-skill-maintainers', '1544621890994184224']) {
assert.ok(dpvpProject.includes(marker), `DPVP project record is missing: ${marker}`);
}
const aerosimProject = read('docs/projects/aerosim.md');
const APP_SHA = '09628fbb828380fbe159be7530da26f4bbf02129';
const DOC_SHA = 'd8a45594c33efc3acbd1523955d4f235facc9a1f';
const AEROSIM_CHECKPOINT_HEADING = 'Delivery progress checkpoint — 2026-09-07';
const markdownSection = (document, heading) => {
const marker = `## ${heading}`;
const start = document.indexOf(marker);
assert.notEqual(start, -1, `AeroSim section is missing: ${heading}`);
const end = document.indexOf('\n## ', start + marker.length);
return document.slice(start, end === -1 ? document.length : end);
};
const uniqueLine = (text, predicate, description) => {
const matches = text.split('\n').filter(predicate);
assert.equal(matches.length, 1, `AeroSim must contain exactly one ${description}`);
return matches[0];
};
function verifyAeroSimProject(document) {
const requiredSectionHeadings = ['Resources', AEROSIM_CHECKPOINT_HEADING, 'Discord'];
const documentLines = document.split('\n');
const requiredSectionIndices = requiredSectionHeadings.map((heading) => {
const indices = documentLines.flatMap((line, index) => line === `## ${heading}` ? [index] : []);
assert.equal(indices.length, 1, `AeroSim required section heading must appear exactly once: ${heading}`);
return indices[0];
});
assert.ok(
requiredSectionIndices.every((index, position) => position === 0 || requiredSectionIndices[position - 1] < index),
'AeroSim required sections must follow Resources, checkpoint, Discord order',
);
const requiredMarkers = [
AEROSIM_CHECKPOINT_HEADING,
'49 / 114',
'43.0%',
'6 / 114 (5.3%)',
'7 / 114 (6.1%)',
'58 / 114 (50.9%)',
'PR #155',
'2581',
'2582',
APP_SHA,
DOC_SHA,
'Wave 15 is active',
'6 of its 7 Tasks are repository-verified',
'PRs #85, #89, #90, #95, #96, and #97',
'integrated tasks `2718`–`2720`',
'`TASK-0078` remains canonical `InProgress`',
'PR #92 is closed without merge',
'Wave 16 remains unclaimed',
];
for (const marker of requiredMarkers) {
assert.ok(document.includes(marker), `AeroSim progress checkpoint is missing: ${marker}`);
}
const resources = markdownSection(document, 'Resources');
const applicationResource = uniqueLine(resources, (line) => line.startsWith('- [Application repository]'), 'application repository resource');
const documentationResource = uniqueLine(resources, (line) => line.startsWith('- [Documentation repository]'), 'documentation repository resource');
assert.match(applicationResource, new RegExp(`application.*\\b${APP_SHA}\\b`, 'i'), 'application repository must reference the application SHA');
assert.match(documentationResource, new RegExp(`documentation.*\\b${DOC_SHA}\\b`, 'i'), 'documentation repository must reference the documentation SHA');
const checkpoint = markdownSection(document, AEROSIM_CHECKPOINT_HEADING);
const checkpointLines = checkpoint.split('\n');
const checkpointTableHeader = '| Measure | Progress | Meaning |';
const checkpointTableHeaderIndices = checkpointLines.flatMap(
(line, index) => line === checkpointTableHeader ? [index] : [],
);
assert.equal(checkpointTableHeaderIndices.length, 1, 'AeroSim checkpoint table header must appear exactly once');
const checkpointTableHeaderIndex = checkpointTableHeaderIndices[0];
assert.equal(checkpointLines[checkpointTableHeaderIndex + 1], '|---|---:|---|', 'AeroSim checkpoint table separator must exactly preserve its three columns and progress alignment');
const expectedRows = [
'Canonical `ToBeReleased`',
'Repository-verified implementation pending reconciliation',
'Canonical `InProgress`',
'Canonical `ReadyForDelivery`',
'Released',
];
assert.deepEqual(
checkpointLines.slice(checkpointTableHeaderIndex + 2, checkpointTableHeaderIndex + 7).map(
(line) => line.match(/^\| ([^|]+?) \|/)?.[1],
),
expectedRows,
'AeroSim checkpoint rows must preserve canonical, reconciliation, active, ready, and released order',
);
const canonicalRow = uniqueLine(checkpoint, (line) => line.startsWith('| Canonical `ToBeReleased` |'), 'canonical ToBeReleased row');
const implementationRow = uniqueLine(checkpoint, (line) => line.startsWith('| Repository-verified implementation pending reconciliation |'), 'repository-verified pending-reconciliation row');
const inProgressRow = uniqueLine(checkpoint, (line) => line.startsWith('| Canonical `InProgress` |'), 'canonical InProgress row');
const readyRow = uniqueLine(checkpoint, (line) => line.startsWith('| Canonical `ReadyForDelivery` |'), 'canonical ReadyForDelivery row');
const releasedRow = uniqueLine(checkpoint, (line) => line.startsWith('| Released |'), 'released row');
const waveStatus = uniqueLine(checkpoint, (line) => line.startsWith('Wave 15 is active'), 'Wave 15 status paragraph');
assert.match(canonicalRow, /\|\s*49\s*\/\s*114\s*\(43\.0%\)/i, 'AeroSim must expose canonical ToBeReleased progress');
assert.match(implementationRow, /\|\s*6\s*\/\s*114\s*\(5\.3%\)/i, 'AeroSim must expose repository-verified pending reconciliation separately');
assert.match(inProgressRow, /\|\s*7\s*\/\s*114\s*\(6\.1%\)/i, 'AeroSim must expose canonical InProgress progress');
assert.match(readyRow, /\|\s*58\s*\/\s*114\s*\(50\.9%\)/i, 'AeroSim must expose canonical ReadyForDelivery progress');
assert.match(releasedRow, /\|\s*0\s*\/\s*114\s*\(0\.0%\)/i, 'AeroSim must distinguish released progress');
assert.match(waveStatus, new RegExp('documentation `test` SHA `' + DOC_SHA + '`[^\\n]*PR #155 exact-head build task'), 'Wave 15 status must bind PR #155 to the documentation SHA');
assert.match(waveStatus, /exact-head build task `2581`[^\n]*integrated build task `2582`/i, 'Wave 15 status must bind exact-head and integrated documentation tasks');
assert.match(waveStatus, new RegExp('application integration head is `' + APP_SHA + '`'), 'Wave 15 status must bind the current application SHA');
assert.match(waveStatus, /6 of its 7 Tasks are repository-verified[^\n]*PRs #85, #89, #90, #95, #96, and #97/i, 'Wave 15 status must enumerate repository-verified integration evidence');
assert.match(waveStatus, /`TASK-0078` remains canonical `InProgress`[^\n]*PR #92 is closed without merge/i, 'Wave 15 status must preserve the unmerged Task state');
assert.match(readyRow, /Waves 9–11 and 16–30 remain ready but unclaimed/i, 'ReadyForDelivery must identify both earlier and later unclaimed waves');
assert.match(waveStatus, /dated portfolio checkpoint, not a second task database/i, 'AeroSim must remain a non-authoritative portfolio checkpoint');
assert.doesNotMatch(checkpoint, /Repository-verified implementation \|/i, 'ambiguous cumulative implementation row must not return');
assert.doesNotMatch(document, /8\s*\/\s*114\s*\(7\.0%\)/i, 'stale Wave 2 portfolio metrics must not remain');
assert.doesNotMatch(waveStatus, /Wave 3 is active/i, 'stale active-wave wording must not remain');
}
verifyAeroSimProject(aerosimProject);
if (process.argv.includes('--self-test')) {
const replaceExactly = (document, oldText, newText) => {
assert.equal(document.split(oldText).length - 1, 1, `mutation fixture must find exactly one occurrence: ${oldText}`);
return document.replace(oldText, newText);
};
const swap = (document, left, right) => {
const placeholder = '__VERIFY_PORTAL_MUTATION_PLACEHOLDER__';
return replaceExactly(replaceExactly(replaceExactly(document, left, placeholder), right, left), placeholder, right);
};
const swapAll = (document, left, right) => {
assert.ok(document.includes(left), `mutation fixture must find: ${left}`);
assert.ok(document.includes(right), `mutation fixture must find: ${right}`);
const placeholder = '__VERIFY_PORTAL_MUTATION_PLACEHOLDER__';
return document.replaceAll(left, placeholder).replaceAll(right, left).replaceAll(placeholder, right);
};
const checkpointRow = (document, prefix) => uniqueLine(
markdownSection(document, 'Delivery progress checkpoint — 2026-09-03'),
(line) => line.startsWith(prefix),
`${prefix} mutation source row`,
);
const sectionBlock = (document, heading) => {
const section = markdownSection(document, heading);
return section.endsWith('\n') ? section : `${section}\n`;
};
const futureCountFixtures = [14, 15, 24, 25, 114].flatMap((count) => [
{
name: `accepts legitimate future count ${count} / 114`,
document: replaceExactly(
aerosimProject,
'Release `1.0.0` contains 114 Tasks.',
`Release \`1.0.0\` contains 114 Tasks. Forecast example: ${count} / 114.`,
),
accepted: true,
},
{
name: `accepts legitimate compact future count ${count}/114`,
document: replaceExactly(
aerosimProject,
'Release `1.0.0` contains 114 Tasks.',
`Release \`1.0.0\` contains 114 Tasks. Forecast example: ${count}/114.`,
),
accepted: true,
},
]);
const staleCountFixtures = [4, 5].flatMap((count) => [
{
name: `rejects stale count ${count} / 114`,
document: replaceExactly(
aerosimProject,
'Release `1.0.0` contains 114 Tasks.',
`Release \`1.0.0\` contains 114 Tasks. Superseded snapshot: ${count} / 114.`,
),
accepted: false,
message: new RegExp(`stale AeroSim checkpoint marker must not remain: ${count} / 114`),
},
{
name: `rejects compact stale count ${count}/114`,
document: replaceExactly(
aerosimProject,
'Release `1.0.0` contains 114 Tasks.',
`Release \`1.0.0\` contains 114 Tasks. Superseded snapshot: ${count}/114.`,
),
accepted: false,
message: new RegExp(`stale AeroSim checkpoint marker must not remain: ${count} / 114`),
},
]);
const canonicalRowFixture = checkpointRow(aerosimProject, '| Canonical `ToBeReleased` |');
const implementationRowFixture = checkpointRow(aerosimProject, '| Repository-verified implementation |');
const releasedRowFixture = checkpointRow(aerosimProject, '| Released |');
const resourcesSectionFixture = sectionBlock(aerosimProject, 'Resources');
const checkpointSectionFixture = sectionBlock(aerosimProject, 'Delivery progress checkpoint — 2026-09-03');
const discordSectionFixture = sectionBlock(aerosimProject, 'Discord');
const fixtures = [
...futureCountFixtures,
...staleCountFixtures,
{
name: 'rejects removed checkpoint table header',
document: replaceExactly(aerosimProject, '| Measure | Progress | Meaning |\n', ''),
accepted: false,
message: /checkpoint table header/,
},
{
name: 'rejects malformed checkpoint table header',
document: replaceExactly(aerosimProject, '| Measure | Progress | Meaning |', '| Measure | Meaning | Progress |'),
accepted: false,
message: /checkpoint table header/,
},
{
name: 'rejects removed checkpoint table separator',
document: replaceExactly(aerosimProject, '|---|---:|---|\n', ''),
accepted: false,
message: /checkpoint table separator/,
},
{
name: 'rejects malformed checkpoint table separator',
document: replaceExactly(aerosimProject, '|---|---:|---|', '|---|---|---|'),
accepted: false,
message: /checkpoint table separator/,
},
{
name: 'rejects swapped canonical and implementation rows',
document: swap(aerosimProject, canonicalRowFixture, implementationRowFixture),
accepted: false,
message: /checkpoint rows must follow canonical, implementation, released order/,
},
{
name: 'rejects swapped implementation and released rows',
document: swap(aerosimProject, implementationRowFixture, releasedRowFixture),
accepted: false,
message: /checkpoint rows must follow canonical, implementation, released order/,
},
{
name: 'rejects removed Resources heading',
document: replaceExactly(aerosimProject, '## Resources\n', ''),
accepted: false,
message: /required section heading.*Resources/i,
},
{
name: 'rejects renamed Resources heading',
document: replaceExactly(aerosimProject, '## Resources', '## Project resources'),
accepted: false,
message: /required section heading.*Resources/i,
},
{
name: 'rejects removed checkpoint heading',
document: replaceExactly(aerosimProject, '## Delivery progress checkpoint — 2026-09-03\n', ''),
accepted: false,
message: /required section heading.*Delivery progress checkpoint/i,
},
{
name: 'rejects renamed checkpoint heading',
document: replaceExactly(aerosimProject, '## Delivery progress checkpoint — 2026-09-03', '## Delivery status — 2026-09-03'),
accepted: false,
message: /required section heading.*Delivery progress checkpoint/i,
},
{
name: 'rejects removed Discord heading',
document: replaceExactly(aerosimProject, '## Discord\n', ''),
accepted: false,
message: /required section heading.*Discord/i,
},
{
name: 'rejects renamed Discord heading',
document: replaceExactly(aerosimProject, '## Discord', '## Project channels'),
accepted: false,
message: /required section heading.*Discord/i,
},
{
name: 'rejects Resources and checkpoint sections in reverse order',
document: swap(aerosimProject, resourcesSectionFixture, checkpointSectionFixture),
accepted: false,
message: /required sections must follow Resources, checkpoint, Discord order/,
},
{
name: 'rejects checkpoint and Discord sections in reverse order',
document: swap(aerosimProject, checkpointSectionFixture, discordSectionFixture),
accepted: false,
message: /required sections must follow Resources, checkpoint, Discord order/,
},
{
name: 'rejects swapped application and documentation SHA associations',
document: swapAll(aerosimProject, APP_SHA, DOC_SHA),
accepted: false,
message: /application repository.*SHA|documentation repository.*SHA/i,
},
{
name: 'rejects swapped publish and validate CI task associations',
document: replaceExactly(
aerosimProject,
'publish task `1760` and validate task `1761`',
'publish task `1761` and validate task `1760`',
),
accepted: false,
message: /publish task.*1760|validate task.*1761/i,
},
{
name: 'rejects swapped documentation CI task associations',
document: replaceExactly(
aerosimProject,
'exact-head build task `1762` and integrated build task `1763`',
'exact-head build task `1763` and integrated build task `1762`',
),
accepted: false,
message: /exact-head build task.*1762|integrated build task.*1763/i,
},
{
name: 'rejects Wave 2 and Wave 3 task-group permutations',
document: swap(
aerosimProject,
'`TASK-0012`, `TASK-0015`, `TASK-0073`, and `TASK-0114`',
'`TASK-0013`, `TASK-0016`, `TASK-0074`, and `TASK-0115`',
),
accepted: false,
message: /Wave 2 task group|Wave 3 task group/i,
},
];
const failures = [];
for (const fixture of fixtures) {
try {
verifyAeroSimProject(fixture.document);
if (!fixture.accepted) throw new assert.AssertionError({message: 'mutated document was incorrectly accepted'});
console.log(`ok - ${fixture.name}`);
} catch (error) {
if (!fixture.accepted && fixture.message?.test(error.message)) {
console.log(`ok - ${fixture.name}`);
} else {
failures.push(`${fixture.name}: ${error.message}`);
console.error(`not ok - ${fixture.name}: ${error.message}`);
}
}
}
assert.equal(failures.length, 0, `AeroSim verifier self-tests failed:\n${failures.join('\n')}`);
console.log('AeroSim verifier self-tests passed.');
}
const lifecycle = read('docs/governance/project-lifecycle.md');
assert.match(lifecycle, /Board approval/i, 'project lifecycle must require Board approval');
@@ -68,7 +434,7 @@ assert.match(config, /indexPages:\s*true/, 'custom pages must be indexed');
const searchRoutesMatch = config.match(/docsRouteBasePath:\s*\[([^\]]+)\]/);
assert.ok(searchRoutesMatch, 'search route configuration is missing');
const searchRoutes = searchRoutesMatch[1];
for (const route of ['/', 'architecture-high-level', 'projects', 'teams', 'members', 'board', 'governance']) {
for (const route of ['/', 'architecture-high-level', 'projects', 'teams', 'members', 'ways-of-working', 'board', 'governance']) {
assert.ok(searchRoutes.includes(`'${route}'`), `search does not include route base ${route}`);
}
@@ -103,7 +469,7 @@ const architecturePages = {
for (const [name, page] of Object.entries(architecturePages)) {
assert.match(page, /!!raw-loader!\.\/diagrams\/.+\.drawio/, `${name} page must render an editable Draw.io source`);
}
for (const term of ['seven channel skills', 'seven engineering skills', 'Gitea Actions', 'scheduler jobs', 'corp-v1-board', 'corp-v1-guild', 'corp-v1--guild', 'UI/UX', 'one AI agent', 'Hermes Agent', 'MicroK8s', 'Penpot', 'Argo CD', 'Harbor']) {
for (const term of ['seven channel skills', 'seven engineering skills', 'Gitea Actions', 'scheduler jobs', 'corp-v1-board', 'corp-v1-guild', 'corp-v1-guild', 'UI/UX', 'one AI agent', 'Hermes Agent', 'MicroK8s', 'Penpot', 'Argo CD', 'Harbor']) {
assert.ok(Object.values(architecturePages).some((page) => page.includes(term)), `architecture explanation is missing: ${term}`);
}
assert.match(architecturePages.channels, /two central portfolio workspaces/i, 'channels overview must distinguish Board and Guild as central workspaces');
@@ -119,7 +485,7 @@ for (const term of ['only two external software systems', 'LLM Provider', 'ICA o
for (const term of ['Gitea Actions runners', 'Penpot', 'LEGO Cloud Pages', 'Harbor', 'Argo CD', 'Identity and access', 'Ingress edge', 'Gondor v1 MicroK8s']) {
assert.ok(architecturePages.overview.includes(term), `container overview is missing internal container: ${term}`);
}
for (const term of ['corp-v1--main', 'corp-v1-channel-ui-ux', 'development-gitops-argo-cd', 'drawio-main', 'systematic-debugging', 'gondor-v1-nodes']) {
for (const term of ['corp-v1-main', 'corp-v1-channel-ui-ux', 'development-gitops-argo-cd', 'drawio-main', 'systematic-debugging', 'gondor-v1-nodes']) {
assert.ok(architecturePages.skills.includes(term), `skills overview is missing: ${term}`);
}
for (const [name, page] of Object.entries(architecturePages)) {
@@ -145,7 +511,7 @@ if (existsSync(join(root, 'build'))) {
const filename = readdirSync(join(root, 'build')).find((name) => /^search-index(?:-[a-f0-9]+)?\.json$/.test(name));
assert.ok(filename, 'production search index is missing');
const search = readFileSync(join(root, 'build', filename), 'utf8').toLowerCase();
for (const term of ['projects registry', 'teams registry', 'members registry', 'board members', 'project lifecycle', 'corp v1 board', 'container overview', 'operating model', 'overview channels', 'overview skills', 'overview repositories']) {
for (const term of ['projects registry', 'teams registry', 'members registry', 'board members', 'project lifecycle', 'corp v1 board', 'ways of working', 'your first 20 minutes', 'onboarding complete', 'container overview', 'operating model', 'overview channels', 'overview skills', 'overview repositories']) {
assert.ok(search.includes(term), `search index is missing: ${term}`);
}
}
+15
View File
@@ -0,0 +1,15 @@
import type {SidebarsConfig} from '@docusaurus/plugin-content-docs';
const sidebars: SidebarsConfig = {
waysOfWorkingSidebar: [
{
type: 'category',
label: 'Ways of Working',
link: {type: 'doc', id: 'index'},
collapsed: false,
items: [{type: 'doc', id: 'onboarding', label: 'Onboarding'}],
},
],
};
export default sidebars;
+39
View File
@@ -0,0 +1,39 @@
import assert from 'node:assert/strict';
import {readFile} from 'node:fs/promises';
import test from 'node:test';
const project = await readFile(new URL('../docs/projects/aerosim.md', import.meta.url), 'utf8');
const packageJson = JSON.parse(await readFile(new URL('../package.json', import.meta.url), 'utf8'));
const lockfile = await readFile(new URL('../pnpm-lock.yaml', import.meta.url), 'utf8');
test('AeroSim portfolio roll-up reports the verified Wave 15 checkpoint', () => {
assert.match(project, /## Delivery progress checkpoint — 2026-09-07/);
assert.match(project, /Canonical `ToBeReleased` \| 49 \/ 114 \(43\.0%\)/);
assert.match(project, /Repository-verified implementation pending reconciliation \| 6 \/ 114 \(5\.3%\)/);
assert.match(project, /Canonical `InProgress` \| 7 \/ 114 \(6\.1%\)/);
assert.match(project, /Canonical `ReadyForDelivery` \| 58 \/ 114 \(50\.9%\)/);
assert.match(project, /Released \| 0 \/ 114 \(0\.0%\)/);
assert.match(project, /Wave 15 is active/);
assert.match(project, /6 of its 7 Tasks are repository-verified/);
assert.match(project, /`TASK-0048`, `TASK-0061`, `TASK-0065`, `TASK-0077`, `TASK-0083`, and `TASK-0111`/);
assert.match(project, /`TASK-0078` remains canonical `InProgress`[^\n]*PR #92 is closed without merge/);
assert.match(project, /`09628fbb828380fbe159be7530da26f4bbf02129`/);
assert.match(project, /`d8a45594c33efc3acbd1523955d4f235facc9a1f`/);
assert.match(project, /PRs #85, #89, #90, #95, #96, and #97/);
assert.match(project, /integrated tasks `2718`–`2720`/);
assert.match(project, /Waves 9–11 and 16–30 remain ready but unclaimed/);
assert.doesNotMatch(project, /Repository-verified implementation pending reconciliation \| 0 \/ 114/);
assert.doesNotMatch(project, /`7f26eca79eadef3171564fc60035e9866c2c848e`/);
assert.doesNotMatch(project, /Wave 3 is active/);
});
test('portal pins patched audit dependencies without downgrading consumers', () => {
assert.deepEqual(packageJson.pnpm?.overrides, {
'fast-uri': '3.1.6',
'serialize-javascript': '7.0.3',
});
assert.match(lockfile, /fast-uri@3\.1\.6:/);
assert.match(lockfile, /serialize-javascript@7\.0\.3:/);
assert.doesNotMatch(lockfile, /fast-uri@3\.1\.5:/);
assert.doesNotMatch(lockfile, /serialize-javascript@6\.0\.2:/);
});