Skip to content

Field-node classes and communication roles — Demory farm site

Purpose: Architecture-level classes for field nodes (roles , not product SKUs ) : what each class does in the local-first network , typical power posture , and WAN dependence . Pair with Mesh and field networking — off-grid Demory and Meshtastic vs HaLow vs Wi‑Fi .**

Doctrine package: Off-grid systems doctrine package — Demory.

Node classes (roles)

Class Communication role Typical power WAN required?
G — Gateway / spine Aggregates mesh/LPAN → MQTT or local broker; buffer when cloud absent Battery-backed from Pcrit / T1 tier No for local delivery
R — Mesh repeater Extends range; may not see all sensors alone Solar + small local pack ; often duty-cycled No
S — Sensor leaf Sparse telemetry ; LoRa / mesh leaf mW–W class ; event or slow cadence No
H — Sub-GHz IP bridge HaLow / 802.11ah segment for IP devices where LoRa is too slow Higher than S ; budget airtime + sleep No for LAN segment
W — WAN edge Starlink / LTE CPE; egress Sheddable (not Pcrit default )** Yes for cloud path only

Role diagram

```mermaid flowchart TB subgraph field["Field — battery / solar at each node"] S1["S — sensor leaf"] R1["R — repeater"] S2["S — sensor leaf"] end

subgraph spine["Spine — Pcrit-backed"] G["G — gateway"] broker["Local broker / SoR edge"] end

subgraph barn["Barn LAN"] nvr["NVR / laptop — policy"] end

subgraph optional["Optional overlay"] W["W — WAN CPE"] end

S1 --> R1 --> G S2 --> R1 G --> broker broker --> nvr broker -.-> W ```

Pilot discipline (Phase 0–1)