Record is an umbrella term for structured information maintained within Chronicle. The canonical historical-preservation object is the Chronicle Entry. Supporting Source, Evidence, and Correction records may be created where their additional structure provides real institutional value, while Verification, Validation, Provenance, Relationships, Versions, and publication state remain governed aspects of Chronicle's handling of the Entry.
Not every referenced object becomes a Chronicle-owned record. Chronicle may maintain its own supporting records while referencing authoritative objects owned by Certifier, Registry, Atlas, Anchor, Beacon, Attestor, Navigator, and other Suite systems.
The Chronicle Entry is the canonical record object through which Chronicle preserves a qualifying historical Occurrence. Supporting records exist only where they perform a distinct operational function and should never become a competing historical-preservation object.
Chronicle records should preserve traceable connections among Entries, Sources, Evidence, Provenance, Verification, Validation, Corrections, Versions, publication lineage, and authoritative Suite references so historical context remains reconstructable.
Chronicle records should remain reviewable and understandable, including Provenance, Version lineage, Correction history, Relationships to authoritative records, Verification State, Validation result where material, and Publication State.
Chronicle records are authoritative only within Chronicle’s own institutional scope. Referenced Certification Packages, SREGs, Integrity References, Trust Statements, Discovery Signals, Workflow Definitions, Atlas records, and other Suite objects remain authoritative within their originating systems.
Chronicle records may connect with one another and with authoritative external Suite objects through stable references. Relationships preserve context without transferring ownership or authority between institutions.
Chronicle records support historical continuity by preserving how Entries, Evidence, Relationships, Provenance, Verification, Validation, Corrections, Versions, and publication states evolved over time.
Chronicle Records follow Satoshium Suite standards for stable objects, canonical terminology, structured schemas, durable identifiers, Version preservation, explicit Validation, authority-aware references, and documented repeatable production procedures.
Suite Interoperability requires reference-based design: Chronicle references authoritative objects maintained by other Suite institutions rather than duplicating, replacing, or reinterpreting them.
Chronicle uses one canonical historical-preservation object together with supporting record classes that perform distinct functions. These supporting classes should not be confused with separate canonical Chronicle objects.
Chronicle should distinguish records it creates and governs from records it only references. It should also distinguish independently maintained supporting records from structures or process results that belong to the Chronicle Entry lifecycle.
A reference to an external record does not make that record part of Chronicle’s authority or lifecycle. Reference does not transfer authority.
The Chronicle Entry follows the documented Entry Lifecycle and Production Procedure while preserving prior substantive states where required. Supporting records should use only the lifecycle or Version structure actually required by their own operational function.
Chronicle's production Validation architecture defines the Validation Record as the information needed to reconstruct a Validation decision, but does not establish a new canonical Validation object or identifier namespace.
The initial implementation preserves full Validation detail through a lightweight institutional Validation artifact associated with the exact Entry Version. Minimal publication-facing Validation information may be referenced where useful.
Chronicle should not create a second canonical “Record” object above or beside the Chronicle Entry. “Record” is an architectural umbrella term, not a competing historical object.
Production historical preservation should remain centered on the Chronicle Entry. Supporting records exist only where they provide a distinct operational function. Verification, Validation, Relationships, Provenance, Versions, and Publication State should not be promoted into separate canonical objects merely for symmetry.
Chronicle's record architecture has now been exercised through CHR-2026-0001.
The first three files form the coordinated canonical Entry representation. The Validation and Publication Gate artifacts preserve durable procedural review for Entry Version 1 without becoming separate canonical Chronicle objects.
Chronicle favors durable, Version-aware preservation over silent deletion whenever practical. Chronicle-owned records provide value not only because they capture information, but because their Provenance, Relationships, Verification, Validation, Correction history, publication lineage, and Versions reveal how the historical record was maintained over time.
The goal is not to accumulate records for their own sake. The goal is to support coherent, reviewable Chronicle Entries and durable historical continuity.
Open Entries → Open Validation → Back to Chronicle →