jarvis-at-skic
cd25976a3f
Build and publish Corp v1 steering documentation / build (push) Successful in 33s
35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
---
|
|
title: AeroSim Team
|
|
sidebar_position: 1
|
|
---
|
|
|
|
# AeroSim Team
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Status | Active |
|
|
| Lead | RootAtSkic |
|
|
| Verified technical member | `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 eight AeroSim project skills.
|
|
|
|
## Gitea access
|
|
|
|
- `aerosim-maintainers` in `corp-v1-aerosim` covers both project repositories.
|
|
- `aerosim-skill-maintainers` in `corp-v1-aerosim-skills-code-agent` covers all eight adopted skill repositories.
|
|
- `jarvis-at-skic` and `root-at-skic` membership and effective repository assignments are verified in both teams.
|
|
|
|
## Communication
|
|
|
|
Exactly three AeroSim channels exist under the `corp-v1` category: `general`, `architecture`, and `delivery`. Hermes access, guidance messages, the pinned general introduction, and three isolated same-project review jobs are verified. No additional `corp-v1-aerosim-*` channel exists.
|