Diagrams

Mermaid source (.mmd) for every architectural diagram, plus rendered SVGs for the status / health / reconciliation flows where a static image is referenced from prose pages. The numbering reflects reading order, not file-system order.

To re-render SVGs from Mermaid source, use the Mermaid CLI:

npx --yes @mermaid-js/mermaid-cli -i 1-container-status-derivation.mmd -o 1-container-status-derivation.svg

How SHC turns raw Docker signals into SHC-level status and health states. Rendered SVGs are checked in because these are referenced from ../status-states.md.

• 1 — Container status derivation (.svg) — Docker state / health → SHC container status.
• 2 — Service status derivation (.svg) — aggregate of container statuses within a service.
• 3 — Service health derivation (.svg) — aggregate of container health within a service.
• 4 — Deployment status derivation (.svg) — event inputs + service-status aggregate → deployment status.
• 5 — Deployment health derivation (.svg) — aggregate of service healths → deployment health.
• 6 — Reconciliation decision (.svg) — when the reconciler takes action vs. leaves alone.

• 7 — Event flow (.svg) — Docker events → ingest → internal fan-out → SSE subscribers.
• 10 — Event propagation — how a Docker event on one node reaches subscribers on peer nodes.
• 15 — Runtime registration — sequence showing main.go wiring ctx, log, the registry, event bus, queue, and per-module task handlers at startup. Related: patterns/import-dag.

• 8 — High-level architecture — the whole system at a glance: internet → Nebula mesh → node daemons → Docker.
• 13 — Cluster topology — voting quorum vs. client nodes, leader/voter roles, overlay addressing.

Leader election is owned by Raft (the rqlite engine); SHC’s leader_hub subsystem polls the Raft leadership status and fans out leader-only callbacks. See core/daemon-manager.md.

• 12 — WebSocket exec — how shc stack exec on node A tunnels into a container on node B.

Service discovery is handled by Docker overlay DNS aliases (the three-tier network model in modules/network.md) plus Traefik labels auto-injected by compose enrichment. There is no separate service-discovery layer.

Referenced from ../patterns/import-dag.md. When you change the dependency structure of core modules, update the .mmd source here and re-render.

• 14 — Import architecture — the package dependency graph from core/scope/ and core/coded/ at the bottom up to the modules.
• 16 — Cycle elimination — before/ after comparison of each circular dependency that was unwound.