Scope defines what Chronicle is responsible for, what it may preserve, what it may reference, and where institutional responsibility remains with another Satoshium Suite system.
Chronicle preserves qualifying historical occurrences through canonical Chronicle Entries. It is selective by design and does not function as a universal activity log or a replacement for the authority of other Suite systems.
Chronicle has one canonical historical-preservation object: the Chronicle Entry.
The Occurrence is what happened. The Chronicle Entry is Chronicle's structured historical-preservation record representing that qualifying Occurrence.
Chronicle does not preserve every action, record, or system change. An Occurrence must satisfy Preservation Eligibility before becoming a Chronicle Entry.
Historical Significance may provide a principal basis for preservation when an Occurrence represents an institutional change, milestone, lifecycle event, governance development, or other meaningful historical transition.
Chronicle may preserve temporal context, authoritative references, Sources, Evidence relationships, Provenance, Relationships, Verification, Validation, Corrections, Versions, publication state, and preservation state within or around a Chronicle Entry.
Sources identify where information came from. Evidence describes material that bears on the Entry or claim. Provenance documents how the information originated, moved, and entered Chronicle.
Verification reviews Chronicle's historical representation. Validation determines whether Chronicle-owned records conform to structural and procedural requirements.
Chronicle may correct its own records while preserving prior substantive states, correction rationale, and version lineage. Chronicle does not use Corrections to modify authoritative objects owned by other Suite systems.
Chronicle may publish validated Entries only after the separate Publication Gate approves Publication. Publication does not create authority over the underlying Occurrence or referenced authoritative objects.
Published Chronicle Entries may support public discovery through the Entry index and, later, a Timeline. Timeline remains downstream of Chronicle Entries rather than becoming a separate canonical record layer.
Chronicle may preserve qualifying Occurrences involving multiple Suite systems and institutional developments.
The final Event Type vocabulary is governed through Chronicle Controlled Values.
Chronicle is not a universal activity log and does not replace the institutional systems it references.
Chronicle does not correct external authoritative objects, issue certifications, create Registry entries, produce attestations, generate Integrity References, create Discovery Signals, orchestrate workflows, or replace Atlas source intelligence.
Chronicle participates in reference-based Suite interoperability while each system retains authority for its own objects and responsibilities.
Reference does not transfer authority.
Preservation Eligibility prevents Chronicle from becoming an unlimited historical repository.
A record or event may be operationally important, technically valid, evidentially strong, or publicly visible and still fall outside Chronicle if it does not satisfy Preservation Eligibility.
Chronicle may expand through additional Event-Type Profiles, broader public historical discovery, additional automation, cryptographic integrity mechanisms, integrity anchoring, and long-term archival systems.
Future expansion should preserve the canonical Chronicle Entry model, Preservation Eligibility, clear authority boundaries, reference-based interoperability, and version-aware historical preservation.
Chronicle's institutional scope has now been exercised through CHR-2026-0001.
The production case confirms Chronicle's operational boundary: preserve qualifying history while leaving authoritative operational objects with the institutions that own them.
Chronicle preserves qualifying historical Occurrences through Chronicle Entries. It may preserve or reference Sources, Evidence, Provenance, authoritative Suite objects, Verification, Validation, Corrections, Versions, Relationships, and publication or preservation state.