Skip to content

Fleet Mission Control — Documentation

Two tracks, kept in sync. Pick the one that matches how you want to read about this system:

  • technical/ — full detail, file:line citations, architecture diagrams, CI gates, library references. For engineers working in this repo.
  • plain/ — the same system explained with analogies and no jargon. For anyone who wants to understand what this does and why, without reading code.
Topic Technical Plain
What this is / how it's built ARCHITECTURE.md OVERVIEW.md
Turning it on getting-started.md getting-started.md
Contributing contributing.md — (see technical)
Libraries/tools/patterns used references.md learn-more.md
Build history (living) making-of.md making-of.md

Diagrams

Every Mermaid diagram embedded in the pages above has its source mirrored under diagrams/ for independent editing (GitHub renders Mermaid natively — no build step). Two C4 diagrams (System Context, Containers) are additionally rendered to committed SVG via D2:

Other docs in this repo

These predate the two-track restructure and are frozen contracts / design records rather than living reference docs — both tracks above link into them where relevant, but they aren't duplicated into either track:

Build reports

BUILD-REPORT-FLT120.md, BUILD-REPORT-FLT122.md, BUILD-REPORT-FLT125.md, and BUILD-REPORT-FLT131.md at the repo root are the per-ticket build reports technical/making-of.md is written from — each states what was built, what was deliberately deferred, and how it was verified.