Source-note abstract and evidence pattern¶

Purpose: A lightweight, repeatable block for wiki/source-notes/ so cluster and batch notes are scannable in Obsidian and MkDocs, and claims remain intelligible when public builds neutralize navigable raw/ links (see docs/operations/raw-corpus-and-publishing.md).

When to use: Hub / index source-notes (multiple raw/ paths), official documentation clusters, and high-friction batches—not necessarily every single-file note.

Optional frontmatter hints¶

Authors may add tags such as source_cluster: authoritative or keep existing confidence / review_status. No new required fields for validation.

Evidence summary block (template)¶

Place after the H1 title and before long tables, or immediately after a short Purpose paragraph.

```markdown

Evidence summary¶

Field	Content
Abstract	2–4 sentences: what this cluster covers and why it exists.
Authority mix	One line: e.g. `agency + extension + vendor docs (captured)` or `official docs + community (supporting only)`.
Decision relevance	Bullet list: which decisions or gates this evidence supports (or does not support).
Canonical wiki links	Bullet list: synthesis pages readers should read first.

Key claims (public-safe; cite authority, not only paths):

Claim one (e.g. “NASS publishes county-level cash rent tables for TN—survey year stated in source-note body”).
Claim two.

Open questions / follow-ups

What remains unknown, unverified, or pending ingest. ```

Shorter variant (single cluster row in a parent index): use only Abstract, Authority mix, and Canonical wiki links in a mini table under the cluster heading.

Authority vocabulary (align with evidence grade)¶

Use the same plain-language bands as Evidence grade and canonical authority:

Official / agency / extension: USDA, NRCS, land-grant Extension, primary statutes as cited.
Vendor primary: upstream project docs, datasheets—good for product facts, not regulatory conclusions alone.
Community / anecdotal: forums, blogs—ideas and failure-mode color only unless corroborated.

Examples in this vault¶

Notes updated to demonstrate the pattern (non-exhaustive):