Skip to content

Execution dossier — Phase 0–1 (East Tennessee two-site)

Purpose

Single entry for the pilot-grounded operating package through Phase 0–1 (roughly months 0–24 on the roadmap, with most families still before or at G1 by month 24). Use this page first, then open only the slice you need.

Stance: Execution = cheap proofs, small pilots, kill criteria—not premature scale.

Sources: Validation backlog and decision gates (V1–V12, G1–G3), Execution gates — Phase 0–1 (East Tennessee two-site) (EG domain pass/fail, pilot vs production), Validation and pilot plan — first 24 months, Pilot and recon checklists, Validation — before major spend.

Package integration (2026-04): Business plan integration revision audit — ledger of doctrine/evidence → canonical business-plan chapters (same package spine).

Read order (minimal hopping)

Order Page Use when
1 Decision memo — Phase 0–1 Today—what is allowed, pilot-only, forbidden
1b Execution gates — Phase 0–1 (East Tennessee two-site) Pass/fail by domain (EG tables); pilot vs production stance before expanding spend
2 First 90 days Narrative arc (days 1–90 bands + connectivity)
2a First 90 days — operator packet (East Tennessee two-site) Canonical weeks 1–12 runbook: priorities, field bundles, stops, checkpoints
3 Master checklist One ordered list—land, infra, business, telemetry, labor
4 First 12 months After day 90—quarterly rhythm
5 First 24 months Full arc + G1 prep window
6 Validation and pilot plan Full validation matrix + cheap proofs table (detail)
7 Pilot and recon checklists Copy-paste rows into your tracker
8 Field verification program — Phase 0–1 (Claxton and Demory) Site work tied to validation tasks and gates: walks, roads, drainage, utilities, power, sensors, gateways, permits

Demory SITE_FARM field sensors (long-range RF, gateways, Starlink = WAN only—not field radio): Farm sensor architecture — Demory farm site · Sensor checklist matrix — Demory farm.

Calendar anchor (fill once)

Symbol Meaning
T0 Execution start date (family-declared)—all windows below are relative to T0

Homelab / edge stack (optional)

When execution includes a Pi + k3s homelab or farm-edge gateway aligned with the smart-farm platform story: How to provision k3s, Longhorn, and Rancher on a Raspberry Pi fleet (stay in P0/P1 scope unless gates justify HA).

Ready for execution: the plan is operational

Treat the wiki package as operational (not merely “written”) only when all are true. This is stricter than having pages filled—it is behavioral and evidence-based. Cross-check: Hostile internal review §7, Remediation §4 P0/P1.

A. Governance and honesty

B. Labor and surge (labor optimism killed)

  • V11: 8+ week hour log complete including one stress/surge window.
  • Weekly DOW template explicitly treated as hypothesis until surge measured (Labor model).
  • Coverage matrix shows who covers overload—or hired/neighbor row non-empty.

C. Truth before scale (narrative optimism killed)

D. Technology optimism killed

  • G8 path: manual water (or critical) baseline log complete before actuation talk.
  • One telemetry pilot only; triage hours tracked vs trip savings (ROI, Stop rules).

E. Financial and insurance illusions killed

If any box is unchecked, the plan is documentation, not operational control.

Domain gates (EG): Cross-check A–E above with the composite stance table in Execution gates — Phase 0–1—especially before claiming G1 in production posture.