Strategic audit — decision-safe operations for a two-site smart farm¶

Purpose: Ruthlessly assess whether this wiki is sufficient to support a future ~5-acre homestead plus ~120-acre farming business ~35 minutes away, both relying on smart tech, automation, telemetry, edge compute, and resilient infrastructure—and to list what data, synthesis, and artifacts must be added before the vault can act as a decision-safe operational brain (not just a document collection).

Scope: Evaluates the repository as a planning system. Distinguishes source-note accumulation, genuine synthesis, reusable operational decision support, and executable architecture. Does not invent capabilities not present in the corpus; uncertainty is called out.

Related meta

• Information architecture — decision-safe operational brain (target design) — target IA: top-level layers, hubs, cross-linking rules, orphans, migration plan.
• Business viability and farm economics — gap analysis (strategic audit) — revenue, enterprise, channels, staffing, insurance, accounting, CAPEX/OPEX, logistics, risk; prioritized business pages; under-modeled decisions.
• Smart technology architecture audit (strategic audit) — telemetry, radios, edge, HA/farmOS/MQTT/TSDB, time, identity, registry, alerting, observability, firmware, degraded modes, security, remote access; fragmentation, reference outline, SOPs, diagrams.
• Agentic wiki improvement prompts (staged, strategic audit) — Pre-prompt + Phase 1–4 agent prompts (foundational → operational → resilience → optimization) with deliverables and acceptance criteria.
• Implementation backlog — strategic audit (P0–P3) — prioritized artifacts, effort, dependencies, and top 10 pages to build first.
• Domain content overview — strand map; this audit extends the “Gaps and growth directions” section with an actionable backlog.
• Knowledge synthesis — entry points across the vault.
• Repository analysis — repo mechanics vs domain content.

1. Executive judgment¶

The vault is strong as a knowledge architecture (raw → source-notes → topics/concepts/analyses, explicit strand map, honest gap callouts in Domain content overview). It is not yet a decision-safe operations system for a two-site, instrumented farm business. Strength is breadth (LPWAN/mesh, solar, farmOS pointer, livestock/garden captures, hydrology, roads). Weakness is thin connective tissue: the wiki already states that pages tying soil/crop decisions to sensor placement and data models are sparse compared to standalone source-notes (Domain content overview — Gaps and growth directions). Synthesis exists in pockets (Timing on the farm — synthesis, Agritourism business plan — guest hub on 120 acres, family home 35 min away, road-erosion analyses, Homestead composting — practical guide). Operational decision support (SOPs, runbooks, asset registry schemas, staffing math, unit economics, security models) is largely missing. Executable architecture (canonical diagrams, telemetry schema, firmware lifecycle, observability) is mostly absent beyond hubs and captures.

2. What the wiki already covers well¶

3. Critical gaps¶

4. Missing integration layers¶

1. Technology ↔ land units: Radio topics rarely tie to paddock boundaries, gates, distance/elevation—the gap is named in Domain content overview.
2. farmOS / records ↔ telemetry: Farm data, farmOS… and sensor topics are adjacent, not integrated (no canonical event → asset → location pattern).
3. Business ↔ operations: Tennessee hobby farm… does not link into labor routing, equipment, or telemetry ROI.
4. Homestead ↔ farm site: Strong link mainly in Agritourism business plan…; Smart home — Matter, Thread… is not tied to farm alerting / on-call.
5. Roads / water / power: Not one resilience graph (if road fails, feed and vet access fail).
6. Biological plan ↔ measurement: Multi-field crop rotation plan mentions distant parcels briefly; no sensor/soil-test loop per field.

5. Missing artifacts to add (backlog)¶

Groupings below are targets for ingest + synthesis, not promises of current content.

Analyses¶

Comparisons¶

Concepts¶

Entities¶

Topics¶

Timelines¶

Templates / checklists / SOPs¶

Architecture docs¶

6. Priority roadmap¶

7. Top 10 decisions not yet supported confidently¶

1. Which enterprises justify fixed infrastructure on 120 ac vs contracting—without unified economics.
2. Which stack is authoritative when farmOS, HA, and a DB disagree.
3. Staffing model for livestock welfare at 35 min (beyond guest-oriented coverage).
4. Single vs dual energy/comms budget for two parcels—no consolidated architecture.
5. Security posture for cameras, VPN, MQTT, remote actuators.
6. Carrying capacity / forage plan for ruminants (prompt only).
7. Market channel under TN rules—pointers only.
8. Instrumentation priority (which acres, which risks first).
9. Insurance for public, employees, volunteers, two parcels.
10. Manual operations when automation is wrong or offline—no runbook layer.

8. Verdict¶

Already helps with: Orienting on tech vocabulary, strand navigation, and one worked dual-site agritourism narrative (Agritourism business plan…); partial decisions on roads, compost, water, time, power themes.

Dangerously close but not ready: Acting as system-design authority for sensors + backhaul + records; replacing extension, vet, attorney, accountant, engineer; “hands-off 120 acres” via automation without a validated architecture.

Must be built for decision-safe use: Owned spatial/asset model (even simple); one reference architecture for telemetry + data + alerts with degraded modes; SOP/runbook layer; financial/enterprise synthesis beyond pointers; non-agritourism dual-site model if that is the real business.

This page is a living backlog: update it when major hubs land or when gap severity shifts.