Evidence is material that bears on Chronicle's historical representation of a qualifying Occurrence. It may support, challenge, contradict, clarify, corroborate, contextualize, or limit confidence in a Chronicle Entry or claim. Evidence supports Verification and may also be subject to applicable Validation requirements.
Evidence is not the authoritative event itself and does not transfer authority to Chronicle. Where another Suite system owns the underlying action, determination, or record, that authoritative object remains authoritative and Chronicle references it separately.
Evidence supports review of Chronicle's own historical representation. It does not replace the Occurrence, the Chronicle Entry, an authoritative Suite object, Verification, or Validation.
Evidence may support a factual assertion, temporal detail, relationship, provenance statement, or other part of Chronicle's historical representation.
Evidence may challenge Chronicle's current representation or indicate that a claim requires further review.
Conflicting Evidence should remain visible rather than being removed merely because it complicates the historical record.
Evidence may clarify ambiguous dates, identities, relationships, terminology, or historical context without independently establishing authority.
Multiple independent items may corroborate the same historical representation. Corroboration should not be confused with duplication.
Evidence may preserve contemporary context showing what was known, documented, disputed, or available at the time of the Occurrence.
Chronicle Verification may use Evidence to assess support, consistency, authenticity, Provenance, Relationships, limitations, and temporal coherence.
Incomplete, stale, conflicting, unavailable, derivative, or otherwise limited Evidence should remain explicitly described where material to later review.
Evidence Type should use the Chronicle Controlled Values Registry rather than ad hoc category labels.
These categories describe the form or institutional character of the Evidence. They do not determine its relationship to the Entry or its evidentiary strength.
Material drawn from or directly reflecting an authoritative record or system. Authority belongs to the originating system, not to Chronicle.
Documents, reports, letters, publications, filings, or other documentary material that bears on the Entry or claim.
Repository records, commits, releases, structured artifacts, or other preserved repository material relevant to the historical representation.
Archived webpages, snapshots, preserved documents, historical collections, or other materials accessed through an archive.
Logs, hashes, timestamps, system outputs, generated metadata, receipts, or other machine-produced material used in historical review.
Statements, interviews, declarations, witness accounts, or similar testimonial material relevant to the Entry.
Material that primarily helps explain the surrounding historical circumstances rather than directly establishing the underlying authoritative action.
Used only when an approved existing Evidence Type cannot accurately represent the material. Repeated use should trigger review for a possible new Controlled Value.
Evidence should be linked explicitly to the Chronicle Entry or specific claim it bears upon.
Linkage should make clear whether the Evidence supports, challenges, contradicts, clarifies, corroborates, contextualizes, or limits confidence.
Evidence relationship terms should remain distinct from Evidence Type.
Candidate relationship terms include Supports, Challenges, Contradicts, Clarifies, Corroborates, Contextualizes, and Limits Confidence. These should become a formal Controlled Value set only when schema and production use demonstrate the need.
A Certification Package, SREG Registry Entry, Integrity Reference, Trust Statement, or other authoritative Suite object may provide Evidence relevant to a Chronicle Entry. Its authoritative status still belongs to the originating system.
Chronicle should preserve qualities and limitations relevant to later review rather than reducing Evidence to a simple present/absent state.
These are quality considerations, not a universal numerical trust score.
A distinct Evidence Record should be created only when its additional structure provides durable operational value. Where one is used, it should preserve enough structure to identify the Evidence and connect it to its Source, Provenance, Entry linkage, limitations, and review context.
Preservation Eligibility and Evidence sufficiency remain separate questions. An Occurrence may be historically significant enough to preserve even when Evidence is incomplete, disputed, or limited.
Chronicle should disclose those conditions rather than automatically importing certification-specific Evidence thresholds into historical preservation.
Phase VIII establishes Chronicle Validation as an active production function. Evidence-related requirements are evaluated through the applicable Chronicle Validation Rules rather than through a separate Evidence-validation system.
Validation should confirm, where applicable:
An Evidence defect may cause the current Entry Version to fail Validation when the affected Evidence information is required by the Base Schema, Event-Type Profile, Provenance rules, Verification dependency, or publication prerequisites.
Evidence handling occurs during assembly of Sources, Evidence, Provenance, and Relationships before Verification and Validation.
Chronicle should preserve enough Evidence structure to support review and traceability without creating unnecessary supporting objects when a direct, durable reference is sufficient.
The first production Chronicle Entry confirmed that Evidence structure should remain proportional to the needs of the Entry.
For CHR-2026-0001, the supporting Certifier artifacts had evidentiary value during Verification, but Chronicle did not create separate Evidence Records merely to duplicate the same material already preserved as traceable Sources and authoritative references.
This production precedent preserves Chronicle's distinction among Source, Evidence, Authoritative Record, and Provenance while applying the principle: Minimum necessary structure first.
Chronicle preserves Evidence so the historical representation can remain inspectable, challengeable, and understandable over time.