Skip to content

Structural audit — page ownership, entity gaps, and hub routing

Purpose: Keep the wiki from becoming an analysis swamp by naming who owns durable meaning (canonical pages), which analyses support them, where entities should anchor repeated real-world subjects, and how hubs route readers. Complements Structural audit — repository shape and canonical routing (merge policy, index structure) and implements AGENTS.md governance (canonicalization, entity-first, hubs).

Epistemic rule: This audit does not invent site facts. It routes and prioritizes; placeholders stay on deployment pages until evidence lands in raw/ + source-notes.

1. Canonical ownership by cluster

Cluster Canonical owner(s) (durable scope) Supporting / extending (do not duplicate TOC) Ownership notes
Business plan / strategy (ET two-site) business-plan/east-tennessee-two-site-farm-business-plan, east-tennessee-two-site-farm-business-plan-framework Chapters in analyses/east-tennessee-two-site-farm-business-plan-*.md; critique/remediation/source-campaign Package hub = navigation; framework = rubric + full tree. New “strategy essays” should extend framework or a single chapter, not parallel packages.
Two-site operating model two-site-operations-model-5ac-homebase-120ac-production (ET scenario) dual-site-operations-model-non-agritourism Generic vs ET-named sites—no merge; routing headers on both. Weekly/family matrices extend ops model.
Telemetry / architecture / SoR reference-architecture-5ac-homebase-120ac-smart-farm (package hub), telemetry-system-of-record-boundaries-and-authority, field-telemetry-reference-architecture-homestead-120ac automation-principles-two-site-smart-farm, remote-access-operational-security-model-two-site-smart-farm, smart-tech business-plan chapter Reference arch = boundaries + package map; field telemetry = MQTT/stack detail; SoR = authority matrix—avoid a fourth “data governance” analysis until one of these is full.
Spatial / identity farm-spatial-model-and-asset-registry-standard Instrumentation matrix (IDs), farmOS model source-notes Parcels/paddocks/devices minimum fields live here; entity Farm parcels and land units summarizes for cross-linking.
Validation / pilot planning east-tennessee-two-site-farm-business-plan-validation-backlog, validation-backlog-before-major-spend-two-site-smart-farm validation-and-pilot-plan-first-24-months-east-tennessee-two-site, pilot-and-recon-checklists-first-24-months-two-site-smart-farm First 24 months = time-boxed matrix; major-spend = $ gates—if a new “validation” analysis appears, it must link these two or justify a new scope in wiki/log.md.
Labor / coverage / risk east-tennessee-two-site-farm-business-plan-labor-and-family-model, east-tennessee-two-site-farm-business-plan-risk-register weekly-coverage-matrix-two-site-farm-operations, family-labor-model-and-coverage-matrix-two-site-smart-farm, business-risk-register-two-site-smart-farm Matrices are artifacts, not alternate labor theories.
Capital / revenue / economics east-tennessee-two-site-farm-business-plan-capital-and-financing, east-tennessee-two-site-farm-business-plan-revenue-and-phased-income capex-opex-enterprise-sequencing-two-site-constraint, enterprise-unit-economics-worksheet-methodology-two-site-smart-farm, farm-accounting-baseline-chart-of-accounts-enterprise-pl-two-site-smart-farm, milestone/ROI models Worksheets hold methodology shells—no competing “capital theory” pages without supersedes.
Water / roads / power / infra Topic hubs (Ponds, water features…, Off-grid solar…, Rural road and driveway erosion…); two-site reference + runbooks for failures Standalone syntheses (e.g. dirt road erosion analyses) Synthesis analyses should end with hub links and entity anchors (Farm water infrastructure system, Farm on-site power system) rather than fork new “infrastructure overview” pages.
Agritourism vs non-agritourism agritourism-dual-site-business-plan-five-and-120-acres (lodging-led alternate scenario) ET business plan package (production-led) Different intent—cross-link as alternate scenario, not merge.

2. Overlapping or sideways analyses (risk)

Pattern Examples Mitigation
Meta-audits Strategic audit, IA target design, implementation backlog, repository structural audit, Structural debt audit — wiki IA and operational maturity, this page Keep one question per audit title; cross-link; do not copy/paste backlog tables between them—pointer instead.
Query syntheses analyses/*query* agritourism, stocking prompts, profitable crops matrix Acceptable as time-stamped answers; if content becomes permanent doctrine, fold into topic hub or canonical analysis and add routing.
Duplicate “overview” Domain content overview vs strategic audit vs business plan executive summary Domain overview = strands; executive summary = business plan only; strategic audit = gap list—readers should not see three competing “north stars” without labels.

3. Weak hubs (before this pass)

Hub Issue Fix direction
index.md Long flat analyses list elsewhere Business plan section already elevates ET package; entities need expansion (below).
two-site-smart-farm-operations Tables strong but no ownership row Addressed (2026-04): Canonical ownership table + Regulatory & site evidence row → Authoritative execution evidence cluster, Execution readiness gap audit.
domain-content-overview Strand map strong; ownership implicit Add canonical routing pointer to this audit and Execution readiness gap audit.

4. Entity layer gaps (addressed incrementally)

Previously: Mostly products (farmOS, Home Assistant) + demo org.

Added (structural placeholders, no fake deeds):

Expanded (2026-04) — operating objects: See Entity layer — operating objects gap audit and the Entities cluster in index.md (node classes, gateways, WAN roles, storage/backup tiers, labor/market/legal patterns, infrastructure categories, field link classes, k8s control-plane roles). Still thin or private: named legal entities with filings; specific SKUs; named buyer relationships—keep on worksheets or future evidenced entity pages.

5. Prompt residue / scaffolding risk

Signal Response
Analysis with only questions and no links to canonical pages Add Routing paragraph or merge into hub.
status: draft everywhere Acceptable for deployment placeholders; business plan framework should graduate to active when family review completes (human gate).
“Hostile review” standing alone Keep as critique artifact; remediation backlog owns follow-up—already linked.
  1. Before analyses/new-*.md: search domain-content-overview + relevant hub + this section.
  2. Prefer entities/ for sites and infrastructure systems that appear in ≥3 pages.
  3. Update hub tables the same commit as a new sibling page.
  4. Log scope decisions in wiki/log.md when creating a page that could be read as canonical.