Container Registry
This registry lists AeroSim's C2 containers and links one C3 Component view for each container.
| C2 container and C3 view | What it owns |
|---|---|
| Web Application | Sign-in session, pre-flight configuration, browser flight runtime, rendering, controls, warnings, outcomes, and API clients |
| API Service | Fastify routes, identity guard, catalogues, pilot services, Socket.IO, health, and Prisma access |
| Pilot Data Store | PostgreSQL schema for pilot linkage, preferences, progress, outcomes, and session metadata |
| Documentation Site | Docusaurus content, canonical-data rendering, editable diagrams, and static publication |
Boundary rules
@corp-v1-aerosim/flight-coreis a build-time component/library used by the Web Application, not a deployable container.- Keycloak, Gitea, Harbor, Gondor, and Project Pages remain external systems or platform services.
- The API Service is the only application access path to the Pilot Data Store.
Canonical functional and non-functional requirement readers expose behavior, quality constraints, and lifecycle status. A Proposed requirement remains unapproved even when implementation or Task evidence exists.