Skip to content

Overview

This vault is a structured synthesis layer on top of immutable raw sources. The agent’s job is to compound knowledge: entities, concepts, timelines, and analyses linked with stable paths and explicit provenance. Purpose and voice for Smart Farm Wiki are stated in concepts/smart-farm-wiki-mission-and-values.md.

Start here (pick one lane)

Lane First pages
East Tennessee two-site (business plan, execution, parcels) Start here → East Tennessee two-site farm business plan (package) → Two-site smart farm operations
Platform / backup / homelab edge Platform doctrine package — homelab / farm edge · Backup and disaster recovery — doctrine hub · Operational standards — farm and homelab platform
Meta (how to read, evidence, navigation health) How to read this wiki · Evidence grade and canonical authority · Wiki navigation and structural hubs · Usability and navigation audit — 2026-04-18

The full flat catalog is index.md. Do not treat the Business plan or Analyses sections of index.md as a linear reading list—use package hubs and canonical pages first.

Onboarding (read first)

Deeper orientation (optional)

  1. index.md — full catalog; log.md — chronological work; source-notes ground claims in raw/processed/.
  2. Repo / publishing: analyses/repository-analysis.md; operator handbook: docs/ at repo root.
  3. Domain strands: analyses/domain-content-overview.md.
  4. IA / audits: analyses/information-architecture-decision-safe-operations.md, analyses/strategic-audit-decision-safe-operations.md, analyses/implementation-backlog-strategic-audit.md.
  5. East Tennessee two-site package: business-plan/east-tennessee-two-site-farm-business-plan.md; topics/local-site-and-county-intelligence.md; topics/two-site-smart-farm-operations.md; repo wiring: analyses/smart-farm-wiki-repository-implementation-plan.md.
  6. Structure / ownership: analyses/structural-audit-repository-and-canonical-routing.md, AGENTS.md, analyses/structural-audit-page-ownership-entity-gaps-and-hub-routing.md; operating-object entities: analyses/entity-layer-operating-objects-gap-audit.md; source authority: analyses/source-authority-hardening-audit.md.
  7. Execution readiness (no invented parcel facts): analyses/execution-readiness-gap-audit-east-tennessee-operational-knowledge.md; agency ingests: source-notes/authoritative-execution-evidence-cluster-east-tennessee.md; ingest visibility: analyses/ingest-visibility-gap-authoritative-evidence-east-tennessee.md. Raw vs synthesis depth: analyses/raw-corpus-evidence-surfacing-audit-2026.md.
  8. Package hubs (avoid flat analysis lists): topics/wiki-navigation-and-structural-hubs.md — platform, backup/DR, off-grid + field RF, local site intelligence, execution & pilots.
  9. Operational standards (repeatable norms): topics/operational-standards-farm-homelab-platform.md — Pi, k3s, storage/secrets, observability, backup cadence, field/WAN naming, site-to-site boundaries.
  10. Procedural guides (how-tos and runbooks): topics/procedural-guides-package-strategy-smart-farm-wiki.md — where they live, vs standards, operational_maturity, links to doctrine and entities.

Principles

  • Raw sources are evidence; the wiki is the maintained model.
  • Prefer incremental edits and explicit deprecation over silent rewrites.
  • Relative links keep Obsidian and validation tooling aligned.