First 24 months — Phase 0–1 execution (East Tennessee two-site)¶
Purpose¶
Capstone narrative for T0 → T0+24 months: Phase 0–1 execution with pilot discipline. Aligns to roadmap Phases 0–2 overlap (10-year roadmap) but does not assume Phase 2 herd or fence MVP by month 24.
Entry: Execution dossier hub · First 90 days · First 12 months.
Detail layer: Validation and pilot plan (full matrix + cheap proofs). Connectivity validation (survey, power, WAN testing, remote access, Starlink may/must-not, cost stops): Validation plan § Connectivity validation.
Local evidence: By T0+24mo, either parcel-true soil/water maps exist for Claxton and Demory, or G1 waivers document why not—county NASS + vault WSS alone are not G1.
Windows (relative to T0)¶
| Window | Roadmap (approx.) | What “good” looks like |
|---|---|---|
| T0 → T0+90d | Phase 0 + start Phase 1 | Books, V8 path, V1/V3 started, V11 log, manual baseline on water started |
| T0+3mo → T0+12mo | Phase 1 | V2/V4/V5/V6 evidence, repair tier list, telemetry pilot ≤ one cluster |
| T0+12mo → T0+18mo | Phase 1 | G1 packet complete or dated waivers documented; pivot to lease if grazing fails |
| T0+18mo → T0+24mo | Phase 1 → possible early Phase 2 | G1 PASS → permission for fence/water/herd MVP per validation backlog—else stay pilot + cheap proofs |
Most families: Month 24 still in Phase 1 or early Phase 2 — normal.
Execution illusion to kill: G1 and Phase 2 permission do not follow the calendar. If month 24 arrives without evidence, you are still in Phase 1—not “behind schedule,” under-proof.
Decision points (do not skip)¶
| When | Decision | Evidence |
|---|---|---|
| T0+90d | Continue vs pause spend on recon | 90-day exit checklist (First 90 days) |
| T0+12mo | G1 ready for formal review ? | V1–V4 + V8 + V6 path |
| T0+18–24mo | Enter Phase 2 CAPEX ? | G1 PASS + major-spend rows |
| T0+12mo and T0+24mo (review) | WAN / Starlink recurring cost vs documented value proxy — continue / trim / freeze scope ? | Quarterly ledger lines + CS- on Automation stop rules ;* Validation plan § Connectivity |
What not to do by month 24 without gates¶
- Financed loader / hay line without hours proof + hire quote (
Remediation§3) - Second enterprise if V11 surge uncovered
- Telemetry fleet if triage > benefit (
Stop rules) - Second farm WAN terminal / redundant uplink without Phase 1 connectivity proof and capital gate (
Connectivity strategy,Capital plan) - Always-on field RF / HaLow / farm Starlink while DR-1 open (
Off-grid decision rules) — CS-5 onAutomation stop rules - Production trust in remote Demory visibility without MV-8 (local-only + SOC-stressed drill )**
- Expanding cloud / WAN-dependent automation while CS-1 / CS-2 (connectivity stops ) are red on
Automation stop rules