Architecture decisions
editorial(governance): resolve architecture-decisions' standing 2026-08-02 ADR-16 flag (Track-B) — confirmed against system-udp/src/main.rs: real mechanism is a zero-broker UDP broadcast to a fixed subnet address (10.8.0.255) with client-side target-field filtering, not the claimed unicast-per-node delivery loop; the article's own 'incompatible with WireGuard' framing was backwards too — the real mesh runs the broadcast over the WireGuard-encrypted subnet directly; de-narrated per register-documentation.yaml, same fix applied to the ES pair
@@ -65,8 +65,8 @@ The systemd init system, required on current Debian cloud nodes, is formally cla **ADR-15 — Console pages are never cached.** All operator console pages are served with cache-disabling headers and versioned fetch parameters. The decision eliminates a failure mode that appears in regulated operational tools: a browser presenting a stale cached state of the console while the underlying data has changed. An operator acting on a cached console view may take an action based on information that no longer reflects the platform's state. The platform prevents this by construction rather than by operator discipline. **ADR-16 — Peer commands travel as unicast, not broadcast.** Commands sent to peer nodes in the platform's mesh network travel as individual unicast deliveries — one command per node — rather than as a network broadcast. Native UDP broadcast is incompatible with the WireGuard encrypted mesh the platform uses for inter-node communication. The unicast loop preserves delivery guarantees without requiring a separate broadcast layer. (Correction, 2026-08-02: this is factually reversed. The real `system-udp/src/main.rs`, verified on canonical `origin/main`, implements a literal `broadcast_intent()` function using `socket.set_broadcast(true)` to a hardcoded broadcast address `10.8.0.255` — a "Zero-Broker UDP Mesh," not a unicast loop. Flagged, not resolved.) **ADR-16 — Peer commands travel as a zero-broker broadcast, filtered by target.** Commands sent to peer nodes in the platform's mesh network travel over UDP broadcast to the mesh subnet's broadcast address — every node on the WireGuard-encrypted mesh receives every command, and the payload carries a `target` field each node uses to decide whether the command is addressed to it. There is no central broker relaying commands to individual nodes; the mesh has no single point of delivery failure. This trades network-level delivery privacy (any node can observe traffic addressed to any other) for a simpler mesh topology with no broker to keep available. **ADR-18 — The operator console is a heads-up display.** The operator console is designed as a heads-up display that bridges operators to the platform's derivative data architecture. Each function key maps to a distinct cartridge viewport — a bounded view of one part of the platform's data — rather than to a free-form interface. The design limits the surface area of each operator interaction, which reduces the categories of error an operator can introduce in a single session.