Correction
A correction is a governed activity addressing an identified error or required change in an Attestor-owned object while preserving prior state, traceability, and the applicable Lifecycle and Versioning rules.
Established ActivityAttestor · Operational Corrections
Corrections
Corrections provide governed mechanisms for addressing errors, clarifications, withdrawals, supersession, and other changes affecting Attestor's own Attestations and Trust Statements.
A correction should change the current interpretation or status of an Attestor object without silently erasing what previously existed, why it changed, or who authorized the change.
Authority boundary: Attestor corrects Attestor-owned objects.
It does not correct authoritative objects owned by other Suite institutions.
Clarification
A clarification may refine wording, scope, context, or interpretation without materially changing the underlying institutional meaning. Materiality determines whether the same canonical object may continue or a new object is required.
Governed ChangeWithdrawal
Withdrawal is an adopted Lifecycle State used when an Attestor object should no longer remain active under applicable rules. Withdrawal remains attributable, preserved, and historically traceable.
Lifecycle StateSupersession
Superseded is an adopted Lifecycle State. Supersession may also be expressed
through the supersedes relationship when a later governed object
replaces an earlier object's institutional role. Prior state remains preserved.
Provenance of Change
Corrections and related changes preserve, as applicable, what changed, why it changed, who or what authorized the change, when it changed, which canonical object or governed state was affected, and the relationship between prior and resulting states.
Established RequirementHistorical Traceability
Prior governed states remain traceable so reviewers can distinguish historical state from current state. Supersession, withdrawal, retirement, or unpublication does not silently erase the prior governed record.
Established RequirementCorrection Is Not a New Canonical Object
Attestor does not establish a separate “Correction Record” as an additional canonical object class. Correction is a governed activity expressed through the applicable Lifecycle, Versioning, Relationship, Attestation, and Trust Statement architecture.
Attestor's canonical objects remain: Attestation + Trust Statement.
Correction Does Not Rewrite Source Authority
If a referenced Certification Package, Registry record, Chronicle Entry, Anchor Integrity Reference, Beacon Discovery Signal or Discovery Metadata, or another governed source changes, Attestor may update its own evaluation or issue a correction, withdrawal, or superseding Trust Statement as appropriate.
Attestor does not alter the originating object. The source institution remains responsible for its own correction and lifecycle rules.
Reference does not transfer authority.
Current State and Historical State
Correction architecture preserves both the currently effective Attestor state and historically relevant prior states. Preserving history does not present a superseded, withdrawn, retired, or otherwise non-current object as current.
Prior State → Governed Change → Current State
Provenance and relationship remain visible across the transition.
Provenance and relationship remain visible across the transition.
First Production Correction Demonstration
The first controlled production operation identified a defect in the relationship representation of ATT-2026-0001 and TRST-2026-0001. Early representations used descriptive relationship strings where structured relationship blocks were required for the canonical production representation.
Defect → Relationship serialization
Governed response → Correct representation
Corrected form → Explicit relationship type + target identifier
Canonical ATT identity → Preserved
Canonical TRST identity → Preserved
Attestation assertion → Unchanged
Trust Statement conclusion → Unchanged
Historical representations → Preserved
Version → V1.0 retained by governed materiality determination
Correction architecture → DEMONSTRATED IN PRODUCTION
Governed response → Correct representation
Corrected form → Explicit relationship type + target identifier
Canonical ATT identity → Preserved
Canonical TRST identity → Preserved
Attestation assertion → Unchanged
Trust Statement conclusion → Unchanged
Historical representations → Preserved
Version → V1.0 retained by governed materiality determination
Correction architecture → DEMONSTRATED IN PRODUCTION
The operation demonstrated that correction reason and versioning consequence are separate governed decisions. The existence of a defect required correction, but the bounded serialization-only nature of that defect did not require a new canonical ATT, a new canonical TRST, or a new version in this operation.
Correction Record and Historical Integrity
The production correction did not create a new canonical Correction Record. Correction remained a governed activity documented through the operation's preserved artifacts, relationship remediation, versioning determination, and historical evidence. Earlier representations were retained rather than silently overwritten.
Separate canonical Correction Record → Not adopted
Correction Attestation type → Not required by first production operation
Prior representation → Preserved
Corrected representation → Distinguishable
Correction reason → Reviewable
Versioning decision → Separately reviewable
Correction ≠ Deletion
Correction ≠ Silent Overwrite
Correction ≠ Automatic New Canonical Object
Correction Attestation type → Not required by first production operation
Prior representation → Preserved
Corrected representation → Distinguishable
Correction reason → Reviewable
Versioning decision → Separately reviewable
Correction ≠ Deletion
Correction ≠ Silent Overwrite
Correction ≠ Automatic New Canonical Object
Established Correction Architecture
Attestor governs correction through Lifecycle, Versioning, Relationships, Provenance, Validation, and Publication. Correction is an activity rather than a lifecycle state or separate canonical object class, and the first production operation has now exercised this architecture.
Correction explains why governed change occurs.
Versioning determines how canonical identity behaves across that change.
Correction ≠ Version
Versioning determines how canonical identity behaves across that change.
Correction ≠ Version
A materially changed Attestation assertion requires a new ATT-YYYY-NNNN. A materially changed Trust Statement conclusion requires a new TRST-YYYY-NNNN. A bounded correction may preserve canonical identity when essential institutional meaning remains intact and the applicable Versioning determination permits it.
Corrections → Established and Production-Proven
Correction as governed activity → Established and exercised
Separate Correction Record → Not adopted
Correction Attestation mechanism → Not required by first production operation
Provenance of change → Exercised
Historical traceability → Exercised
No silent overwrite → Demonstrated
Correction / Versioning distinction → Demonstrated
Bounded serialization correction → Exercised
Withdrawal / supersession correction paths → Established but not exercised in first production
Production proof → ESTABLISHED
Correction as governed activity → Established and exercised
Separate Correction Record → Not adopted
Correction Attestation mechanism → Not required by first production operation
Provenance of change → Exercised
Historical traceability → Exercised
No silent overwrite → Demonstrated
Correction / Versioning distinction → Demonstrated
Bounded serialization correction → Exercised
Withdrawal / supersession correction paths → Established but not exercised in first production
Production proof → ESTABLISHED
Production proof does not make every future correction non-material. Each correction must independently determine authority, materiality, version consequences, lifecycle effects, publication consequences, and whether a new canonical object is required.
Back to Attestor →