jarvis-at-skic
23ad72c038
Build and publish Corp v1 Board portal / build (pull_request) Successful in 36s
2.3 KiB
2.3 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| AeroSim Team | 1 |
AeroSim Team
| Field | Value |
|---|---|
| Status | Active |
| Lead | RootAtSkic |
| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; Piotras; Andrius; Dovydas; Giedrius K; Jone Tamulaite - Nong; jarvis-at-skic / Hermes code agent |
| Assigned project | AeroSim |
Mandate
Deliver the AeroSim browser flight-simulation platform, its documentation, and the reusable project-specific engineering practices required to operate it.
Responsibilities
- Product and delivery coordination.
- Flight-simulation architecture and shared flight model.
- Application, API, CI/CD, GitOps, and documentation delivery.
- Adoption and maintenance of the fourteen mandatory AeroSim project skills.
Gitea access
aerosim-maintainersincorp-v1-aerosimcovers four current project-organization repositories.aerosim-skill-maintainersincorp-v1-aerosim-skills-code-agentcovers all fourteen adopted skill repositories.jarvis-at-skic,root-at-skic,martynas-pazusis, andpiotrasmembership and effective repository assignments are verified in both teams.- Piotras maps to Gitea account
piotrasand has verified membership inaerosim-maintainersandaerosim-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.
Communication
Exactly seven AeroSim channels exist in dedicated category corp-v1-aerosim (1542627633123299359): general, scope, architecture, ui-ux, kanban, delivery, and releases. Channel IDs, permission overwrites, and history were preserved during migration; Hermes read access and lifecycle order were reverified. Existing purpose guidance, the pinned general introduction, and project automation records remain attached to the unchanged channel IDs.