The Chronicle Entry Model defines the canonical conceptual structure of a Chronicle Entry and is implemented through the Chronicle Base Schema and, where applicable, an Event-Type Profile.
The model establishes which logical components every Entry must contain, which components become required only under defined conditions, and which components remain optional when they add meaningful historical context.
A Chronicle Entry is the canonical historical-preservation object of Chronicle. It represents one qualifying historical Occurrence.
The Entry Model defines the conceptual anatomy of that canonical object. Formal field names, identifier syntax, Controlled Values, machine-readable structure, and Validation requirements are governed by Chronicle's production schemas and institutional specifications.
Optional does not mean unimportant. It means the component is not universally applicable to every Chronicle Entry.
Establishes the stable identity of the Chronicle Entry and distinguishes it from every other Chronicle-owned record.
Identity conceptually includes the Entry identifier, Entry title or label, governing schema version, and Entry version.
RequiredDescribes the qualifying Occurrence being preserved: what happened, what changed, or what historically significant state or milestone the Entry represents.
RequiredPreserves when the underlying Occurrence happened and distinguishes that time from when Chronicle created, validated, published, corrected, or versioned the Entry.
RequiredClassifies the Occurrence using an approved Chronicle Event Type and determines whether an Event-Type Profile applies.
RequiredExplains why the Occurrence matters and provides the surrounding institutional, temporal, relational, or historical context needed to understand it.
RequiredConnects the Entry to Chronicle Source Records documenting where supporting information originated.
ConditionalConnects the Entry to other Chronicle Entries, supporting Chronicle records, authoritative Suite objects, or other referenced records when those relationships are historically meaningful.
ConditionalDocuments how information, authoritative references, Sources, Evidence, or other material originated, moved, and entered Chronicle.
RequiredConnects the Entry to Evidence Records or other approved Evidence structures that support, challenge, contradict, clarify, corroborate, contextualize, or limit confidence.
ConditionalRecords Chronicle's review of its own historical representation, including verification state, review context, limitations, and applicable references.
RequiredIdentifies the preserved state of the Chronicle Entry and supports traceable lineage when the Entry changes over time.
RequiredConnects the Entry to Correction Records and prior or resulting versions when Chronicle has materially corrected its own historical record.
ConditionalIdentifies the Entry's state within Chronicle's publication process and distinguishes publication from Verification, Validation, lifecycle, and preservation state.
RequiredRepresents the Entry's institutional lifecycle condition within Chronicle, independent of Verification State, Publication State, Validation result, or the lifecycle/status of the underlying object preserved by the Entry.
RequiredEvery production Chronicle Entry should contain the conceptual components needed to identify the Entry, represent the Occurrence, establish time, classify the event, explain historical context, preserve provenance, support review, maintain version lineage, and express publication and lifecycle state.
Conditional components become required when the nature of the Entry, its Event-Type Profile, its history, or its supporting material makes them applicable.
An Event-Type Profile may convert a normally conditional component into a required component for that Event Type.
Optional components may be added when they improve historical understanding without being universally required across all Chronicle Entries.
Examples may later include supplemental notes, public-facing summaries, interpretive context, archival annotations, display metadata, or other approved extensions.
A Chronicle Entry may reference authoritative records from other Suite systems, but those references do not transfer institutional authority to Chronicle.
The Entry Model must preserve the distinction between the time of the underlying Occurrence and Chronicle's own recordkeeping actions.
This distinction is essential for retrospective preservation.
The Entry Model defines the logical structure. The Chronicle Base Schema translates that model into formal fields, required properties, data types, Controlled Values, Relationships, and machine-readable Validation rules. Event-Type Profiles specialize the Base Schema for governed Event Types.
The Entry Model has now been exercised through CHR-2026-0001 Entry Version 1.
The production Entry confirmed that the same canonical Chronicle Entry can carry the required historical, structural, traceability, review, and lifecycle components without creating a competing canonical “Event” or generic Status object.
Every Chronicle Entry should contain enough structure to remain identifiable, understandable, traceable, reviewable, correctable, versioned, and preservable across time.
Back to Chronicle →