East Tennessee two-site farm business plan (package)¶
First-class entry for the decision-grade business plan: ~5-acre home base and ~120-acre production in East Tennessee, ~35-minute separation, family labor, phased enterprises, telemetry as capital, 10-year horizon. Detailed rubric, knowns/unknowns, and full tables live in the planning framework; this page is the stable navigation spine for readers and agents.
What changed — integration pass (2026-04)¶
This revision does not replace the package or reading order. It binds newer canonical doctrine and county/site intelligence into chapter pages so the narrative matches execution reality: local evidence + missing-data discipline, off-grid/WAN-optional sequencing, sensor architecture + checklist matrix, platform/backup/DR + observability trust bar, procedural standards routing, and clearer confidence boundaries (desk evidence vs parcel truth). Durable ledger: Business plan integration revision audit (2026-04).
Operational bar: The package is not “live” until Ready for execution passes—see Hostile internal review §7.
Canonical detail hub: East Tennessee two-site farm business plan — planning framework
Topic operations hub (telemetry, runbooks, comparisons): Two-site smart farm operations
Execution & pilots router (Phase 0–1 dossier, validation—without replacing this TOC): Business plan execution and pilot operations hub
Phase timeline (visual): East Tennessee two-site farm business plan — phase timeline
Modeled sites & systems (entities) — planning roles, not your deed: Five-acre home base (SITE_HOME), 120-acre production farm (SITE_FARM), Field telemetry network — two-site. Business shell (TN + federal compliance, not legal advice): Tennessee farm business compliance package · entity pattern router Farm business legal entity model. Page ownership (avoid analysis sprawl): Structural audit — page ownership, entity gaps, and hub routing.
Authority & execution evidence (regulatory / agency / extension — not parcel-specific facts): Authoritative execution evidence cluster — East Tennessee. Gap audit (what is still missing for execution-grade clarity): Execution readiness gap audit — East Tennessee operational knowledge. Evidence hardening audit (2026-04 desk portals + routing; open gaps): Tennessee two-site — evidence hardening audit (2026-04). Vocabulary (canonical vs supporting vs exploratory): Evidence grade and canonical authority. Operator contract (ingest activation, Evidence summaries, structural vs integration validation): AGENTS.md.
Site intelligence (named anchors): Router (county vs place vs validation vs gaps): Local site and county intelligence. Analyses: Claxton home base — Anderson County (SITE_HOME), Demory farm — Campbell County (SITE_FARM), Anderson vs Campbell — operating implications. Parcel worksheets (structured fields; evidence-backed only): Parcel intelligence package — East Tennessee two-site. Local field evidence (measured vs reported; execution tables): Local evidence package — East Tennessee two-site — site/infrastructure/utility/loads baselines, field observation templates, parcel evidence workflow. Folded into canonical chapters (2026-04-22): two-site operating model, recommended enterprise strategy, capital plan, revenue model, risk register, validation/pilot plan, execution dossier (90d/12m/24m), spatial model, labor model, smart-tech strategy—no duplicate package pages.
Reading order (core narrative)¶
Execution, pilots, and first 24 months¶
Integration ledger (2026-04): Business plan integration revision audit — material plan deltas vs doctrine/evidence packages.
Start here (Phase 0–1 dossier): Execution dossier hub — read order: Decision memo → Execution gates — Phase 0–1 (EG gate tables; pilot vs production) → First 90 days → First 90 days — operator packet (weeks 1–12 runbook) → Master checklist → First 12 months → First 24 months.
Validation and pilot plan — first 24 months— full validation matrix + cheap proofs (detail)Pilot and recon checklists— copy-paste rows
Operational artifacts (fillable matrices)¶
Linked from the framework; same targets as Two-site smart farm operations Operations & logistics / Resilience tables.
Two-site operating model — 5 ac / 120 acConnectivity strategy — Claxton home base and Demory farm site— Canonical WAN (Starlink, LTE, terrestrial); pilot vs scale; security and degraded hooks.Execution topology package — two-site smart farm (Mermaid)— Reference / pilot / degraded diagrams; trust zones; runbook links.- Demory /
SITE_FARMoff-grid-first (solar + battery; mesh-first; WAN optional):Off-grid systems doctrine package — Demory(first-class hub),Demory farm — site intelligence(Off-grid-first section),Off-grid power doctrine — Demory,Power domains and battery-backed tiers — Demory,Field-node classes — Demory,Connectivity dependency map — Demory,Local-first / WAN-optional — Demory,Mesh and field networking — off-grid Demory,Farm sensor architecture — Demory,Sensor checklist matrix — Demory farm,Off-grid infrastructure stop rules,Off-grid degraded modes,Off-grid farm execution topology (Mermaid),Meshtastic vs HaLow vs Wi‑Fi. Execution tie-in:First 90 days(Demory parallel rules),Validation planoff-grid gates. Family labor model and coverage matrixInstrumentation priority matrixCapital phasing table — years 0–10Business risk registerManual fallback and degraded modesValidation backlog — before major spend
Financial planning layer (methodology; evidence fills placeholders)¶
Enterprise unit economics — worksheet methodologyCAPEX, OPEX, and enterprise sequencingFarm accounting baselineRevenue milestone modelExecution gates — financial thresholds— Fin-G(0→1) … Fin-G(3→4); consolidates pass/fail vs M0–M4Instrumentation ROI modelAutomation stop rules
Business shell — entity, tax, insurance, labor (Tennessee + federal)¶
Router: Tennessee farm business compliance package — LLC path, EIN/responsible party, TNTAP + ag exemption research, greenbelt per county, insurance checklist (UT W1266), DOL/TN DOL labor routing, BOI/FinCEN status note, compliance calendar.
Critique, remediation, and source campaign¶
Wiki / repository wiring (merge order, not farm economics)¶
Smart Farm Wiki — repository implementation plan— file tree, minimum merge set, phased repo work.Business plan wiki — Git-friendly execution sequence— PR batches and landing order.