Verification is Chronicle's structured review of its own historical representation. It examines whether a Chronicle Entry is adequately supported, internally coherent, traceable to authoritative references, Sources, Evidence, and Provenance, temporally consistent, relationship-aware, and appropriately limited where uncertainty remains.
Verification does not re-adjudicate certifications, registrations, attestations, anchors, discovery signals, workflows, Atlas records, or other determinations owned by another Satoshium institution.
Verification reviews Chronicle. It does not replace the authority of the systems Chronicle references.
Confirm that the Entry under review is clearly identified and that the reviewed materials, Sources, Evidence, Relationships, and authoritative references belong to the intended Chronicle Entry Version. Identifier syntax and formal conformance are tested during Validation.
Confirm that required Source Records or external Source references exist, are identifiable, and correspond to the Sources cited by the Entry.
Confirm that referenced authoritative Suite objects are identifiable and that Chronicle represents their role without assuming their institutional authority.
Confirm that Event Date and other temporal information are internally consistent and are not confused with Entry creation, retrieval, publication, Correction, or Version dates.
Confirm that material Relationships use the correct direction and meaning and are consistent with the referenced records and historical sequence.
Confirm that required Evidence is available or properly referenced and that known limitations, unavailable items, or disputed material remain visible.
Confirm that origin, access method, retrieval date, Source references, transformations, and known provenance limitations are coherent.
Confirm that Chronicle's historical context does not overstate what the Sources, Evidence, authoritative records, or Relationships support.
Chronicle may verify that it accurately references an authoritative record. Chronicle must not re-decide the determination owned by the originating system.
Confirm the record under review and the applicable Chronicle Entry Version, Event Type, and governing schema or profile context.
Confirm the exact Entry Version being reviewed and ensure that all materials considered during Verification correspond to that Entry. Formal identifier syntax, uniqueness, and schema conformance are handled by Validation.
Confirm that required Source Records and external references exist and are sufficiently identifiable for later review.
Confirm that authoritative external records are correctly identified and that Chronicle has not converted a reference into an authority claim.
Compare Event Date and other relevant dates against the cited records, Source context, and Provenance.
Review directional and non-directional Relationships for semantic accuracy, target correctness, historical consistency, and unsupported implications.
Confirm required Evidence exists or is referenced, Evidence Type is appropriate, and Evidence limitations are visible.
Review the documented information path and confirm that Chronicle can explain how the supporting information entered the historical record.
Confirm that Chronicle's narrative and contextual representation does not overstate what the authoritative references, Sources, Evidence, Relationships, dates, or Provenance support.
Confirm that unresolved conflicts, missing Sources, incomplete Provenance, unavailable Evidence, uncertain dates, or other material limitations are disclosed.
Assign the approved Verification State that accurately reflects the current result of Chronicle's review.
Verification State should use the Chronicle Controlled Values Registry.
The Chronicle Entry has not yet undergone the applicable Verification procedure.
Verification is actively underway and no final Verification State has yet been assigned.
Chronicle completed the applicable review and found the historical representation sufficiently supported and internally consistent under current Chronicle rules.
Chronicle completed the review, but material limitations remain and are explicitly preserved in the Entry or supporting records.
A material issue remains open, such as conflicting Evidence, incomplete Provenance, uncertain dates, unresolved Relationships, or another condition preventing a fully resolved Verification outcome.
Verification State may change when new Sources, Evidence, Corrections, Provenance, or authoritative records become available.
Verification reviews Evidence but does not convert Evidence into authority.
Verification checks whether the recorded provenance path is sufficient and internally consistent. It does not manufacture missing Provenance.
Verification and Validation are sequential but distinct institutional functions.
Verification State is not a Validation result. Validation applies the CHR-VAL-001 through CHR-VAL-014 rule set and produces the authoritative conformance outcome:
Schema defines structure. Verification reviews the representation. Validation tests conformance. Publication determines public production state.
Verification is a prerequisite to publication, but Verification alone does not make an Entry publication-ready.
The required Verification State may depend on Chronicle publication rules and material limitations. Validation confirms whether that prerequisite has been satisfied; the Publication Gate then makes the separate institutional approval decision, and Publication performs the later state-changing action.
Reverification may be required when material new information changes the basis on which Chronicle previously reviewed the Entry.
When a change affects requirements previously validated, Reverification should be followed by targeted or full Revalidation as governed by the Chronicle Validation Sequence.
Verification results should remain traceable to the exact Entry Version reviewed, the authoritative references, Sources, Evidence, Provenance, Relationships, limitations considered, and the Verification State assigned.
Chronicle does not presently require a separate canonical Verification Record for every Entry merely for architectural symmetry. Verification information should be preserved through the Entry, supporting operational artifacts, or other lightweight institutional documentation sufficient to reconstruct the review.
Chronicle Verification has now been exercised in production. On August 22, 2026, CHR-2026-0001 Entry Version 1 underwent formal Verification before CHR-VAL Validation and Publication.
The production review confirmed the intended boundary: Chronicle verified its historical representation of the July 5, 2026 certification Occurrence without re-performing or replacing Certifier's authoritative certification determination.
Open CHR-2026-0001 →Chronicle verifies the integrity of its historical representation—not the institutional authority of the systems it documents.