Project Architecture Documents Index
Navigation guide to the project-wide architecture documents.
Project Architecture Documents Index
Navigation guide to all project-wide architecture documents.
Quick Links by Role
For RF Engineers
Start here: Node DSP Pipeline -> Shared Antenna Capabilities -> Ground Station Backend
For Backend Developers
Start here: Project Architecture Overview -> Ground Station Backend -> Shared APIs & Contracts
For Frontend Developers
Start here: Ground Station Frontend -> Ground Station Control Surface Design -> Shared APIs & Contracts
For Product & Operators
Start here: Project Operational Flow -> Project Deployment & Risks -> Project Architecture Overview
All Documents
Overview & Planning
| Document | Purpose | Audience |
|---|---|---|
| Project Architecture Overview | Whole-project architecture, goals, baseline capabilities | All |
| Project End-to-End | Use cases, hardware inventory, software placement | All (intro) |
| Project Reasoning Notes | Design rationale for scope boundaries and tier separation | Decision makers |
| Project Gaps & Deferred Decisions | Unresolved decisions tracked for ADR follow-up | Architects |
Technical Specifications
| Document | Purpose | Audience |
|---|---|---|
| Shared APIs & Contracts | Endpoint families, payload schemas, parameter binding | Backend devs |
| Node DSP Pipeline | Why raw DSP stays out of Python | RF engineers |
| Shared Antenna Capabilities | Antenna types, tracking modes, multi-emitter handling | RF/Integration |
| Ground Station Backend | Central responsibilities, node coordination, normalization | Backend architects |
| Ground Station Frontend Architecture | Browser shell, roles, page layout, interaction model | Frontend lead |
| Ground Station Control Surface Design | Capability-driven UI patterns, frame config, bindings | Frontend devs |
Operational & Deployment
| Document | Purpose | Audience |
|---|---|---|
| Project Operational Flow | Data flows, mission states, runtime behavior | Operations |
| Project Deployment & Risks | MVP scope, technical risks, product risks, next steps | Product/Ops lead |
Navigation Notes
- Use the project section for whole-platform architecture.
- Use ground-station for the central server and browser UI.
- Use shared for contracts, schemas, and other cross-cutting references.
- Use node for antenna-side implementation and DSP internals.