Business plan source-ingest campaign — East Tennessee two-site package¶
Scope: Minimum authoritative sources to reduce uncertainty on the completed ET two-site business plan package—not maximum volume.
Anchors: Planning framework, Remediation backlog, Hostile internal review.
Principles: Prefer primary and Extension / agency documents over generic blogs. Optimize for decision support (gates, numeric bands, legal triggers). Do not ingest broad inspirational or “smart farm vision” material unless it directly changes a gate, budget line, or risk owner.
1. Campaign goals¶
| Goal | Success looks like |
|---|---|
| G1 — Enterprise economics | At least one TN-relevant enterprise budget or budget methodology per major enterprise path under consideration, with line items mappable to revenue model and capital plan. |
| G2 — Production + conservation physics | Grazing / forage / water guidance sufficient to defend carrying capacity bands, fence + water sequencing, and NRCS practice choices in recommended strategy and capital phasing. |
| G3 — Compliance surface | County / state pointers for structures, transport, on-farm sales / agritourism (if ever on-path), captured as citable notes—enough to stop treating V8 as a wiki placeholder. |
| G4 — Telemetry as OPEX | farmOS (or chosen stack) data model + ops docs grounded so smart-tech strategy and instrumentation matrix avoid fantasy schemas and double-counted labor. |
| G5 — Downside protection | Insurance / liability primers (rural or farm-specific where possible) tied to binder review and Phase 2 gates in risk register and validation backlog. |
| G6 — Market realism | Channel economics references (auctions, direct, processor) to support all-in per head and processing path rows—not optimistic price decks. |
| G7 — Books | IRS / extension farm recordkeeping and Schedule F–adjacent framing so “margin” claims in the wiki stay defensible (not tax advice—decision-grade clarity). |
Stop rule: If a candidate source does not advance G1–G7 for a named wiki section or validation ID (V1–V11), defer or skip.
2. Prioritized source categories (order of attack)¶
P0 — Must land before creditable scaling narrative: TN/ET enterprise budgets, Extension production guides (forage/beef/water), NRCS grazing + water + conservation planning, local regulatory capture (zoning / structures / transport).
P1 — Before telemetry fleet or salary claims: farmOS documentation, telemetry architecture (OPEX, alerts, integration boundaries), market-channel economics, insurance / liability.
P2 — When enterprise path includes on-farm sales / events / lodging: agritourism regulatory + liability; otherwise keep as optional backlog items, not bulk ingest.
P3 — Tax / accounting references: small set of stable IRS + Extension primers; avoid deep tax strategy content in wiki unless explicitly scoped.
3. Category briefs¶
3.1 East Tennessee / Tennessee enterprise budgets¶
| Field | Content |
|---|---|
| Questions to answer | What line-item structure do TN Extension or comparable budgets use? What yield / price assumptions are explicit? What owner labor is imputed vs cash? What working capital hints appear (feed, breeding stock, seasonal cash peaks)? |
| Strengthens | revenue model, revenue milestone model, enterprise options, capital plan |
| Prefer | UT Extension enterprise budgets, FM- / PB- / SP fact sheets with revision dates; USDA cost-return series when TN-specific is missing (note geography gap in synthesis). |
| Avoid | National “average farm” infographics; unattributed spreadsheet copies; any source that mixes hobby and commercial without labeling assumptions. |
Existing repo touchpoint: ut-extension-fm-boot-2017-budgets-velandia-pdf — use as template for future budget source-notes; do not treat 2017 alone as current numbers without refresh.
3.2 Tennessee Extension production guides¶
| Field | Content |
|---|---|
| Questions to answer | What management calendar and input assumptions apply to beef + forage systems in TN? What risk sections (drought, endophyte, internal parasite) change surge labor or feed costs? |
| Strengthens | labor model, family coverage matrix, recommended strategy, enterprise options |
| Prefer | UT Extension publications with numbers (rates, windows, thresholds); regional forage guides tied to fescue / warm-season reality in ET. |
| Avoid | Generic pasture poetry; copy-paste of entire manuals—extract only decision-useful sections into source-notes with page / section pointers. |
3.3 NRCS — grazing, water, conservation planning¶
| Field | Content |
|---|---|
| Questions to answer | What practices apply to water development, cross-fencing, piping, ponds, access—and what planning steps precede cost-share? What documentation does the agency expect (maps, grazing plan, engineering)? |
| Strengthens | capital plan, capital phasing, validation backlog (V2 / V4), risk register |
| Prefer | NRCS field office manuals / technical guides / state grazing initiatives; FY scenario summaries where they benchmark practice bundles. |
| Avoid | Third-party “NRCS hacks”; national blog summaries without document IDs—always anchor to agency PDF or official web capture in raw/ + source-note. |
Existing repo touchpoints: nrcs-tennessee-grazing-lands-glci-excerpt, nrcs-fy25-conservation-scenarios-pdf.
3.4 farmOS — data model and operations¶
| Field | Content |
|---|---|
| Questions to answer | What assets, logs, and quantities does farmOS actually model? What is API vs UI workflow? What does not belong in farmOS (finance, payroll) so the wiki does not conflate systems? |
| Strengthens | smart-tech strategy, instrumentation matrix, implementation backlog |
| Prefer | Official farmOS.org docs and versioned API references; small worked examples from project docs. |
| Avoid | Vendor “digital twin” whitepapers unless they map to one concrete integration decision; full stack tutorials that skip data ownership and backup burden. |
Existing repo touchpoints: farmos-model-assets-documentation, farmos-model-logs-documentation.
3.5 Smart agriculture — telemetry architecture¶
| Field | Content |
|---|---|
| Questions to answer | What reference architectures separate edge → broker → storage → alerting? What failure modes (power, LTE, false positives) are standard in industrial / ag IoT guidance? What security minimums apply to remote access to farm networks? |
| Strengthens | smart-tech strategy, manual fallback, business risk register, optional homelab ops checklist (if created) |
| Prefer | CISA OT / remote access primers; peer-reviewed or standards-body sensing stack papers when tied to deployment constraints; one good LoRa / LPWAN reference for link budget reality. |
| Avoid | Meshtastic community threads as budget evidence; inspirational “future of farming” decks; duplicate ingest of overlapping survey papers without a clear wiki question. |
Existing repo touchpoints (examples): CISA excerpts in wiki/source-notes/; precision-ag papers already filed—use only when a business-plan section cites them.
3.6 Rural / farm insurance and liability¶
| Field | Content |
|---|---|
| Questions to answer | What coverage categories matter for livestock, farm property, liability, umbrella, commercial if any direct sales? What questions should a binder review checklist ask? |
| Strengthens | risk register, validation backlog (V9), business risk register |
| Prefer | Insurer farm program guides (state farm / nationwide / etc.) as generic framing; Extension liability primers; state agritourism fact sheets if on-path. |
| Avoid | Single forum anecdotes as coverage facts; SEO legal blogs without primary statute or official brochure. |
3.7 Market-channel economics¶
| Field | Content |
|---|---|
| Questions to answer | How do auction, direct, and processor channels differ in shrink, logistics, working capital, and price discovery? What TN-specific infrastructure constraints matter (distance to inspected processing)? |
| Strengthens | revenue model, enterprise options, validation backlog (V5 / V6) |
| Prefer | Extension marketing and meat channel guides; USDA AMS or state market reports with dates; one peer-reviewed or Extension review on direct marketing economics. |
| Avoid | Brand marketing playbooks; unverifiable “farmers’ market gold rush” content. |
3.8 Tax and accounting — farm enterprises¶
| Field | Content |
|---|---|
| Questions to answer | What does IRS expect for farm records? How do cash vs accrual, inventory, and capital assets interact at a high level—so the wiki’s margin language stays honest? |
| Strengthens | revenue model, capital plan, 10-year roadmap |
| Prefer | IRS Publication 225 (and updates); Extension recordkeeping circulars; single CPA-society or land-grant summary with date. |
| Avoid | Aggressive tax minimization content; any wiki text that reads as personal tax advice—keep “consult a CPA” boundary. |
3.9 Agritourism — regulatory and liability (conditional)¶
| Field | Content |
|---|---|
| Questions to answer | If events, U-pick, or lodging are serious branches: what TN statutes / rules and county overlays apply? What insurance and visitor safety patterns repeat in Extension materials? |
| Strengthens | agritourism dual-site business plan, enterprise options, risk register |
| Prefer | TN Department of Agriculture / Extension agritourism or rural tourism pubs; sample hold-harmless language only from official or attorney-reviewed Extension kits—not random blogs. |
| Avoid | Instagram farm tour aesthetics; national “start a farm stay” ebooks without TN hook. |
4. Source-ingest backlog (proposed titles)¶
Naming: New wiki/source-notes/*.md files use kebab-case; titles in frontmatter sentence case; source_ids point at raw/processed/... when PDFs exist.
| Priority | Proposed source-note title (filename stem) | Maps to gap / gate |
|---|---|---|
| P0 | ut-extension-beef-cow-calf-budget-tn-20xx.md |
G1, enterprise line items |
| P0 | ut-extension-forage-establishment-maintenance-et.md |
G2, surge / input timing |
| P0 | ut-extension-livestock-water-systems-tn.md |
G2, V2/V4, capital water rows |
| P0 | nrcs-tn-pasture-practice-standards-water-access.md |
G2, NRCS sequencing |
| P0 | tn-county-zoning-ag-exemption-structure-path-YYYYMMDD.md |
G3, V8 (replace with actual county when known) |
| P1 | farmos-deployment-backup-migration-official.md |
G4, homelab fragility / ops |
| P1 | usda-ams-cattle-reporting-tn-or-southeast-method-note.md |
G6, market realism |
| P1 | ut-extension-direct-marketing-meat-channel-checklist.md |
G6, V5/V6 |
| P1 | extension-farm-liability-insurance-primer-20xx.md |
G5, V9 |
| P1 | irs-p225-farmers-tax-guide-excerpt.md |
G7, margin language |
| P2 | tn-agritourism-liability-statute-extension-summary.md |
G3/G5, only if path selected |
| P2 | cisa-secure-remote-access-farm-network-appendix.md |
Telemetry security cross-link (if not duplicate) |
Raw drops (inbox → processed): use raw/processed/2026/ (or year of acquisition) + short kebab stem matching source-note source_ids.
5. Rules — raw note vs source note vs synthesis vs comparison¶
| Stage | When to use | Repository action |
|---|---|---|
raw/ only |
You have a file (PDF, export, your scan of a county doc) but no time to summarize; must preserve provenance. | Add under raw/inbox/ → move to raw/processed/...; run pdf_to_markdown.py when PDF; do not rewrite processed text to “fix” meaning (per ingest workflow). |
source_note |
The source is stable enough to cite (URL with archive date, government PDF, manual version); you can state what it answers for the wiki. | Create wiki/source-notes/<stem>.md with page_type: source_note, source_ids, scope, limits, link to raw extract. |
| Synthesis update | A named business-plan section needs a number, gate, or risk row backed by the source. | Edit specific analysis pages (e.g. capital plan); add “Source:” line with relative link to source-note; update remediation backlog if weakness closes. |
| Comparison input | Two credible alternatives (hire vs own, auction vs direct, farmOS vs ledger-only) need side-by-side criteria not buried in narrative. | Create or update wiki/comparisons/*.md (or dedicated analysis table) with explicit columns; each column should trace to source-notes or labeled owner assumptions. |
| Defer | Source is motivational, duplicate, or answers a question already closed by validation in the field. | No new file; optional one-line pointer in validation backlog under deferred. |
Escalation shortcut: If ingest would change financing or legal posture, require both a source_note and a log entry (ingest) with gate ID affected.