Chronicle · Entries

Satoshium Chronicle Entries

The Chronicle Entries collection is the public production surface for Satoshium Chronicle’s canonical historical-preservation records. Each published Entry represents one qualifying Occurrence that Chronicle has determined should be preserved as part of the historical record. The collection is now operational with CHR-2026-0001 as its first published production Entry.

Chronicle preserves the historical representation, context, Relationships, Provenance, Verification, Validation context, publication lineage, Corrections, and Entry Versions while leaving authoritative actions and records under the control of the Suite institutions that created them.

Production Status

Operational · First Production Entry Published

Chronicle has completed its first full production cycle from Occurrence identification through Preservation Eligibility, authoritative-reference collection, Event Type classification, Event-Type Profile selection, permanent Chronicle identifier assignment, Entry construction, Relationships, Sources / Evidence / Provenance, formal Verification, formal Validation, the separate Publication Gate, and Publication.

The first published production Chronicle Entry is CHR-2026-0001, preserving the July 5, 2026 creation of Certification Package SC-CERT-2026-0001.

CHR-2026-0001 · Entry Version 1 · active · verified · Validation PASS · Publication Gate APPROVED · published August 22, 2026 at 8:38 AM PDT.

The earlier August 20 operational dry run remains part of Chronicle’s institutional history. During that dry run, CHR-2026-0001 was only a simulated candidate and was not assigned or reserved. Formal production identity began with the August 22, 2026 assignment.

Canonical Object

Chronicle Entry is the canonical record object created and maintained by Chronicle. The Entry is not the Occurrence itself; it is Chronicle’s structured historical-preservation record representing that qualifying Occurrence.

Authority Boundary

A Chronicle Entry is authoritative only as Chronicle’s historical-preservation record. Certifier, Registry, Anchor, Beacon, Attestor, Navigator, Atlas, and external institutions remain authoritative for the objects and actions within their own responsibilities.

Reference does not transfer authority.

Production Contract

Every production Entry is governed by the Chronicle Base Schema and, where applicable, an approved Event-Type Profile. Required, Conditional, and Optional fields are determined by those governing machine-readable and institutional rules.

Identity and Versioning

Production Entries use permanent identifiers in the form CHR-YYYY-NNNN. The identifier remains stable across material Corrections and Entry Versions. Entry Version is distinct from Schema Version.

Verification

Verification reviews Chronicle’s own historical representation: whether it is adequately supported, internally coherent, traceable, temporally consistent, relationship-aware, and appropriately limited.

Validation

Validation determines whether the current Entry Version conforms to the governing Base Schema, applicable Event-Type Profile, Controlled Values, authoritative-reference rules, temporal requirements, Relationships, Provenance, Version / Correction rules, authority boundaries, and publication prerequisites.

Production Entry Package

Every published Chronicle Entry preserves a minimal canonical Entry package together with durable procedural artifacts when they provide real institutional value.

/chronicle/entries/CHR-YYYY-NNNN/
├── index.html — official human-readable Chronicle Entry
├── record.json — official machine-readable Chronicle Entry
├── README.md — institutional / repository documentation
├── CHR-YYYY-NNNN-vN-validation.md — durable Validation artifact for the Entry Version
└── CHR-YYYY-NNNN-vN-publication-gate.md — durable Publication Gate decision for the Entry Version

The canonical Chronicle Entry remains the coordinated index.html, record.json, and README.md representation. Validation and Publication Gate files are supporting procedural artifacts associated with a specific Entry Version; they are not separate Chronicle Entries and do not receive independent Chronicle identifiers.

Minimum necessary structure remains the governing principle. Additional Verification, Source, Evidence, Provenance, Correction, or Version artifacts are created only when their additional structure provides durable institutional value.

Entry Production Path

A production Chronicle Entry follows the documented Chronicle Entry Production Procedure.

Identify Occurrence → Assess Preservation Eligibility → Collect Authoritative References → Classify Event Type → Select Event-Type Profile → Assign Chronicle Identifier → Create Entry → Establish Relationships → Record Sources / Evidence / Provenance → Perform Verification → Perform Validation → Publication Gate → Publish → Preserve

Publication Readiness and Publication Gate

Chronicle keeps Validation readiness and publication approval separate.

CHR-VAL-011 — Publication Readiness
Tests whether publication prerequisites are satisfied from a Validation standpoint.

Chronicle Publication Gate
Makes the separate institutional decision to approve or withhold Publication.

The formal Publication Gate requires:

Required Verification State + Validation PASS + Required Authoritative References + Publication Prerequisites = Eligible for Publication

Validation PASS does not itself approve or publish an Entry.

Published Entries

Published Chronicle Entries appear here after completing the governed production procedure, formal Verification, formal Validation, the separate Publication Gate, and the Publication state transition.

CHR-2026-0001 · Creation of SC-CERT-2026-0001

Entry Version: 1 Event Type: certification_created Event Date: July 5, 2026 Lifecycle: active Verification: verified Validation: PASS Publication Gate: APPROVED Publication: published Published: August 22, 2026 · 8:38 AM PDT

Preserves the inaugural Operational certification issued by Satoshium Certifier for the Satoshium Atlas Jurisdiction Record — El Salvador. Certifier remains authoritative for SC-CERT-2026-0001, Registry remains authoritative for SREG-2026-0001, Atlas remains authoritative for the underlying jurisdiction record, and Chronicle owns the historical-preservation representation.

Open Chronicle Entry → Open Machine-Readable Record → Open README →

Maintenance After Publication

Publication does not end Chronicle responsibility. New Evidence, corrected Provenance, Relationship changes, classification corrections, authoritative external changes, schema migration, or other material developments may require maintenance.

Published Entry → New Information / Defect → Materiality Review → Editorial Update / Formal Correction / New Entry Version / New Chronicle Entry → Reverification where required → Revalidation → Publication decision → Preserve prior material state

Correct forward. Preserve backward.

Entry Philosophy

Chronicle preserves qualifying historical memory without assuming authority belonging to another Suite institution. Historical Context may explain why an Occurrence matters, but interpretation remains distinguishable from authoritative fact, Source material, Evidence, Verification, and Validation.

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

Schema defines structure. Verification reviews the representation. Validation tests conformance. Publication determines public production state.

Open Entry Model → Open Validation → Open Identifiers → Back to Chronicle →