First 12 months — Phase 0–1 execution (East Tennessee two-site)¶
Purpose¶
T0 → T0+12 months: deepen Phase 0–1 proofs without scaling into Phase 2 unless G1 is actually green (most families: prepare G1 in year 1, pass in year 2).
Spine: Execution dossier hub · First 90 days · Master checklist.
Connectivity validation (year 1) — obstruction re-check (leaf-on), WAN 90-day summary, remote access audit, quarterly WAN cost vs value: Validation and pilot plan § Connectivity validation.
Local evidence: Months 4–6 fence/road scoping on Campbell should assume earthwork and drainage may co-own the quote with perimeter—Demory site intelligence. V7 comps: cite 2024 NASS Anderson vs Campbell cropland rent estimates as ballpark (comparison).
Months 1–3 (overlap with “first 90 days”)¶
Finish anything open from the 90-day exit checklist. Priority: V2, V4, V5 completion toward 12-week sale bills; fence walk complete enough for repair tier list; water flow band honest.
Months 4–6 — Infrastructure truth + business paper¶
| Stream | Actions | Gates |
|---|---|---|
| Water | I2 flow/recovery notes; dry season plan if applicable | V2 progress |
| Fence | Repair tier list → scoped quotes only if G1 path clear | V3 |
| Carrying capacity | V4 conservative upper bound documented | G1 input |
| Markets | V5 12-week set complete; V7 lease comps if relevant | V5, V7 |
| Labor | W1 done; W3 weekly rhythm rev | V11 |
Forbidden: Full perimeter fence CAPEX without G1; owned herd above proven capacity; financed equipment without major-spend gates.
Months 4–12 — Connectivity validation (WAN / Starlink)¶
| Window | Do | Links |
|---|---|---|
| Months 4–6 | Leaf-on obstruction re-pass for SITE_HOME terminal / CPE (if trees ); complete power / grounding checklist before declaring WAN “ production ” |
Validation plan § Connectivity |
| Months 7–9 | First 90-day WAN reliability summary (outages, fade, LTE handoff ) filed ; V10 evidence updated beyond screenshots | V10 ; Runbook — broker or backhaul down drill optional |
| Months 10–12 | Remote access hardening review: inventory matches Remote access and operational security model before any second sensor cluster ; quarterly WAN cost vs value review (apply CS- if needed )* |
Automation stop rules |
Rules reminder: May depend on Starlink / WAN for convenience telemetry and egress ; must not depend on it for welfare proof or books without offline discipline — tables on Validation plan § Connectivity.
Demory / off-grid (year 1): Treat solar + battery + inverter headroom as a gating input for field networking—not only WAN. By T0+12mo, either DR-1 is satisfied (networking load bracketed) or CS-5 keeps new always-on RF/WAN scope frozen. Schedule MV-8 drill before declaring Demory telemetry production-trusted (Validation plan off-grid subsection, Capital plan off-grid sequencing).
Months 7–9 — Telemetry pilot discipline¶
| Actions | Success / kill |
|---|---|
| One pilot sensor path stable | T4 trip count before/after 4 weeks |
| T5 triage hours tracked | T6 kill if triage > benefit (ROI) |
| No fleet rollout | Automation stop rules |
Months 10–12 — G1 preparation (not automatic pass)¶
| Actions | Notes |
|---|---|
Assemble G1 evidence packet per validation backlog: V1–V4 minimum + legal use |
Date each row |
| V6 processing path credible for intended animal | Calls + range costs |
| V9 insurance review | Before financed gear (even if year 2 ) |
| V12 if debt: limits in writing | Capital plan |
Normal outcome: G1 ready to review at 12–18 months calendar—not forced by month 12.