Chronicle · FAQ

Satoshium Chronicle FAQ

Frequently asked questions about Chronicle's purpose, canonical Chronicle Entry, Preservation Eligibility, authority boundaries, Sources, Evidence, Provenance, Verification, Validation, Corrections, Timeline, and historical-preservation model.

These answers provide a plain-language introduction to the architecture defined more formally throughout the Chronicle Foundation.

What is Chronicle?

Chronicle is the historical-preservation institution of the Satoshium Suite. It preserves qualifying historical Occurrences through canonical Chronicle Entries.

Why does Chronicle exist?

Chronicle preserves institutional memory so future reviewers can understand what happened, when it happened, which authority established it, what Sources and Evidence existed, and how Chronicle's own historical record evolved.

Does Chronicle determine truth?

No. Chronicle does not claim universal or absolute truth authority. It preserves its own structured historical representation while other Suite systems remain authoritative for their own objects and determinations.

What is a Chronicle Entry?

A Chronicle Entry is the canonical historical-preservation object of Chronicle. The Occurrence is what happened; the Entry is Chronicle's structured preservation record representing that qualifying Occurrence.

What is Preservation Eligibility?

Preservation Eligibility is Chronicle's admission rule. It asks whether an Occurrence should be preserved. Not every action, record, or system event belongs in Chronicle.

What is Historical Significance?

Historical Significance explains why an Occurrence is important enough to preserve, such as an institutional change, milestone, governance development, first or last occurrence, or other meaningful transition.

Source, Evidence, and Provenance

Source = Where information came from.
Evidence = What bears on the Entry or claim.
Provenance = How the information originated, moved, and entered Chronicle.

What is Verification?

Verification reviews Chronicle's own historical representation using authoritative references, Sources, Evidence, Provenance, temporal consistency, relationships, and known limitations.

What is Validation?

Validation determines whether a Chronicle-owned record conforms to structural and procedural requirements such as identifiers, schemas, Controlled Values, relationships, Provenance, versioning, and publication readiness.

What are Corrections?

Corrections are documented changes to Chronicle-owned records. Substantive Corrections should preserve prior state, correction rationale, and version lineage.

Why preserve corrections?

Visible correction history allows future reviewers to reconstruct how Chronicle's own representation changed over time rather than hiding material revisions.

Can Chronicle preserve conflicting information?

Yes. Chronicle may preserve uncertainty, disagreement, conflicting Sources, disputed Evidence, or incomplete Provenance when those limitations are documented transparently.

Does a Chronicle Entry prove an event happened?

Not by itself. A Chronicle Entry is Chronicle's historical-preservation record. Its reviewability depends on authoritative references, Sources, Evidence, Provenance, Verification, Validation, and known limitations.

Is Chronicle a certification system?

No. Certifier remains authoritative for Certification Packages, certification determinations, status, and certification lifecycle.

Is Chronicle a registry?

No. Registry remains authoritative for SREG Registry Entries, registration, cataloging, Registry metadata, relationships, and Registry lifecycle.

How does Chronicle relate to Certifier?

Chronicle may preserve a qualifying certification Occurrence through a Chronicle Entry that references the authoritative Certification Package. Chronicle does not recreate the certification.

How does Chronicle relate to Registry?

Chronicle may reference SREG Registry Entries or preserve qualifying Registry milestones. Registry authority remains with Registry.

How does Chronicle relate to the rest of the Suite?

Chronicle may reference authoritative objects from Atlas, Certifier, Registry, Anchor, Beacon, Attestor, and Navigator while each system retains authority for its own objects and responsibilities.

What is the authority rule?

Chronicle uses reference-based interoperability.

Reference does not transfer authority.

What is an Event-Type Profile?

An Event-Type Profile specializes the Chronicle Base Schema for a particular class of Occurrence by adding required fields, references, relationships, Evidence expectations, Provenance requirements, or Validation rules.

Can Verification results change?

Yes. New Evidence, improved Provenance, changed authoritative records, or better historical context may justify an updated Verification State.

Does Chronicle preserve unavailable information?

Not always directly. Where original material cannot be preserved, Chronicle may retain durable references, metadata, Provenance, archive references, integrity information, limitations, and preservation notes.

Can Chronicle preserve history retrospectively?

Yes. Later context may establish Preservation Eligibility for an earlier Occurrence. Event Date remains distinct from Entry creation, publication, Correction, or Version dates.

Is Timeline the historical record?

No. Timeline is intended as a downstream chronological discovery view of published Chronicle Entries. The Chronicle Entry remains canonical.

Is Chronicle operational now?

Yes. Chronicle is operational as a production historical-preservation institution. Its first canonical production Entry, CHR-2026-0001, was formally assigned, verified, validated, approved through the separate Publication Gate, and published on August 22, 2026.

What Did Chronicle Prove in Its First Production Operation?

Chronicle demonstrated that a qualifying Occurrence can move through the complete institutional production path without collapsing authority boundaries.

Occurrence → Preservation Eligibility → Chronicle Entry → Authoritative References → Sources / Evidence / Provenance → Verification → Validation → Publication Gate → Publication → Maintenance / Versioning → Historical Preservation

CHR-2026-0001 completed that path as Entry Version 1.

What Is Chronicle's Long-Term Goal?

Chronicle's long-term goal is a durable historical-preservation institution capable of maintaining Satoshium history across changing technologies, systems, organizations, and generations.

Chronicle already supports machine-readable Chronicle Entries, Event-Type Profiles, structured Validation, cross-Suite historical relationships, and production publication. Future capabilities may extend public Timeline discovery, automation, cryptographic integrity verification, and long-term Provenance preservation.

Guiding Principle

Events happen.
Suite systems establish authority.
Chronicle preserves qualifying historical memory.

Back to Chronicle →