Source Families
05+
Examples documented in current spec
Every visible node is intended to trace back to explicit source families, timeline markers, and curatorial notes that can be audited.
The UI should never imply certainty without evidence. Provenance is treated as a first-class field so records remain inspectable instead of decorative.
Source Families
05+
Examples documented in current spec
Core Fields
Region / Era
Theme, category, notes
Audit Goal
Readable
Human-facing integrity trail
Record Integrity
Every visible node is intended to trace back to explicit source families, timeline markers, and curatorial notes that can be audited.
Source Families
Municipal ledgers, census extracts, and testimony indexes are linked to every visible node before it appears in the explorer.
Metadata Fields
Region, era, theme, category, and provenance notes are converged through multi-review pipelines to guarantee interpretability.
Quality Gates
Confidence scoring, freshness checks, and conflict handling form the last mile before a node is allowed into the registry.
Provenance Chain
Source Families
Examples include census extracts, municipal records, route maps, oral testimony indexes, and institutional ledgers.
Metadata Fields
Region, era, theme, category, and provenance notes are treated as first-class attributes used for filtering and interpretation.
Quality Gates
Future production flow should include confidence scoring, source freshness checks, and explicit conflict handling for disputed records.
Audit Trail
Each node that flows from the registry is logged with timestamps plus reviewer initials before it is surfaced to the public explorer.
Current Public Summary
Provenance policy describes how America250 archive records are tied to source families, metadata fields, and quality gates for interpretability.
Provenance refers to explicit source and metadata context attached to each record so users can inspect where claims came from.
Region, era, theme, category, and provenance notes are core fields used for filtering and interpretation.
The roadmap calls for confidence scoring, source freshness checks, and conflict handling so ambiguity is visible rather than hidden.
Related Information
These pages reduce ambiguity around the current preview build and tie the America250 topic cluster back to the archive surface, policies, and trust model.