Evidence grade and canonical authority¶
Purpose: Give readers a small vocabulary for how much to trust a page and where to start so the vault stays navigable as analyses accumulate.
Canonical pages (durable scope)¶
Canonical pages own a topic for the East Tennessee two-site package or a named system (e.g. telemetry SoR). They are updated in place; new pages extend them rather than competing with parallel essays. Anchors: East Tennessee two-site farm business plan (package), Structural audit — page ownership, entity gaps, and hub routing.
Supporting analyses¶
Supporting analyses provide matrices, artifacts, runbooks, or time-boxed validation detail. They do not redefine the strategy owned by the canonical chapter— they link back to it.
Exploratory / anecdotal¶
Exploratory material (blogs, forums, listicles) may inform ideas or failure-mode color; it is not a substitute for extension, agency, or primary legal sources for operational, financial, regulatory, or safety claims. Mark low authority in prose or confidence: low where used.
Raw vs public pages¶
Source-notes may cite raw/processed/ paths. Published wiki pages must remain intelligible without opening raw files: state the claim, the authority type (e.g. “NASS county table, 2024 survey”), and a link to the source-note or official reference.
See also¶
Source-note abstract and evidence pattern— Cluster source-notes: abstract, authority mix, canonical links, key claimsEvidence grade(glossary)Source authority hardening audit— where low-authority ingests remain, and which official clusters supersede themExecution readiness gap auditAuthoritative execution evidence cluster — East Tennessee