Integrity Reference
Anchor's canonical operational object is the Integrity Reference, which preserves the governed integrity information associated with a defined artifact representation.
Anchor · Integrity Preservation
Satoshium Anchor Integrity Preservation
Integrity Preservation defines Anchor's enduring institutional function: preserving durable Integrity References for authoritative artifacts and records so their integrity can be independently reviewed over time.
Anchor is not defined by blockchain, Bitcoin, hashing, or signatures. Those may serve as implementation mechanisms. The institution is integrity preservation.
Canonical Representation
Integrity can be evaluated only when Anchor knows exactly what representation was anchored. The representation boundary must therefore be explicit and reproducible.
Integrity
Integrity means a reviewed artifact representation can be compared against a preserved Integrity Reference to determine whether the representation remains consistent with the anchored state.
Tamper Evidence
Anchor does not need to make every artifact immutable. It preserves enough evidence to make later alteration detectable, reviewable, and historically understandable.
The Institutional Role
Anchor preserves integrity context for artifacts owned by other Suite institutions and authoritative systems.
It does not create the substantive authority of the referenced artifact, certify its meaning, register it, preserve its historical interpretation, determine its trustworthiness, or redefine its lifecycle.
The institution is not blockchain. The institution is integrity preservation.
Cryptographic Digest
A cryptographic digest may represent the Integrity Value generated from a defined Canonical Representation using a governed hash algorithm.
Temporal Context
Anchor may preserve observation time, anchoring time, publication time, verification time, or other governed timestamps needed to interpret when integrity evidence was created or reviewed.
Signatures
Digital signatures may support integrity or origin verification, but a valid signature does not itself establish substantive truth, institutional authority, or trustworthiness.
Verification Material
Anchor may preserve algorithm information, digest values, signature references, canonicalization instructions, timestamp context, external commitments, and other data needed for reproducible integrity review.
Integrity Verification
Integrity Verification compares a reviewed artifact representation against the Integrity Reference governing that representation.
Reviewed Representation → Reproduce / Validate Integrity Material → Compare → Verification Result
A matching result supports integrity consistency. A mismatch requires investigation but does not automatically establish tampering, wrongdoing, or substantive invalidity.
Integrity vs. Truth
A record can be cryptographically intact and still contain incorrect information. Integrity does not determine substantive truth.
Integrity vs. Certification
Anchor verifies integrity relationships. Certifier performs certification under Suite Standards and Suite Methodology.
Integrity vs. History
Anchor preserves integrity context. Chronicle preserves qualifying historical Occurrences through canonical Chronicle Entries.
Integrity vs. Trust
Anchor may provide integrity evidence useful to later trust evaluation, but Attestor owns Trust Statements and Anchor does not determine reputation or trustworthiness.
What Integrity Preservation Supports
Anchor may preserve Integrity References for authoritative artifacts produced across the Satoshium Suite.
Atlas Records · Certification Packages · SCPRs · SCRs · SCRDs · Satoshium Registry Entries · Chronicle Entries · Discovery Artifacts · Trust Statements · Workflow Definitions
Not every derived artifact requires a separate Integrity Reference. Anchor should preserve only the structure necessary to provide durable, reviewable integrity value.
Source Authority
The artifact being anchored remains authoritative within the institution that created and maintains it.
Anchor owns only its own Integrity Reference and Anchor-controlled integrity metadata.
Reference does not transfer authority.
Artifact Changes and Integrity Lineage
An authoritative artifact may legitimately change after an Integrity Reference is created through a new Version, Correction, lifecycle change, republication, migration, or new canonical representation.
A later change does not invalidate the historical Integrity Reference. Anchor should preserve enough lineage to identify which representation was anchored, which Integrity Reference covered it, and how later representations relate to that earlier state.
Implementation Neutrality
Anchor should remain institutionally defined by integrity rather than by any one technical implementation.
Hashing, signatures, timestamping, transparency logs, Merkle structures, distributed systems, or future Bitcoin commitments may all support Anchor.
Tools may change. Integrity preservation remains the purpose.
Bitcoin and Anchor
Bitcoin may eventually provide an external commitment layer for Anchor, including proof-of-existence, timestamp anchoring, Merkle-root commitments, or long-term independently verifiable integrity references.
Bitcoin should be treated as an implementation or commitment mechanism, not as the definition of Anchor itself.
Integrity Preservation Principle
Anchor should preserve enough information that integrity can still be independently reviewed after the original moment has passed.
Integrity is preserved when change becomes visible.
Purpose →
Definitions →
Back to Anchor →