Chronicle · Corrections

Satoshium Chronicle Corrections

Corrections improve Chronicle's own preservation records while preserving transparency, historical continuity, Provenance, Version lineage, and traceability.

Chronicle does not silently rewrite history. A Correction records what was wrong, what changed, why it changed, when it changed, which fields were affected, which Entry Version resulted, and whether Reverification or Revalidation was required.

Corrections in the Entry Production Procedure

Corrections are part of Chronicle maintenance rather than a separate preservation architecture.

Published Entry → New Information / Defect → Materiality Review → Editorial Update / Formal Correction / New Entry Version / New Chronicle Entry as appropriate → Reverification → Revalidation → Republish / Maintain / Withdraw → Preserve Prior Material State

The exact path depends on whether Chronicle is correcting its representation of the same Occurrence or preserving a distinct later Occurrence.

First Production Correction Baseline

CHR-2026-0001 Entry Version 1 established Chronicle's first production Correction baseline.

Prior Entry Version: None
Formal Chronicle Correction: None
CHR-VAL-010 — Correction and Version Consistency: Not Applicable

The initial production Entry therefore entered publication without a formal Correction lineage. Future material changes to Chronicle's representation will use the Correction and Versioning rules defined on this page rather than silently rewriting Entry Version 1.

A distinct later authoritative action—such as a future certification suspension, revocation, renewal, or expiration—would ordinarily be assessed as a new qualifying Occurrence and a new Chronicle Entry rather than treated as a Correction to the original certification-created Occurrence.

Correction Principle

Correct forward. Preserve backward.

Chronicle may improve its own record without pretending the earlier institutional state never existed.

Why Corrections Exist

Corrections address errors, omissions, misclassification, broken references, Provenance defects, Evidence issues, Relationship errors, inaccurate dates, Validation failures, publication defects, or other defects in Chronicle-owned records.

Authority Boundary

Chronicle corrects only its own Entries and Chronicle-owned supporting records. It does not correct, supersede, invalidate, or reinterpret authoritative objects owned by another Suite system.

Transparency

Reviewers should be able to identify what changed, why it changed, when it changed, which fields were affected, and which Version contains the corrected state.

Prior-State Preservation

Material prior states remain preserved so Chronicle's own historical evolution remains reviewable.

Required Correction Record

Every formal Chronicle Correction should preserve the following minimum information:

Original information · Corrected information · Correction date · Reason · Affected fields · Resulting Version · Reverification / Revalidation requirement where applicable

Original Information

Preserve the prior value, statement, relationship, classification, reference, or other material state being corrected.

Corrected Information

Preserve the replacement value or corrected representation that becomes part of the resulting Chronicle record state.

Correction Date

Record when Chronicle formally applied or approved the Correction.

Reason

Record why the Correction was necessary, including the issue discovered and the basis for the change.

Affected Fields

Identify the Entry or supporting-record fields changed by the Correction.

Resulting Version

Identify the Entry Version or supporting-record Version produced by the Correction when Versioning is required.

Correction Types

Correction Type should use the Chronicle Controlled Values Registry.

Typographical · Metadata · Contextual · Relationship · Provenance · Evidence · Classification · Substantive

Typographical

Corrects spelling, punctuation, or similar presentation defects without changing institutional meaning.

Metadata

Corrects structured metadata. Materiality determines whether a new Version is required.

Contextual

Corrects or improves Historical Context. A new Version is required when historical interpretation materially changes.

Relationship

Corrects Relationship Type, target, direction, or another material connection.

Provenance

Corrects origin, acquisition, retrieval, transformation, archive path, or other Provenance information.

Evidence

Corrects Evidence identity, Evidence Type, linkage, Source reference, limitation, or other evidentiary representation.

Classification

Corrects Event Type or another controlled classification without changing the Chronicle Entry identifier.

Substantive

Corrects material historical meaning and ordinarily requires a new Entry Version, Reverification, and Revalidation where applicable.

Correction and Versioning Are Different

Correction = Why Chronicle changed its record.
Version = The resulting preserved state of that record.

A Formal Correction and a new Version often occur together, but a minor non-substantive Correction may not require a new Version.

Materiality Rule

The deciding question is whether a future reviewer would reasonably need to know that the earlier Chronicle record said something materially different.

If yes → preserve prior state and create a new Version.

Minor Corrections

Minor Corrections may include typographical fixes, non-substantive formatting, broken-link repair, or minor metadata cleanup that does not change historical meaning.

Chronicle may use simplified Correction handling for these changes, but the boundary must never be used to hide a material historical change.

Substantive Corrections

A substantive Correction should ordinarily require:

Original state preserved → Correction documented → Supporting Source / Evidence reviewed → New Version created where required → Reverification where required → Revalidation → Publication decision / republication updated → Prior state preserved

Corrections After Validation Failure

A Validation FAIL identifies a nonconforming Chronicle representation. It does not delete the Entry or establish that the historical Occurrence is false.

Validation FAIL → Identify failed CHR-VAL rule → Return Entry for correction / completion / review → Reverify where required → Revalidate

Correction handling should address the specific failed requirement while preserving prior material states when the change is substantive.

No Silent Historical Rewriting

Chronicle must not silently alter substantive historical content.

Material changes to Event Date, Event Type, Event Representation, Historical Context, Sources, Evidence, Provenance, Relationships, Verification limitations, or other meaning-bearing fields require explicit Correction or Version lineage.

A changed record must leave evidence that it changed.

Correction Workflow

Issue / Validation Failure Identified → Authority Boundary Checked → Correction Type Assigned → Source / Evidence / Provenance Reviewed → Original State Preserved → Corrected State Prepared → Materiality Assessed → New Version if Required → Reverification where Required → Revalidation → Publication Decision / Republication Updated → Lineage Preserved

Corrections to Authoritative References

Chronicle may correct its own reference to an authoritative object if the identifier, originating system, description, or Relationship was wrong.

Chronicle does not alter the authoritative object itself.

Correct the reference. Do not re-adjudicate the authority.
Reference does not transfer authority.

Corrections Triggered by External Changes

If another Suite system changes its authoritative record, Chronicle should first determine whether that change is:

A correction to Chronicle's existing representation
or
A distinct later Occurrence requiring a new Chronicle Entry

Preservation Eligibility, Correction, Versioning, and Event classification rules determine the appropriate path. A distinct later authoritative action should ordinarily become a new Chronicle Entry rather than a Correction to the earlier Occurrence.

Correction Lineage

Correction lineage should allow future reviewers to reconstruct:

Prior Version · Correction · Changed fields · Corrected Version · Verification result · Validation result · Publication history

Corrections and Historical Preservation

Corrections become part of the Chronicle Entry's own institutional history. Corrected records should remain more accurate without becoming historically amnesiac.

Preserve what Chronicle said. Preserve why Chronicle changed it.
Corrections improve the record. Versioning preserves the lineage. History remains reviewable.