Preservation Eligibility is Chronicle's institutional admission rule. It determines whether an Occurrence should become part of the Chronicle historical record through a canonical Chronicle Entry.
Historical Significance is treated within this model as a principal rationale for preservation rather than as a separate institutional system.
Preservation Eligibility is assessed before a production Chronicle Entry is created. It prevents Chronicle from becoming a universal activity log while preserving room for historically meaningful Occurrences that deserve institutional memory.
The eligibility decision determines admission to Chronicle. The Entry Model determines the structure of the record after admission.
The Occurrence materially relates to Satoshium, a Suite institution, an authoritative Suite object, governance, architecture, public operation, or another recognized area of institutional history.
Eligibility FactorThe Occurrence has enduring value for understanding how Satoshium developed, changed, operated, or established institutional continuity.
Eligibility FactorThe Occurrence represents a meaningful creation, renewal, suspension, revocation, expiration, transition, completion, or other historically relevant lifecycle milestone.
Eligibility FactorThe Occurrence is the first, last, largest, earliest, inaugural, terminal, threshold-crossing, or otherwise historically distinctive milestone of its kind.
Eligibility FactorThe Occurrence materially changes rules, standards, institutional responsibilities, architecture, interoperability, policy, or another foundational element.
Eligibility FactorThe Occurrence establishes, changes, or terminates a historically meaningful relationship among Suite institutions, records, systems, or authoritative objects.
Eligibility FactorPreserving the Occurrence materially improves later understanding of another historical Entry, institutional development, disputed interpretation, or major historical sequence.
Eligibility FactorThe Occurrence fills a meaningful gap needed to reconstruct Chronicle history across time, even if the event appears less significant when viewed in isolation.
Eligibility FactorChronicle does not require every eligible Occurrence to satisfy every factor. Eligibility should depend on an approved preservation basis appropriate to the Event Type and historical circumstances.
Chronicle may approve limited classes of Occurrences for which preservation is presumed or automatically required because their historical value is already institutionally established.
Automatic classes should remain narrow and governed. They should be created only after operational experience demonstrates that repeated individual eligibility review would add little value.
Automatic preservation removes the need to re-decide historical importance, but the resulting Chronicle Entry must still satisfy Entry Model, authority, Provenance, Verification, Validation, publication, and other production rules.
No broad automatic preservation catalog should be frozen yet. Certification operational experience should determine whether specific certification milestones warrant automatic treatment.
Occurrences outside an automatic class may still qualify through discretionary Preservation Eligibility review.
Discretionary review should document the preservation rationale rather than relying on intuition alone.
When Historical Significance supports preservation, Chronicle should preserve a concise rationale explaining why the Occurrence has enduring historical value.
The rationale should identify the relevant significance basis without attempting to create an artificial universal importance score.
An Occurrence should ordinarily be excluded when preservation would add little or no durable historical value or would duplicate information already adequately represented elsewhere.
Normal operational actions should not become Chronicle Entries merely because they occurred or generated system records.
Minor changes with no meaningful historical, institutional, lifecycle, relational, or continuity value should ordinarily remain outside Chronicle.
Chronicle should not create multiple Entries for the same Occurrence merely because multiple Sources, records, or references describe it.
Routine formatting changes, metadata maintenance, internal processing actions, automated checks, and similar administrative events ordinarily belong in logs or operational records rather than Chronicle.
Predictions, rumors, or imagined future developments should not become historical Entries merely because they may later prove important.
An Occurrence outside Chronicle's institutional scope should not be admitted unless a legitimate historical relationship to Satoshium brings it within Scope.
Multiple records, Sources, Evidence items, or Suite references may describe the same underlying Occurrence. Chronicle should ordinarily preserve one canonical Chronicle Entry for that Occurrence and attach the relevant supporting relationships.
A later development should receive a separate Entry only when it represents a distinct qualifying Occurrence rather than additional information about the original one.
Triviality should be assessed in historical context rather than by event size alone. A small technical action may become historically important if it represents a first, final transition, governance milestone, or necessary continuity point.
Event Type classifies the Occurrence. Preservation Eligibility decides whether Chronicle should preserve it.
Matching an approved Event Type does not automatically guarantee preservation unless Chronicle has explicitly designated that Event Type or class as automatic.
Preservation Eligibility is distinct from Evidence sufficiency. An Occurrence may be historically important even when Evidence is incomplete, disputed, or limited.
Chronicle should preserve those limitations transparently rather than using evidentiary uncertainty as an automatic substitute for the eligibility decision.
An Occurrence may become eligible later when subsequent history reveals significance that was not apparent at the time.
The Preservation Eligibility decision should result in a clear institutional outcome.
Final decision-state terminology should be established through Chronicle Controlled Values.
Chronicle's Preservation Eligibility model has now been exercised in production. On August 22, 2026, the July 5, 2026 issuance of SC-CERT-2026-0001 was formally determined ELIGIBLE for preservation and became the Occurrence represented by Chronicle's first canonical published production Entry: CHR-2026-0001.
The production case confirmed the model's central distinction: Preservation Eligibility determines whether Chronicle should preserve an Occurrence; it does not re-perform Certifier's certification analysis, determine Evidence sufficiency, perform Verification, perform Validation, or authorize Publication.
Open CHR-2026-0001 →Chronicle should preserve enough history to maintain institutional memory, but not so much activity that history becomes indistinguishable from operational noise.