Chronicle · Validation

Satoshium Chronicle Validation

Satoshium Chronicle Validation defines how Chronicle determines whether a constructed Chronicle Entry conforms to the governing institutional and machine-readable requirements applicable to that Entry.

Validation tests conformance. It does not decide whether an Occurrence should be preserved, re-adjudicate an external authoritative determination, replace Chronicle Verification, or itself publish the Entry.

Institutional Position

Validation occurs after Chronicle has assembled and Verified the current Entry representation and before that Entry proceeds through the publication gate.

Occurrence Identified → Preservation Eligibility → Entry Created → Verification → Validation → Publication Gate → Publication
Preservation Eligibility asks whether Chronicle should preserve the Occurrence. Verification reviews Chronicle's historical representation. Validation determines whether the resulting Entry conforms to the requirements governing that representation.

Why Validation Matters

A historically appropriate Entry may still be incomplete or structurally invalid if identifiers, schema fields, Controlled Values, authoritative references, dates, Relationships, Provenance, or publication prerequisites are wrong or missing.

The Core Question

Chronicle Validation asks:

Does this Chronicle Entry conform to the institutional and machine-readable requirements that govern this Entry Version?

Chronicle's Responsibility

Chronicle validates its own Entry structure, classifications, references, Relationships, Provenance, Version state, and publication readiness.

Chronicle's Limitation

Validation does not create external authority, certify a subject, prove every underlying claim, replace Verification, or determine the substantive correctness of another Suite institution's authoritative action.

Canonical Validation Model

Chronicle Rules + Base Schema + Event-Type Profile + Controlled Values + Institutional Requirements → Validation Result

Validation applies the requirements governing one specific Chronicle Entry Version.

Schema ≠ Verification ≠ Validation ≠ Publication

Schema = Defines structure.
Verification = Reviews Chronicle's historical representation.
Validation = Tests conformance to governing requirements.
Publication = Determines whether the validated Entry enters public production use.

These functions support one another but remain institutionally distinct.

Validation Domains

  • Chronicle Entry identifier validation;
  • Base Schema conformance;
  • applicable Event-Type Profile conformance;
  • Controlled Values validation;
  • Required and Conditional field validation;
  • authoritative reference validation;
  • date and time formatting validation;
  • Relationship integrity validation;
  • Provenance validation;
  • Correction and Version consistency where applicable;
  • publication readiness validation.

Identifier Validation

Confirms the Chronicle Entry identifier conforms to the approved CHR-YYYY-NNNN architecture, remains stable, and does not conflict with identifier rules.

Schema Validation

Confirms the Entry conforms to the Chronicle Base Schema and, where applicable, the governing Event-Type Profile.

Controlled Values

Confirms governed values such as Event Type, Verification State, Lifecycle State, Publication State, and Relationship Type use approved Chronicle vocabularies.

Required Fields

Confirms universal Base Schema fields are present and Conditional fields are present whenever their governing condition applies.

Authoritative References

Confirms required authoritative records are identified through durable references and that Chronicle does not misrepresent external authority as Chronicle authority.

Date and Time Validation

Confirms Event Dates, timestamps, publication dates, retrieval dates, and Version dates use valid formats and remain semantically distinct.

Relationship Integrity

Confirms Relationship Types are approved, targets are identifiable, direction is coherent, and Relationships do not imply unsupported causation or authority transfer.

Provenance Validation

Confirms the Entry preserves how information originated, was acquired or accessed, when it was retrieved, and which Source or authoritative record supplied it.

Version and Correction Validation

Confirms Entry Version, prior-Version references, Corrections, and resulting states preserve Chronicle's required historical lineage when a material change exists.

Publication Readiness

Confirms the Entry has satisfied the structural and institutional prerequisites required before it may proceed into public production use.

Validation Inputs

Chronicle Validation should identify the exact requirements being applied.

  • Chronicle Base Schema identity and Version;
  • applicable Event-Type Profile and Profile Version;
  • Chronicle Identifier rules;
  • Chronicle Controlled Values;
  • Chronicle Relationship rules;
  • Chronicle Provenance requirements;
  • Chronicle Versioning and Correction requirements where applicable;
  • Chronicle Publication prerequisites;
  • applicable Suite authority and interoperability requirements;
  • Validation procedure or checklist version.
A Validation result is meaningful only when the governing requirements are identifiable.

Validation Workflow

Receive Entry for Validation → Validate Identifier → Validate Base Schema → Validate Event-Type Profile → Validate Controlled Values → Validate References → Validate Relationships and Provenance → Validate Publication Readiness → Record Result

Validation Outcomes

The initial Chronicle Validation model should remain simple.

  • PASS — all blocking Validation requirements are satisfied.
  • FAIL — one or more blocking Validation requirements are not satisfied.
A FAIL result means the current Chronicle representation is not ready to proceed. It does not establish that the historical Occurrence is false.

Validation Failure

A failed Validation should identify the failed requirement and preserve enough information to correct the Entry.

Validation failure does not:

  • delete the Chronicle Entry;
  • erase the historical Occurrence;
  • invalidate an external authoritative object;
  • convert Chronicle into the authority for another institution's determination;
  • permit silent substantive rewriting.
Correct the representation. Preserve the history.

Revalidation

Revalidation may be required after:

  • material Entry correction;
  • new Entry Version;
  • Event Type correction;
  • authoritative-reference change;
  • Relationship change;
  • Provenance correction;
  • material Evidence change affecting the representation;
  • schema or Event-Type Profile migration;
  • publication-state change where requirements must be reevaluated;
  • discovery of a prior Validation defect.

Revalidation should determine whether targeted review is sufficient or the full Validation sequence must be repeated.

Relationship to Verification

Verification and Validation are separate Chronicle functions.

Verification ≠ Validation

Verification asks whether Chronicle's historical representation is adequately supported and internally reviewable.

Validation asks whether that representation conforms to the requirements governing the current Entry Version.

Relationship to Publication

Validation feeds the Publication Gate; it is not the Publication Gate or Publication itself.

Validation PASS → CHR-VAL-011 PASS → Publication Gate → Publication when Approved

A Validation PASS confirms conformance. Chronicle Publication still determines whether and how the Entry enters public production use.

Relationship to External Authority

Chronicle Validation does not validate another Suite institution's authoritative determination as though Chronicle owned that authority.

Certifier establishes a certification action.
Chronicle verifies its historical representation.
Chronicle validates the Chronicle Entry.
Chronicle does not re-certify the subject.

What Validation Does Not Establish

  • It does not determine Preservation Eligibility.
  • It does not replace Chronicle Verification.
  • It does not certify the subject of an external record.
  • It does not prove every historical claim independently.
  • It does not create external Source Authority.
  • It does not transfer authority from another Suite institution.
  • It does not itself publish the Chronicle Entry.
  • It does not authorize silent rewriting of prior states.
  • It does not eliminate future revalidation.

Production Validation in Operation

Chronicle's Validation architecture has now been exercised in live production. Entry Version 1 of CHR-2026-0001 completed the full CHR-VAL sequence on August 22, 2026.

Chronicle Base Schema v1.0.0 + Certification Event-Type Profile v1.0.0 + CHR-VAL-001 through CHR-VAL-014 = OVERALL VALIDATION: PASS
CHR-VAL-010: Not Applicable
CHR-VAL-011 Publication Readiness: PASS
Publication Gate: APPROVED FOR PUBLICATION
Publication then executed as a separate institutional action.

The durable production Validation artifact is CHR-2026-0001-v1-validation.md. It is associated with Entry Version 1 and does not constitute a separate canonical Chronicle object.

Open CHR-2026-0001 → Open Validation Artifact → Open Chronicle Schemas →

Validation Principle

Chronicle Validation should confirm that each Entry is structurally conformant, institutionally coherent, traceable to its authoritative references and Provenance, semantically consistent, and ready to proceed toward publication.

Schema defines structure.
Verification reviews the representation.
Validation tests conformance.
Publication determines public production state.
Back to Chronicle → Open Verification → Open Provenance →
Validation tests whether Chronicle implemented its own requirements correctly.