Execution readiness gap audit — East Tennessee operational knowledge base¶
Purpose: Move the vault from a strong planning-and-synthesis system toward a more execution-ready operational knowledge base by naming what is still missing, where authority is unclear, and which canonical pages should absorb improvements—without inventing parcel-specific facts or spawning overlapping strategy essays.
Baseline: Published site structure (wiki/index.md, package hub, structural audits). Epistemic rule: Site-specific numbers (soil class, septic setbacks, cash rent per acre, tax outcomes) belong in your worksheets and citable sources—not in synthesized pages unless explicitly tied to a source-note or labeled assumption.
Companion pages: Evidence grade and canonical authority (signaling vocabulary), Authoritative execution evidence cluster — East Tennessee (source index), Structural audit — page ownership, entity gaps, and hub routing (anti–analysis-swamp policy).
Execution gate system (Phase 0–1): Execution gates — Phase 0–1 (East Tennessee two-site) — operational pass/fail by domain (EG IDs), pilot vs production; complements this gap audit (which names what is missing, not when spend may proceed).
1. Missing site-specific execution data¶
| Gap | Why it blocks execution | Fill strategy (no fake site facts) |
|---|---|---|
| Parcel soil capability (map unit, limiting factors, hydric flags) | Gates fence/water/crop/grazing assumptions | Use Web Soil Survey + SSURGO interpretation; ground-truth with county soil survey or consultant. Source cluster: WSS + elevation captures. |
| Elevation / drainage / wetness (DEM-derived flow paths, ponding risk) | Road/building/pasture layout; erosion | 3DEP / lidar-backed products + field observation. Same capture note; tie to Farm water infrastructure system. |
| Septic / SSDS / buildability (permit class, setbacks, soil morph) | Homestead expansion, shop, guest infrastructure | TDEC / county rules—not blog generalizations. Tennessee onsite sewage / septic captures. |
| County-level land economics (cash rent by practice) | Lease vs own vs custom hire; milestone realism | USDA NASS county tables (survey year explicit). NASS cash rents TN 2024, survey page capture. |
| TN tax posture (ag exemption, sales tax on inputs, agritourism exposure) | Cash planning; entity choice discussions | Primary: DOR publications. TN Revenue ag exemption PDF, Agricultural exemption capture, Public Chapter 498 (act text—not individualized tax advice). |
| Grazing / forage calendar + enterprise budgets | Stocking, hay, surge labor | Extension PB1663 calendar, UT budgets, Livestock Companion, NRCS GLCI excerpt. |
| FSA / credit / beginning-farmer programs (eligibility, timelines) | Capital plan gates | FSA program captures, Beginning farmer resources—apply through FSA/USDA, not wiki. |
| farmOS operational bindings (asset ↔ geometry ↔ log ↔ location) | SoR + spatial registry coherence | Official model docs + inbox captures: Assets, Logs, farmOS documentation captures. |
| Remote access / OT exposure (homelab ↔ field) | Security posture for telemetry | CISA: Guide to securing remote access (PDF), Joint guide OT cybersecurity asset inventory (PDF)—tie to Remote access and operational security model. |
2. Weak or under-modeled entities / layers¶
| Layer | Issue | Recommended canonical update |
|---|---|---|
| Parcels / land units | IDs described; soil + permit links underdeveloped | Farm parcels and land units — extended “authority chain” (WSS → map units → field verify). |
| farmOS product | Strong on Assets/Logs; Location + movement pattern from captures under-linked | farmOS — pointer to inbox doc captures. |
| Spatial registry | MAP_AUTHORITY_LABEL still often TBD |
Farm spatial model and asset registry standard — explicit external references subsection. |
| Glossary / timeline | Thin vs. volume of analyses | Add evidence grade glossary entry; phase timeline gains one evidence milestone row (see phase timeline). |
3. Mixed-authority source clusters (reader hazard)¶
| Cluster | Mixed content | Mitigation |
|---|---|---|
| Tennessee business / hobby | Listicles + DOR + news in same topic strand | Route decisions to primary PDFs/captures; keep listicles as exploratory in Tennessee hobby farm…. |
| Soil / “smart farming” | Vendor IoT + academic + extension | Operational claims (capacity, liming, rotation) → extension / NRCS; ML/sensor surveys → labeled exploratory. |
| Road / pond / homestead hydrology | Forum threads + handbook PDFs | Use forums for failure-mode color only; engineering claims need handbook / NRCS / PE. |
| Agritourism | Lifestyle blogs vs PC498 statute | Statute + DOR for tax/legal triggers; blogs for UX/marketing ideas only. |
4. Thin or hard-to-navigate layers¶
| Layer | Symptom | Fix |
|---|---|---|
| Onboarding | New readers see long index analysis lists |
Package hub + execution dossier + this audit as “start here” triad; see overview. |
| Glossary | Few entries vs. many named gates (G1, V*, Fin-G*) |
Evidence grade glossary + link from glossary hub. |
| Canonical vs exploratory | Analyses read as equal weight | Use Evidence grade and canonical authority vocabulary; business plan package lists canonical spine vs supporting. |
5. Pages or sections where canonical authority was unclear (resolved by routing)¶
| Reader confusion | Resolution |
|---|---|
| “Which page is the business plan?” | Package hub east-tennessee-two-site-farm-business-plan; framework = rubric child. |
| “Where is distance tax definitive?” | Two-site operations model — 5 ac / 120 ac + Trip policy. |
| “Where is telemetry authority?” | Telemetry system of record — boundaries and authority + Reference architecture. |
| “What sources back TN execution?” | Authoritative execution evidence cluster. |
6. Recommended canonical updates (prioritized)¶
P0 — structural (high value, low churn)
- Package hub — short Authority & execution evidence block (links to cluster + audit).
- Two-site operations topic — Regulatory & site evidence row pointing to cluster + WSS/septic/NASS.
- Farm spatial model — Authoritative land-intelligence references subsection.
- Capital plan — FSA / program references line (not application advice).
- Execution dossier hub — link this audit under Related.
P1 — entities
- Farm parcels — soil survey + permit authority chain (no parcel numbers).
- farmOS — documentation capture links for Location / Assets / Logs.
P2 — meta
- Domain content overview — pointer to this audit under steering / backlog.
- Phase timeline — one evidence milestone row.
Defer: New parallel “strategy” analyses; duplicate economics essays. Extend existing worksheets and remediation items instead.
7. Anti–analysis-swamp guardrails (restated)¶
- One durable owner per cluster per
Structural audit — page ownership…. - New operational content should attach to entity, artifact table, or validation ID—not float as a third narrative.
- Query syntheses stay time-stamped or fold into hubs when promoted to doctrine.