frank/ruvnet--RuView
1
0
Fork 0
mirror of https://github.com/ruvnet/RuView synced 2026-07-24 17:43:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: happiness scoring pipeline with ESP32 swarm + Cognitum Seed coordinator

Browse Source 
ADR-065: Hotel guest happiness scoring from WiFi CSI physiological proxies.
ADR-066: ESP32 swarm with Cognitum Seed as coordinator for multi-zone analytics.

Firmware:
- swarm_bridge.c/h: FreeRTOS task on Core 0, HTTP client with Bearer auth,
  registers with Seed, sends heartbeats (30s) and happiness vectors (5s)
- nvs_config: seed_url, seed_token, zone_name, swarm intervals
- provision.py: --seed-url, --seed-token, --zone CLI args
- esp32-hello-world: capability discovery firmware for 4MB ESP32-S3 variant

WASM edge modules:
- exo_happiness_score.rs: 8-dim happiness vector from gait speed, stride
  regularity, movement fluidity, breathing calm, posture, dwell time
  (events 690-694, 11 tests, ESP32-optimized buffers + event decimation)
- ghost_hunter.rs standalone binary: 5.7 KB WASM, feature-gated default pipeline

RuView Live:
- --mode happiness dashboard with bar visualization
- --seed flag for Cognitum Seed bridge (urllib, background POST)
- HappinessScorer + SeedBridge classes (stdlib only, no deps)

Examples:
- seed_query.py: CLI tool (status, search, witness, monitor, report)
- provision_swarm.sh: batch provisioning for multi-node deployment
- happiness_vector_schema.json: 8-dim vector format documentation

Verified live: ESP32 on COM5 (4MB flash) registered with Seed at 10.1.10.236,
vectors flowing, witness chain growing (epoch 455, chain 1108).

Co-Authored-By: claude-flow <ruv@ruv.net>
This commit is contained in:
ruv
2026-03-20 18:32:10 -04:00
parent 8a84748a83
commit a2d1739c07
21 changed files with 3067 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/adr/ADR-065-happiness-scoring-seed-bridge.md
+234
View File
@@ -0,0 +1,234 @@
# ADR-065: Hotel Guest Happiness Scoring -- WiFi CSI + Cognitum Seed Bridge
**Status:** Proposed
**Date:** 2026-03-20
**Deciders:** @ruvnet
**Related:** ADR-040 (WASM edge modules), ADR-039 (edge intelligence), ADR-042 (CHCI), ADR-064 (multimodal ambient intelligence), ADR-060 (multi-node aggregation)
## Context
Hotels lack objective, privacy-preserving methods to measure guest satisfaction in real time. Current approaches (post-stay surveys, NPS scores) are delayed, biased toward extremes, and capture less than 10% of guests. Meanwhile, ambient RF sensing can infer behavioral cues that correlate with comfort and well-being -- without cameras, wearables, or any guest interaction.
### Hardware
Two ESP32-S3 variants are deployed:
| Device | Flash | PSRAM | MAC | Port | Notes |
|--------|-------|-------|-----|------|-------|
| ESP32-S3 (QFN56 rev 0.2) | 4 MB | 2 MB | 1C:DB:D4:83:D2:40 | COM5 | Budget node, uses `sdkconfig.defaults.4mb` + `partitions_4mb.csv` |
| ESP32-S3 | 8 MB | 8 MB | -- | COM7 | Full-featured node, existing deployment |
Both run the Tier 2 DSP firmware with presence detection, vitals extraction, fall detection, and gait analysis.
### Cognitum Seed Device
A Cognitum Seed unit is deployed on the same network segment:
- **Address:** 169.254.42.1 (link-local)
- **Hardware:** Raspberry Pi Zero 2 W
- **Firmware:** 0.7.0
- **Vector store:** 398 vectors, dim=8
- **API endpoints:** 98 (REST, fully documented)
- **Sensors:** PIR, reed switch (door), vibration, ADS1115 ADC (4-ch analog), BME280 (temp/humidity/pressure)
- **Security:** Ed25519 custody chain with tamper-evident witness log
The Seed's 8-dimensional vector store and drift detection engine make it a natural aggregation point for behavioral feature vectors extracted from CSI data.
### Existing WASM Edge Modules
The following modules already run on-device and produce features relevant to happiness scoring:
| Module | Event IDs | Outputs |
|--------|-----------|---------|
| `exo_emotion_detect.rs` | 610-613 | Arousal level, stress index |
| `med_gait_analysis.rs` | 130-134 | Cadence, stride length, regularity |
| `ret_customer_flow.rs` | 410-413 | Entry/exit count, direction |
| `ret_dwell_heatmap.rs` | 420-423 | Dwell time per zone |
## Decision
### 1. New WASM Module: `exo_happiness_score.rs`
Create a new WASM edge module that fuses outputs from existing modules into an 8-dimensional happiness vector, matching the Seed's vector dimensionality (dim=8).
**Event ID registry (690-694):**
| Event ID | Name | Description |
|----------|------|-------------|
| 690 | `HAPPINESS_VECTOR` | Full 8-dim happiness vector emitted per scoring window |
| 691 | `HAPPINESS_TREND` | Windowed trend (rising/falling/stable) over last N vectors |
| 692 | `HAPPINESS_ALERT` | Score crossed a configured threshold (low satisfaction) |
| 693 | `HAPPINESS_GROUP` | Aggregate score for multi-person zone |
| 694 | `HAPPINESS_CALIBRATION` | Baseline recalibration event (new guest check-in) |
### 2. Happiness Vector Schema (8 Dimensions)
Each dimension is normalized to [0.0, 1.0] where 1.0 = maximal positive signal:
| Dim | Name | Source | Derivation |
|-----|------|--------|------------|
| 0 | `gait_speed` | `med_gait_analysis` (130) | Normalized walking velocity. Brisk = positive. |
| 1 | `stride_regularity` | `med_gait_analysis` (131) | Low stride-to-stride variance = relaxed gait. |
| 2 | `movement_fluidity` | CSI phase jerk (d3/dt3) | Low jerk = smooth, unhurried movement. |
| 3 | `breathing_calm` | Vitals BR extraction | BR 12-18 at rest = calm. Deviation penalized. |
| 4 | `posture_openness` | CSI subcarrier spread | Wide phase spread across subcarriers = open posture. |
| 5 | `dwell_comfort` | `ret_dwell_heatmap` (420) | Moderate dwell in amenity zones = engagement. |
| 6 | `direction_entropy` | `ret_customer_flow` (410) | Low entropy = purposeful movement. Wandering penalized. |
| 7 | `group_energy` | Multi-target CSI clustering | Synchronized movement of 2+ people = social engagement. |
The composite scalar happiness score is the weighted L2 norm:
```
score = sum(w[i] * v[i] for i in 0..7) / sum(w[i])
```
Default weights are uniform (all 1.0), configurable via NVS or Seed API.
### 3. ESP32 to Seed Bridge
```
ESP32-S3 (CSI) Cognitum Seed (169.254.42.1)
+------------------+ +----------------------------+
| Tier 2 DSP | | |
| + WASM modules | UDP 5555 | /api/v1/store/ingest |
| exo_happiness |──────────────| (POST, 8-dim vector) |
| _score.rs | | |
| | | /api/v1/drift/check |
| |◄─────────────| (drift alerts via webhook) |
| | | |
| | | /api/v1/witness/append |
| | | (Ed25519 audit trail) |
+------------------+ +----------------------------+
```
**Data flow:**
1. ESP32 runs CSI capture at 20+ Hz and feeds subcarrier data through existing WASM modules.
2. `exo_happiness_score.rs` collects outputs from emotion, gait, flow, and dwell modules every scoring window (default: 30 seconds).
3. The 8-dim happiness vector is packed as a 32-byte payload (8x float32) and sent via UDP to port 5555 on 169.254.42.1.
4. A lightweight bridge task on the Seed receives the UDP packet and POSTs it to `/api/v1/store/ingest` with metadata (room ID, timestamp, MAC).
5. The Seed's drift detection engine monitors the happiness vector stream and flags anomalies (sudden drops, sustained low scores).
6. Every ingested vector is appended to the Seed's Ed25519 witness chain, providing a tamper-proof audit trail.
### 4. Seed Drift Detection for Happiness Trends
The Seed's built-in drift detection compares incoming vectors against a rolling baseline:
- **Check-in calibration:** When a new guest checks in, event 694 resets the baseline.
- **Drift threshold:** Configurable (default: cosine distance > 0.3 from baseline triggers alert).
- **Trend window:** Last 20 vectors (~10 minutes at 30s intervals).
- **Alert routing:** Seed webhook notifies hotel management system when happiness trend is declining.
### 5. RuView Live Dashboard Update
`ruview_live.py` gains a `--seed` flag:
```bash
python ruview_live.py --port COM5 --seed 169.254.42.1 --mode happiness
```
This mode displays:
- Real-time 8-dim radar chart of the happiness vector
- Scalar happiness score (0-100) with color coding (red/yellow/green)
- Trend sparkline over the last hour
- Seed witness chain status (last hash, chain length)
- Room-level aggregate when multiple ESP32 nodes report
### 6. Architecture
```
+------------------------------------------+
| Hotel Room |
| |
| [ESP32-S3] [Cognitum Seed] |
| COM5 or COM7 169.254.42.1 |
| 4MB or 8MB flash Pi Zero 2 W |
| | | |
| | WiFi CSI | PIR, reed, |
| | 20+ Hz | BME280, |
| v | vibration |
| +-----------+ | |
| | Tier 2 DSP| v |
| | presence | +-------------+ |
| | vitals | | Seed API | |
| | gait | | 98 endpoints| |
| | fall det | | 398 vectors | |
| +-----------+ | dim=8 | |
| | +-------------+ |
| v ^ |
| +-----------+ UDP 5555 | |
| | WASM edge |─────────────┘ |
| | happiness | |
| | score | Drift alerts |
| | (690-694) |◄────────────── |
| +-----------+ /api/v1/drift/check |
| |
+------------------------------------------+
|
| MQTT / HTTP
v
+------------------+
| Hotel Management |
| System / RuView |
| Live Dashboard |
+------------------+
```
### 7. 4MB Flash Support
The 4MB ESP32-S3 variant (COM5) is officially supported for happiness scoring. The existing `partitions_4mb.csv` and `sdkconfig.defaults.4mb` from ADR-265 provide dual OTA slots (1.856 MB each), sufficient for the full Tier 2 DSP firmware plus `exo_happiness_score.wasm` (estimated < 40 KB).
Build for 4MB variant:
```bash
cp sdkconfig.defaults.4mb sdkconfig.defaults
idf.py build
```
The WASM module loader selects which modules to instantiate based on available heap. On the 4MB/2MB PSRAM variant, happiness scoring runs with a reduced scoring window (60s instead of 30s) to conserve memory.
### 8. Privacy Considerations
- **No cameras.** All sensing is RF-based (WiFi subcarrier amplitude/phase).
- **No facial recognition.** Happiness is inferred from movement patterns, not expressions.
- **No audio capture.** Breathing rate is extracted from chest wall displacement via RF, not microphone.
- **No PII stored on device.** Vectors are anonymous; room-to-guest mapping lives only in the hotel PMS.
- **Seed witness chain** provides auditable proof of what data was collected and when, satisfying GDPR Article 30 record-keeping requirements.
- **Guest opt-out:** A physical switch on the ESP32 node (GPIO connected to a toggle) disables CSI capture entirely. The Seed's reed switch can also serve as a "privacy mode" trigger (door-mounted magnet removed = sensing paused).
- **Data retention:** Vectors are retained on the Seed for the duration of the stay plus 24 hours, then purged. The witness chain retains hashes (not vectors) indefinitely for audit.
### 9. API Integration
Key Cognitum Seed endpoints used:
| Endpoint | Method | Purpose |
|----------|--------|---------|
| `/api/v1/store/ingest` | POST | Ingest 8-dim happiness vector |
| `/api/v1/store/query` | POST | Retrieve vectors by room/time range |
| `/api/v1/drift/check` | GET | Check if current vector drifts from baseline |
| `/api/v1/drift/configure` | PUT | Set drift threshold and window size |
| `/api/v1/witness/append` | POST | Append event to Ed25519 custody chain |
| `/api/v1/witness/verify` | GET | Verify chain integrity |
| `/api/v1/sensors/bme280` | GET | Room temperature/humidity (comfort correlation) |
| `/api/v1/sensors/pir` | GET | PIR presence (cross-validate with CSI) |
## Consequences
### Positive
- Provides real-time, objective guest satisfaction measurement without surveys or wearables.
- Reuses four existing WASM modules -- the happiness module is a fusion layer, not a rewrite.
- The Seed's 8-dim vector store is a natural fit; no schema changes needed.
- Ed25519 witness chain satisfies hospitality industry audit requirements and GDPR record-keeping.
- Both 4MB and 8MB ESP32-S3 variants are supported, enabling low-cost deployment at scale (~$8 per room for the 4MB node).
- Seed's environmental sensors (BME280, PIR) provide complementary context (room temperature, humidity) that can be correlated with happiness scores.
- No cloud dependency -- all processing is local (ESP32 edge + Seed link-local network).
### Negative
- Happiness inference from movement patterns is a proxy, not a direct measurement. Correlation with actual guest satisfaction must be validated empirically.
- The 4MB variant has reduced scoring frequency (60s vs 30s) due to memory constraints.
- UDP transport between ESP32 and Seed is unreliable; packets may be lost. Mitigation: sequence numbers and a small retry buffer on the ESP32 side.
- Link-local addressing (169.254.x.x) limits the Seed to the same network segment as the ESP32. Multi-room deployments need one Seed per subnet or a routed bridge.
- Drift detection thresholds require per-property tuning; a luxury resort has different movement patterns than a budget hotel.
- The system cannot distinguish between guests in a multi-occupancy room without additional multi-target CSI clustering, which is experimental (ADR-064, Tier 3).
docs/adr/ADR-066-esp32-swarm-seed-coordinator.md
+274
View File
@@ -0,0 +1,274 @@
# ADR-066: ESP32 CSI Swarm with Cognitum Seed Coordinator
**Status:** Proposed
**Date:** 2026-03-20
**Deciders:** @ruvnet
**Related:** ADR-065 (happiness scoring + Seed bridge), ADR-039 (edge intelligence), ADR-060 (provisioning), ADR-018 (CSI binary protocol), ADR-040 (WASM runtime)
## Context
ADR-065 established a single ESP32-S3 node pushing happiness vectors to a Cognitum Seed at `169.254.42.1` (Pi Zero 2 W, firmware 0.7.0). The Seed is now on the same WiFi network (`RedCloverWifi`, `10.1.10.236`) as the ESP32 node (`10.1.10.168`).
The Seed already exposes REST APIs for:
- Peer discovery (`/api/v1/peers`) — 0 peers currently registered
- Delta sync (`/api/v1/delta/pull`, `/api/v1/delta/push`) — epoch-based replication
- Reflex rules (`/api/v1/sensor/reflex/rules`) — 3 rules (fragility alarm, drift cutoff, HD anomaly indicator)
- Actuators (`/api/v1/sensor/actuators`) — relay + PWM outputs
- Cognitive engine (`/api/v1/cognitive/tick`) — periodic inference loop
- Witness chain (`/api/v1/custody/epoch`) — epoch 316, cryptographically signed
- kNN search (`/api/v1/store/search`) — similarity queries across the full vector store
A hotel deployment requires multiple ESP32 nodes (lobby, hallway, restaurant, rooms) coordinated as a swarm with centralized analytics on the Seed.
## Decision
Implement a Seed-coordinated ESP32 swarm where each node operates autonomously for CSI sensing and edge processing, while the Seed serves as the swarm coordinator for registration, aggregation, drift detection, cross-zone inference, and actuator control.
### Architecture
```
ESP32 Node A ESP32 Node B ESP32 Node C
(Lobby) (Hallway) (Restaurant)
node_id=1 node_id=2 node_id=3
10.1.10.168 10.1.10.xxx 10.1.10.xxx
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ WiFi CSI │ │ WiFi CSI │ │ WiFi CSI │
│ Tier 2 DSP │ │ Tier 2 DSP │ │ Tier 2 DSP │
│ WASM Tier 3 │ │ WASM Tier 3 │ │ WASM Tier 3 │
│ Swarm Bridge │ │ Swarm Bridge │ │ Swarm Bridge │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ HTTP POST │ HTTP POST │ HTTP POST
│ (happiness vectors, │ │
│ heartbeat, events) │ │
└──────────┬───────────────┴──────────────────────────┘
│
▼
┌───────────────┐
│ Cognitum Seed │
│ (Coordinator) │
│ 10.1.10.236 │
├───────────────┤
│ Vector Store │ ← 8-dim vectors tagged with node_id + zone
│ kNN Search │ ← Cross-zone similarity ("which room matches?")
│ Drift Detect │ ← Global mood trend across all zones
│ Witness Chain │ ← Tamper-proof audit trail per node
│ Reflex Rules │ ← Trigger actuators on swarm-wide patterns
│ Cognitive Eng │ ← Periodic cross-zone inference
│ Peer Registry │ ← Node health, last-seen, capabilities
└───────────────┘
```
### Swarm Protocol
#### 1. Node Registration (on boot)
Each ESP32 registers with the Seed via HTTP POST on startup. The Seed's peer discovery API tracks active nodes.
```
POST /api/v1/store/ingest
{
"vectors": [{
"id": "node-1-reg",
"values": [0,0,0,0,0,0,0,0],
"metadata": {
"type": "registration",
"node_id": 1,
"zone": "lobby",
"mac": "1C:DB:D4:83:D2:40",
"ip": "10.1.10.168",
"firmware": "0.5.0",
"capabilities": ["csi", "tier2", "presence", "vitals", "happiness"],
"flash_mb": 4,
"psram_mb": 2
}
}]
}
```
#### 2. Heartbeat (every 30 seconds)
```
POST /api/v1/store/ingest
{
"vectors": [{
"id": "node-1-hb-{epoch}",
"values": [happiness, gait, stride, fluidity, calm, posture, dwell, social],
"metadata": {
"type": "heartbeat",
"node_id": 1,
"zone": "lobby",
"uptime_s": 3600,
"csi_frames": 72000,
"free_heap": 317140,
"presence_now": true,
"persons": 2,
"rssi": -60
}
}]
}
```
#### 3. Happiness Vector Ingestion (every 5 seconds when presence detected)
```
POST /api/v1/store/ingest
{
"vectors": [{
"id": "node-1-h-{epoch}-{ts}",
"values": [0.72, 0.65, 0.80, 0.71, 0.55, 0.60, 0.85, 0.45],
"metadata": {
"type": "happiness",
"node_id": 1,
"zone": "lobby",
"timestamp_ms": 1742486400000,
"persons": 2,
"direction": "entering"
}
}]
}
```
#### 4. Cross-Zone Queries (Seed-side)
The Seed can answer questions across the entire swarm:
```
POST /api/v1/store/search
{"vector": [0.8, 0.7, 0.9, 0.8, 0.6, 0.7, 0.9, 0.5], "k": 5}
Response: nearest neighbors across all zones, showing which
rooms had the most similar mood to a "happy" reference vector.
```
#### 5. Reflex Rules for Swarm Patterns
Configure the Seed's reflex engine to act on swarm-wide patterns:
| Rule | Trigger | Action | Use Case |
|------|---------|--------|----------|
| `low_happiness_alert` | Mean happiness < 0.3 across 3+ nodes for 5 min | Activate `alarm` relay | Staff alert: guest dissatisfaction |
| `crowd_surge` | Presence count > 10 across lobby + hallway | PWM indicator brightness 100% | Lobby congestion warning |
| `zone_drift` | Drift score > 0.5 on any node | Log to witness chain | Trend change documentation |
| `ghost_anomaly` | Event 650 (anomaly) from any node | Notify + log | Security: unexpected RF disturbance |
### ESP32 Firmware: Swarm Bridge Module
New module `swarm_bridge.c` added to the CSI firmware, activated via NVS config:
```c
typedef struct {
char seed_url[64]; // e.g. "http://10.1.10.236"
char zone_name[16]; // e.g. "lobby"
uint16_t heartbeat_sec; // Default: 30
uint16_t ingest_sec; // Default: 5
uint8_t enabled; // 0 = disabled, 1 = enabled
} swarm_config_t;
```
NVS keys (provisioned via `provision.py --seed-url http://10.1.10.236 --zone lobby`):
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| `seed_url` | string | (empty) | Seed base URL; empty = swarm disabled |
| `zone_name` | string | `"default"` | Zone identifier for this node |
| `swarm_hb` | u16 | 30 | Heartbeat interval (seconds) |
| `swarm_ingest` | u16 | 5 | Vector ingest interval (seconds) |
The swarm bridge runs as a FreeRTOS task on Core 0 (separate from DSP on Core 1):
```
swarm_bridge_task (Core 0, priority 3, stack 4096)
├── On boot: POST registration to Seed
├── Every 30s: POST heartbeat with latest happiness vector
├── Every 5s (if presence): POST happiness vector
└── On event 650+ (anomaly): POST immediately
```
HTTP client uses `esp_http_client` (already in ESP-IDF, no extra dependencies). JSON is formatted with `snprintf` (no cJSON dependency needed for the small payloads).
### Node Discovery and Addressing
Nodes find the Seed via:
1. **NVS provisioned URL** (primary) — `provision.py --seed-url http://10.1.10.236`
2. **mDNS fallback** — Seed advertises `_cognitum._tcp.local`; ESP32 resolves `cognitum.local`
3. **Link-local fallback** — `http://169.254.42.1` when connected via USB
### Vector ID Scheme
```
{node_id}-{type}-{epoch}-{timestamp_ms}
```
Examples:
- `1-reg` — Node 1 registration
- `1-hb-316` — Node 1 heartbeat at epoch 316
- `1-h-316-1742486400000` — Node 1 happiness vector at epoch 316, timestamp T
- `2-h-316-1742486401000` — Node 2 happiness vector at same epoch
### Witness Chain Integration
Every vector ingested into the Seed increments the epoch and extends the witness chain. The chain provides:
- **Per-node audit trail** — filter by node_id metadata to get one node's history
- **Tamper detection** — Ed25519 signed, hash-chained; break = detectable
- **Regulatory compliance** — prove "sensor X reported Y at time Z" for disputes
- **Cross-node ordering** — Seed epoch gives total order across all nodes
### Scaling Considerations
| Nodes | Vectors/hour | Seed storage/day | kNN latency |
|-------|---|---|---|
| 1 | 720 | ~1.5 MB | < 1 ms |
| 5 | 3,600 | ~7.5 MB | < 2 ms |
| 10 | 7,200 | ~15 MB | < 5 ms |
| 20 | 14,400 | ~30 MB | < 10 ms |
The Seed's Pi Zero 2 W has 512 MB RAM and typically an 8-32 GB SD card. At 30 MB/day for 20 nodes, storage lasts 250+ days before compaction is needed. The Seed's optimizer runs automatic compaction in the background.
### Provisioning for Swarm
```bash
# Node 1: Lobby (COM5, existing)
python provision.py --port COM5 \
--ssid "RedCloverWifi" --password "redclover2.4" \
--node-id 1 --seed-url "http://10.1.10.236" --zone "lobby"
# Node 2: Hallway (future device)
python provision.py --port COM6 \
--ssid "RedCloverWifi" --password "redclover2.4" \
--node-id 2 --seed-url "http://10.1.10.236" --zone "hallway"
# Node 3: Restaurant (future device)
python provision.py --port COM8 \
--ssid "RedCloverWifi" --password "redclover2.4" \
--node-id 3 --seed-url "http://10.1.10.236" --zone "restaurant"
```
## Consequences
### Positive
- **Zero infrastructure** — no cloud, no server, no database. Seed + ESP32s + WiFi router is the entire stack
- **Autonomous nodes** — each ESP32 runs full Tier 2 DSP independently; Seed loss degrades gracefully to local-only operation
- **Cryptographic audit** — witness chain gives tamper-proof history for every observation across all nodes
- **Real-time cross-zone analytics** — Seed kNN search answers "which zones are happy/stressed right now" in < 5 ms
- **Physical actuators** — Seed's relay/PWM outputs can trigger real-world actions (lights, alarms, displays) based on swarm-wide patterns
- **Horizontal scaling** — add ESP32 nodes by flashing firmware + running provision.py; no Seed reconfiguration needed
- **Privacy-preserving** — no cameras, no audio, no PII; only 8-dimensional feature vectors stored
### Negative
- **Single point of aggregation** — Seed failure loses cross-zone analytics (nodes continue autonomously)
- **WiFi dependency** — nodes must be on the same network as the Seed; no mesh/LoRa fallback yet
- **HTTP overhead** — REST/JSON adds ~200 bytes overhead per vector vs raw binary UDP; acceptable at 5-second intervals
- **Pi Zero 2 W limits** — 512 MB RAM, single-core ARM; adequate for 20 nodes but not 100+
- **No WASM OTA via Seed** — currently WASM modules are uploaded per-node; future work could use Seed as WASM distribution hub
### Future Work
- **Seed-initiated WASM push** — Seed distributes WASM modules to all nodes via their OTA endpoints
- **mDNS auto-discovery** — nodes find Seed without provisioned URL
- **Mesh fallback** — ESP-NOW peer-to-peer when WiFi is down
- **Multi-Seed federation** — multiple Seeds for multi-floor/multi-building deployments
- **Seed dashboard** — web UI on the Seed showing live swarm map with per-zone happiness