docs(adr): ADR-083 — per-cluster Pi compute hop (proposed) - #428
Merged
Conversation
Adopt one Pi per cluster of 3-6 ESP32-S3 sensor nodes as the canonical fleet-shape, rather than the full three-tier (dual-MCU + per-node Pi) shape. Sensor nodes are unchanged from ADR-028 / ADR-081; the cluster Pi gains the responsibilities the ESP32-S3 cannot carry — pose-grade ML inference, QUIC backhaul to gateway/cloud, and a cluster-level OTA + secure-boot anchor. The cluster-Pi shape is the L3-hybrid path identified in docs/research/architecture/decision-tree.md §2 — the cheapest viable upgrade. The full three-tier shape remains the long-term exploration target, gated behind no_std CSI maturity (decision-tree L4) and per-node ISR-jitter evidence (L2). Status: Proposed. Acceptance gated on: 1. Cross-compile to aarch64 / armv7 with workspace tests passing 2. 3-sensor + 1-Pi field test demonstrating end-to-end CSI → fusion → cloud at <=100 ms cluster latency 3. Cluster-Pi SoC choice ADR (decision-tree L6) approved References: - docs/research/architecture/three-tier-rust-node.md (seed exploration) - docs/research/architecture/decision-tree.md (L3 hybrid path) - docs/research/sota/2026-Q2-rf-sensing-and-edge-rust.md (SOTA evidence) Co-Authored-By: claude-flow <ruv@ruv.net>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adopt one Pi per cluster of 3-6 ESP32-S3 sensor nodes as the canonical RuView mid-scale deployment shape, rather than the full three-tier (dual-MCU + per-node Pi) shape from
docs/research/architecture/three-tier-rust-node.md.This is the L3-hybrid path identified in
docs/research/architecture/decision-tree.md§2 — the cheapest viable upgrade. Sensor nodes are unchanged from ADR-028 / ADR-081; the cluster Pi gains the responsibilities the ESP32-S3 cannot carry:quinn+rustlsis mature on Linux but does not run on ESP32-class hardware in any production-grade form (SOTA §5).Status
Proposed — not committing to implementation. Acceptance gated on:
aarch64-unknown-linux-gnu/armv7-unknown-linux-gnueabihfwith workspace tests passingWhat this ADR does NOT decide
no_stdCSI maturity (decision-tree.md L4) — not required for the cluster-Pi shape; only required for dual-MCU.Validation in this PR
v2/(rebased on top of chore(repo): rename rust-port/wifi-densepose-rs → v2/ (flatten to one level) #427's rename merge).Test plan
docs/research/architecture/three-tier-rust-node.md,decision-tree.md,sota/2026-Q2-rf-sensing-and-edge-rust.md)🤖 Generated with claude-flow