jarvis-at-skic
2dc80c16e2
Build and publish Corp v1 Board portal / build (pull_request) Successful in 35s
37 lines
2.0 KiB
Markdown
37 lines
2.0 KiB
Markdown
---
|
|
title: AeroSim Team
|
|
sidebar_position: 1
|
|
---
|
|
|
|
# AeroSim Team
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Status | Active |
|
|
| Lead | RootAtSkic |
|
|
| Members | RootAtSkic; Panther Skeleton; MartynasP; Eduard; Linas; Jenny; Piotras; `jarvis-at-skic` / Hermes code agent |
|
|
| Assigned project | [AeroSim](/projects/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-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.
|
|
- 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.
|
|
|
|
## 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.
|