Rewrite as current state rather than how it was decided

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013kj58Jugkic783b8ZrtTVZ
This commit is contained in:
2026-09-04 15:23:09 +09:00
parent 8a10b2f6c0
commit 2924a4adf8
+4 -10
View File
@@ -5,14 +5,11 @@ updated: 2026-09-04
--- ---
# Initial plan # Initial plan
## The scope question, first ## Scope
This started as "aggregator and pusher to the tablet over USB". The pushing part Aggregation and the HTTP surface. **Not** a telemetry relay: over USB the tablet
may not need to exist: over USB the tablet has an IP link via RNDIS, and the has an IP link via RNDIS, and a client that can subscribe to the broker does so
architecture already says Class B devices reaching the bus over IP connect to the directly.
broker directly. A Flutter MQTT client can talk to mosquitto with no hop in between.
What does not go away:
| Job | Why it needs a gateway | | Job | Why it needs a gateway |
|---|---| |---|---|
@@ -21,9 +18,6 @@ What does not go away:
| Static assets | Serving the PMTiles basemap to the display | | Static assets | Serving the PMTiles basemap to the display |
| Non-IP transports | BT SPP and plain serial for ESP32 clients have no broker access | | Non-IP transports | BT SPP and plain serial for ESP32 clients have no broker access |
So: build the aggregation and the HTTP surface. Do not build a telemetry relay for
clients that can already subscribe for themselves.
## Order ## Order
1. Static file serving for the basemap — smallest useful thing, unblocks the map. 1. Static file serving for the basemap — smallest useful thing, unblocks the map.