docs: onboard Jarvis across Corp v1
Build and publish Corp v1 Board portal / build (push) Successful in 50s
Build and publish Corp v1 Board portal / build (push) Successful in 50s
This commit is contained in:
@@ -9,7 +9,7 @@ sidebar_position: 4
|
||||
|---|---|
|
||||
| Status | Active — Gitea lead activation pending |
|
||||
| Lead | Linas |
|
||||
| Members | Linas |
|
||||
| Members | Linas; `jarvis-at-skic` / Hermes executing code agent |
|
||||
| Assigned project | [3D Architecture Wizzard](/projects/3darch/) |
|
||||
|
||||
## Mandate
|
||||
@@ -27,4 +27,6 @@ Deliver the 3D Architecture Wizzard browser experience, its documentation, and t
|
||||
|
||||
- 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.
|
||||
|
||||
@@ -28,6 +28,7 @@ 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.
|
||||
- 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, Giedrius K, and Jone Tamulaite - Nong 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.
|
||||
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
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 |
|
||||
| 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`.
|
||||
- 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.
|
||||
@@ -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, grant per-unit write access, and contain verified users `root-at-skic` and `jarvis-at-skic`. Jarvis's Discord view, send, and history access passes across all seven lifecycle channels.
|
||||
|
||||
## Communication and autonomy
|
||||
|
||||
|
||||
+3
-2
@@ -8,9 +8,10 @@ sidebar_position: 1
|
||||
|
||||
| Team | Status | Lead | Members | Active projects |
|
||||
|---|---|---|---:|---:|
|
||||
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 8 | 1 |
|
||||
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 12 | 1 |
|
||||
| [Maze Next Gen Team](/teams/mazeng/) | Active | RootAtSkic | 4 | 1 |
|
||||
| [E-Shop v1 Team](/teams/eshopv1/) | Active | RootAtSkic | 2 | 1 |
|
||||
| [3D Architecture Wizzard Team](/teams/3darch/) | Active — Gitea lead activation pending | Linas | 1 | 1 |
|
||||
| [3D Architecture Wizzard Team](/teams/3darch/) | Active — Gitea lead activation pending | Linas | 2 | 1 |
|
||||
| [DPVP Team](/teams/dpvp/) | Kickoff in progress | RootAtSkic | 3 | 1 |
|
||||
|
||||
A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.
|
||||
|
||||
@@ -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`, and `piotras`. Jarvis's verified memberships cover two project repositories and fourteen project-skill repositories, and its Discord view, send, and history access passes across all seven lifecycle channels. Piotras's memberships are also verified. Jenny has verified Discord access, but her Gitea team access remains pending a verified username or account creation; no identity was guessed.
|
||||
|
||||
## Communication
|
||||
|
||||
|
||||
Reference in New Issue
Block a user