Business plan execution and pilot operations — hub¶
Purpose: Router for Phase 0–1 execution, pilots, validation (V*), and gates (G*)—distinct from the strategic narrative chapters in the business plan package. Use this when you are doing the work, not reading the thesis.
What this hub owns: Where to start for execution artifacts and how they relate to the package hub. It does not duplicate the full chapter TOC—that stays on East Tennessee two-site farm business plan (package).
What it does not own: Financial thresholds as live numbers—those are worksheets and family evidence; the wiki holds structure and gates, not your bank account.
Start here¶
| Reader goal | Open |
|---|---|
| Pilot / Phase 0–1 — single entry | Execution dossier — Phase 0–1 (hub) |
| What is allowed today | Decision memo — Phase 0–1 execution |
| First 90 days | First 90 days — Phase 0–1 execution |
| Full validation matrix + T0 windows | Validation and pilot plan — first 24 months |
| Strategic package (chapters, roadmap, economics) | East Tennessee two-site farm business plan (package) |
| Business shell — entity, tax, insurance, labor, BOI | Tennessee farm business compliance package |
Canonical (durable scope)¶
| Page | Role |
|---|---|
East Tennessee two-site farm business plan (package) |
Navigation spine for strategy, reading order, links to execution |
East Tennessee two-site farm business plan — planning framework |
Rubric, document tree, knowns/unknowns |
Execution dossier — Phase 0–1 (hub) |
Execution spine: memo → EG gates → 90d → checklist → 12m → 24m |
Execution gates — Phase 0–1 (East Tennessee two-site) |
EG domain pass/fail; pilot vs production; G1 production composite |
Validation backlog and decision gates |
V* tasks and G* gates (cross-check with dossier) |
Business plan integration revision audit (2026-04) |
Ledger: doctrine/evidence packages bound into canonical chapters—not a parallel plan |
Supporting analyses and artifacts¶
| Page | Role |
|---|---|
Master checklist — Phase 0–1 |
One ordered list |
First 12 months — Phase 0–1, First 24 months — Phase 0–1 |
Horizons after day 90 |
Pilot and recon checklists — first 24 months |
Copy-paste rows |
Validation backlog — before major spend |
$-sensitive gate framing |
Execution gates — financial thresholds |
Phase 0→4 G thresholds (methodology) |
Phase 0–1 operator burden review — East Tennessee two-site (hostile) |
Skeptical labor/triage/off-grid/backup stack; pairs EG gates + R17 |
First 90 days — operator packet (East Tennessee two-site) |
Weeks 1–12 pilot runbook: priorities, field bundles, stops, evidence 30/60/90 |
Operational topic (broader than execution only): Two-site smart farm operations — ownership table for telemetry, runbooks, business-plan links.
Related hubs¶
Local site and county intelligence— Claxton / Demory evidence and parcel gapsOff-grid power and field networking hub— Demory parallel execution rulesPlatform doctrine package — homelab / farm edge— optional Pi/k3s alignment with executionWiki navigation and structural hubs