Wiki navigation and structural hubs¶
Purpose: Reduce flat-list fatigue in index.md by naming where to start for meta/IA, two-site operations, homelab edge, and audits. This page is a router, not a duplicate of every analysis.
IA policy & debt: Structural debt audit — wiki IA and operational maturity · AGENTS.md (canonicalization, page_subtype, operational_maturity).
Operational standards (farm & homelab)¶
| Page | Use when |
|---|---|
Operational standards — farm and homelab platform |
Catalog of Pi, k3s, storage, secrets, backup cadence, field naming, gateways, site boundaries |
Raspberry Pi fleet provisioning standard — smart farm / homelab |
Every node checklist |
Kubernetes edge — scheduling, storage class, and Longhorn roles standard |
Labels, defaults, taints |
Site-to-site network role boundaries standard |
Zones, SITE_* roles, WAN vs local |
Procedural guides (how-tos and runbooks)¶
| Page | Use when |
|---|---|
Procedural guides package strategy — Smart Farm Wiki |
Contract: where guides live (analyses/), vs standards/essays, operational_maturity, required links (architecture, standards, entities) |
How to provision k3s, Longhorn, and Rancher on a Raspberry Pi fleet |
Guide hub — Pi edge stack bootstrap sequence (page_subtype: operational_guide) |
Backup and disaster recovery package — smart farm stack |
DR doctrine spine — operator routing across backup tracks |
Runbook — backup validation and recovery drill |
Example incident/drill runbook (runbook-*.md) |
Incident runbooks (degraded mode): Runbook — broker or backhaul down, Runbook — power loss at remote site, Runbook — sensor false-positive alert triage, Runbook — manual fallback irrigation, gates, pumps.
Five package hubs (start here for “whole topics”)¶
| Hub | Use when |
|---|---|
Platform doctrine package — homelab / farm edge |
k3s / Longhorn / Rancher / Pi doctrine and provisioning pointers |
Backup and disaster recovery — doctrine hub |
farmOS / Postgres / etcd / Longhorn backup and restore navigation |
Off-grid power and field networking hub |
Demory off-grid doctrine + two-site WAN + field RF routing + Farm sensor architecture — Demory |
Local site and county intelligence |
Claxton / Demory / Anderson / Campbell evidence and parcel gaps |
Business plan execution and pilot operations hub |
Phase 0–1 execution dossier, pilots, V*/G*—not the full strategy TOC |
Onboarding and terminology¶
| Page | Use when |
|---|---|
Start here — Smart Farm Wiki |
First visit—fast paths without reading analyses |
How to read this wiki |
Layers, page types, how to use the catalog |
Smart Farm Wiki glossary (hub) |
Vocabulary (gates, SoR, two-site, off-grid, platform) |
Wiki overview |
North-star + optional deep orientation list |
Entity layer — operating objects¶
| Page | Use when |
|---|---|
Entity layer — operating objects gap audit |
Audit: what entities were for; what this pass added |
Field node classes (G/R/S/H/W) |
Off-grid roles (not SKUs) |
RF and telemetry gateway roles vs WAN edge and backhaul roles |
Disambiguate field vs internet gateways |
Backup and restore tier labels |
Tier 0–3 DR vocabulary |
Kubernetes edge control-plane roles |
k3s / etcd / Rancher boundaries |
index.md |
Full Entities list including labor, markets, infrastructure categories |
Backup / disaster recovery¶
| Page | Use when |
|---|---|
Backup and disaster recovery — doctrine hub |
Router—start here for DR navigation |
Backup and disaster recovery package — smart farm stack |
Canonical spine (same story as hub; full prose) |
Disaster recovery decision rules — farm edge stack |
Incidents: what failed, what to restore first, execution alignment |
Runbook — backup validation and recovery drill |
Restore-tested drills |
Meta, audits, and steering¶
| Page | Use when |
|---|---|
Usability and navigation audit — 2026-04-18 |
Reader UX: flat index pain, hub strength, source-note scanability; pairs with structural audits |
Source-note abstract and evidence pattern |
Authoring: optional Evidence summary block for cluster source-notes |
Domain content overview |
Strand map, maturity matrix, backlog |
Repository analysis |
Repo layout, CI, MkDocs, validation |
Structural audit — repository shape and canonical routing |
Merge policy, index IA |
Structural audit — page ownership, entity gaps, and hub routing |
Anti–analysis-swarm ownership map |
Structural debt audit — wiki IA and operational maturity |
Sprawl diagnosis, ops maturity taxonomy |
Execution readiness gap audit — East Tennessee |
ET execution evidence gaps |
Source authority hardening audit |
Provenance: forums/blogs vs official clusters; backlog |
Tennessee two-site — evidence hardening audit (2026-04) |
Desk portals, infra/observability routing, open gaps; complements execution readiness audit |
Raw corpus vs wiki synthesis — evidence surfacing audit (2026) |
raw/processed/ depth vs visible synthesis; theme gaps + Evidence-summary priorities |
Package artifact backlog — canonical East Tennessee packages |
Matrices / standards / runbooks / checklists gaps + Evidence summary queue for remaining clusters |
Two-site smart farm (East Tennessee package)¶
| Page | Role |
|---|---|
Two-site smart farm operations |
Main hub: business plan links, telemetry, runbooks, ownership table |
East Tennessee two-site farm business plan (package) |
Reading order spine |
Business plan execution and pilot operations hub |
Execution / pilots router (memo, 90d, validation) |
Reference architecture — 5 ac + 120 ac |
Architecture package map |
Execution dossier — Phase 0–1 (hub) |
Pilot execution entry (canonical analysis) |
Off-grid systems — Demory farm (SITE_FARM)¶
| Page | Role |
|---|---|
Off-grid power and field networking hub |
Umbrella router (Demory doctrine + two-site WAN + field links) |
Sub-GHz field networking — synthesis |
Single-file index: LoRaWAN / Meshtastic / HaLow, WAN vs field RF, links to comparisons and sources |
Off-grid systems doctrine package — Demory |
First-class hub: power domains, field-node classes, WAN deps, degraded modes, stop rules |
Off-grid power doctrine — Demory |
Solar+battery default; always-on vs duty-cycled; networking as load |
Power domains and battery-backed infrastructure tiers — Demory |
Pcrit / Popt; T0–T3 tiers |
Field-node classes and communication roles — Demory |
G/R/S/H/W roles (architecture, not SKUs) |
Connectivity dependency map — farm systems (Demory) |
What must work without WAN |
Local-first / WAN-optional operating model — Demory |
Operating posture; pilot vs scale |
Off-grid degraded modes — power and connectivity (Demory) |
P1/P2/N1/N2 failure classes |
Off-grid infrastructure stop rules — Demory |
DR-* rules; simplification triggers |
Mesh and field networking — off-grid Demory |
Layering; Meshtastic vs HaLow vs Wi‑Fi |
Off-grid farm execution topology (Mermaid) |
Reference / pilot / degraded diagrams |
Homelab / edge Kubernetes (Pi, k3s, Longhorn)¶
| Page | Role |
|---|---|
Platform doctrine package — homelab / farm edge |
First-class hub: strategy, HA semantics, k3s/Longhorn/Rancher roles, storage comparison, approved vs deferred |
Observability, secrets, and trust bar — homelab / farm edge |
Alert routing, SOPS/Flux, optional Alloy, remote trust bar |
Platform strategy for farm and homestead services |
Canonical stack narrative (same file; alias old long title) |
Platform decision memo — phase, HA scope, deferrals |
Governance: Phase 0/1 vs deferred |
HA meaning and constraints — homelab / farm platform |
What HA does / does not mean here |
k3s role in the homelab / farm platform, Longhorn role in the homelab / farm platform |
Component boundaries |
How to provision k3s, Longhorn, and Rancher on a Raspberry Pi fleet |
Operational guide hub (page_subtype: operational_guide) |
Docker, Kubernetes, Compose, and Bake |
Distro / compose context |
Runbooks and degraded modes (two-site)¶
| Page | Role |
|---|---|
Automation degraded modes and manual fallback SOP |
Parent SOP |
Manual fallback and degraded modes — critical operations |
Scenario matrix |
Runbook — broker or backhaul down |
MQTT / uplink |
Runbook — power loss at remote site |
Field hub power |
Full catalog¶
The authoritative flat list remains index.md (required for validation and discoverability). Use this hub to choose a lane first.