Off-grid infrastructure stop rules — power and networking (Demory farm)
Purpose
Executable stop rules and simplification triggers (placeholders allowed ) for when to add RF , power more CPE , or stop scaling telemetry at Demory — aligned with Automation stop rules (CS-5, MV-8) and** Connectivity validation.
Doctrine package: Off-grid systems doctrine package — Demory.
Rules (fill private thresholds)
| ID |
Rule |
| DR-1 |
No new always-on IP radio until P_NET_ALWAYS_W (or bracketed Wh/day for networking) is metered and budgeted against battery days of autonomy (placeholder). Stacks with Automation stop rules CS-5. |
| DR-2 |
No second farm WAN terminal until Connectivity strategy Phase 1 proof rows pass. |
| DR-3 |
If triage hours exceed trip savings for telemetry, freeze fleet (Stop rules)—off-grid does not exempt this. |
| DR-4 |
HaLow or new mesh hop only if Meshtastic vs HaLow vs Wi‑Fi shows ROI vs Meshtastic or Ethernet for that use case. |
| DR-5 |
Pilot phase: one gateway + one RF class + one WAN path maximum until G8 / V10 evidence is honest. |
Pilot vs later scale (summary)
| Phase |
Networking + power |
| 0–1 |
Measure loads; one mesh cluster; optional Starlink on a sheddable branch. |
| Later |
HaLow backhaul segments, redundant gateway, dual WAN only with O&M budget. |
Simplification triggers (de-scope before adding)
| Trigger |
Response |
P_NET or network Wh/day unmeasured vs battery days of autonomy |
Freeze new always-on radios (stacks with CS-5 )** |
| Triage hours > trip savings (DR-3) |
Freeze sensor fleet ; manual rounds first |
| MV-8 drill fails (local-only / SOC-stressed )** |
No new automation until drill passes |
| Second RF class before first is boring |
Violates DR-5 — stop adding hops |