Definitions establishes the canonical terminology used throughout Chronicle documentation, schemas, records, procedures, and public historical-preservation interfaces.
Consistent terminology protects architectural clarity. Terms should retain their defined meaning across Chronicle and remain compatible with broader Satoshium Suite standards.
The Occurrence is what happened. The Chronicle Entry is Chronicle's canonical structured historical-preservation record representing that qualifying Occurrence.
The historical-preservation institution of the Satoshium Suite. Chronicle is authoritative for its own Entries and historical-preservation state while referenced Suite systems retain authority for their own objects.
The canonical historical-preservation object of Chronicle. A Chronicle Entry represents one qualifying historical Occurrence.
An event, action, change, decision, publication, milestone, lifecycle transition, governance development, or other thing that happened independently of Chronicle.
A controlled classification describing the kind of Occurrence represented by a Chronicle Entry. Event Type does not create a second canonical object.
A specialization of the Chronicle Base Schema that adds Event-Type-specific requirements without creating a new canonical record class.
Chronicle's admission rule for historical preservation. It answers: “Should Chronicle preserve this occurrence?”
The substantive reason an Occurrence is important enough to preserve. It answers: “Why is this occurrence worth preserving?”
An architectural umbrella term for structured information created, maintained, or governed within Chronicle. Record is not a competing canonical object.
A Chronicle-owned record serving a distinct function in support of Chronicle Entries, such as a Source Record, Evidence Record, or Correction Record when additional structure is operationally justified.
A record whose institutional authority comes from the system responsible for creating or governing it. Chronicle may reference it without assuming its authority.
The origin of information referenced by Chronicle. A Source does not automatically establish truth or Chronicle authority.
A supporting Chronicle-owned record documenting source attribution, temporal context, location, provenance, archival state, limitations, and relationships.
A controlled classification describing what a Source is, such as a webpage, document, archive, database, institutional record, repository, dataset, or statement.
A provisional description of how a Source functions in relation to a Chronicle Entry or Evidence Record. Source Role is not presently a frozen Chronicle Controlled Value set.
Material that supports, challenges, contradicts, clarifies, corroborates, contextualizes, or limits confidence in a Chronicle Entry or claim.
A supporting Chronicle-owned record describing the role, origin, integrity, limitations, provenance, and relationships of Evidence.
The documented origin and movement of information, Sources, Evidence, records, or artifacts into Chronicle.
Identification of the creator, publisher, institution, system, person, or Source responsible for originating or distributing information.
Institutional responsibility assigned to a Suite system for its own objects, determinations, actions, and lifecycle.
Review of Chronicle's own historical representation using authoritative references, Sources, Evidence, Provenance, temporal information, relationships, and limitations.
Determination that the current Chronicle Entry Version conforms to the institutional and machine-readable requirements governing it.
A documented change to a Chronicle-owned record intended to improve accuracy, clarity, context, provenance, references, relationships, or completeness.
A preserved state within the lineage of a Chronicle-owned record. Record Version is distinct from Schema Version.
The version of the schema governing the structure of a Chronicle-owned record.
An approved enumerated term used where consistency, interoperability, validation, or machine readability requires a governed vocabulary.
A structured connection between a Chronicle Entry, supporting record, Authoritative Record, or other referenced object.
The defined sequence of institutional states or procedures through which a Chronicle-owned record progresses over time.
The institutional act by which an approved Chronicle Entry is made publicly available after the separate Publication Gate decision.
A candidate concept for describing archival or preservation condition where a future operational need justifies it. Preservation State is not presently a frozen universal Chronicle state system.
Preservation of an Occurrence after it happened when later context establishes Preservation Eligibility.
Preservation of relationships, context, provenance, corrections, versions, and temporal order across Chronicle history.
A downstream discovery view that organizes published Chronicle Entries chronologically. Timeline is not a separate canonical historical object.
Durable preservation of historically significant context, relationships, decisions, milestones, records, and changes needed to understand Satoshium over time.
The ability to reconstruct relationships among Chronicle Entries, authoritative records, Sources, Evidence, Provenance, Verification, Corrections, Versions, and publication history.
Chronicle uses several distinct institutional states. These concepts should not be collapsed into one generalized status field.
Chronicle may reference authoritative objects from across the Satoshium Suite, but the originating system retains institutional authority.
Chronicle's first production Entry confirms the practical separation of several core terms:
These terms describe different institutional concepts and should not be collapsed into a generalized status field.
Chronicle terminology exists to preserve architectural precision across documentation, records, schemas, validation, publication, and historical review.