Skip to content

Off-grid systems doctrine package — Demory farm site (SITE_FARM)

Purpose: First-class doctrine for SITE_FARM at Demory (Campbell County): off-grid-first electrical architecture (solar + batteries default), resilient local networking (mesh / sub-GHz where justified), WAN as optional overlay, explicit degraded modes, field-node classes, and stop rules — without inventing kW / Ah / SKU choices (those are local engineering after measured loads ).**

Business plan spine: East Tennessee two-site farm business plan (package) · Execution dossier — Phase 0–1 · First 90 days (Demory parallel rules).

Provenance hub: Off-grid power, field RF, and optional WAN — source index.

Umbrella router (off-grid + field RF + two-site WAN—without replacing this page): Off-grid power and field networking hub.

Integration / package boundary: New off-grid or field RF sources must activate into Off-grid power, field RF, and optional WAN — source index and the analyses linked in the Doctrine map (power doctrine, mesh strategy, degraded modes, stop rules) when DR-* stop rules, node-class, or WAN assumptions change. Sensors specifics: Farm sensor architecture — Demory farm site + Sensor checklist matrix — Demory farm—this doctrine page routes to them; it does not duplicate the full sensor matrix.

What this hub owns

  • Full doctrine for off-grid-first SITE_FARM at Demory: power domains, G/R/S/H/W node classes, WAN as overlay, degraded modes, DR-* stop rules.
  • Diagrams and read order for Demory-specific analyses below.

Start here

Goal Page
Read the doctrine in order Follow Doctrine map (next section)—row 1 is Off-grid power doctrine — Demory
Two-site WAN (both sites, not only Demory) Connectivity strategy — Claxton & Demory via Off-grid power and field networking hub

Canonical vs supporting

Canonical (this package) Supporting
Rows 1–7 in Doctrine map Comparisons, Mermaid-only pages, Loads register (placeholders)

Doctrine map (read order)

# Page Role
1 Off-grid power doctrine — Demory farm site Policy: off-grid-first stance; always-on vs duty-cycled; networking as load
2 Power domains and battery-backed infrastructure tiers — Demory Pcrit / Popt ; tiers tied to network spine
3 Field-node classes and communication roles — Demory · Entity Field node classes (G/R/S/H/W) RF / gateway / sensor roles (not a shopping list )**
4 Connectivity dependency map — farm systems (Demory) What requires WAN vs what must not
5 Local-first / WAN-optional operating model — Demory Operating posture ; pilot vs scale
6 Off-grid degraded modes — power and connectivity P1 / P2 / N1 / N2 failure classes
7 Off-grid infrastructure stop rules — Demory DR- rules ; simplification triggers ; links CS-5 / MV-8*

Diagrams: Off-grid farm execution topology — Demory (Mermaid) · Mesh and field networking — off-grid Demory · Connectivity strategy — Claxton & Demory.

Field sensing (SITE_FARM) — long-range sensors, gateways, Starlink as WAN only: Farm sensor architecture — Demory farm site · Sensor checklist matrix — Demory farm · LoRaWAN vs Wi‑Fi HaLow vs Meshtastic — Demory farm sensor layer · Demory farm sensor layer — official and operator-grade source cluster.

Loads register (site-specific placeholders): Loads register — two sites.

End-to-end doctrine (Mermaid)

```mermaid flowchart TB subgraph power["Power — solar + battery default"] pv["PV array"] batt["Battery / BMS"] inv["Inverter / DC buses"] pcrit["Pcrit bus — must stay up"] popt["Popt / sheddable"] end

subgraph localnet["Local-first network"] mesh["Mesh / LoRa / sub-GHz"] gw["Field gateway spine"] lan["Barn LAN / Ethernet"] end

subgraph wan["WAN — optional overlay"] starlink["Starlink / LTE CPE"] cloud["Cloud / admin"] end

pv --> batt --> inv inv --> pcrit inv --> popt pcrit --> gw mesh --> gw gw --> lan gw -. optional .-> starlink starlink -.-> cloud ```

Reading: Solid lines are required for local operations ; dotted WAN path is discretionary Wh and ops .

Non-negotiables (summary)

Must work without WAN May use WAN when powered and policy allows
Welfare-related local interlocks (water, gates policy) Remote dashboards, OTA (if chosen), weather
At least one local path to verify critical state (sight, float, local UI) Starlink for coordination—not for sole welfare proof
Paper / offline record discipline for books Cloud egress of MQTT