Purpose
The Anchoring Process provides the repeatable institutional path for creating an Integrity Reference without transferring authority away from the system that owns the referenced artifact.
Anchor · Anchoring Process
Satoshium Anchor Anchoring Process
The Anchoring Process defines how an authoritative artifact becomes associated with a durable Anchor Integrity Reference.
The process begins with source authority and representation definition, not with hashing. Integrity is meaningful only when Anchor knows exactly what is being referenced and why that representation is stable enough to verify later.
Process Boundary
Anchor does not create the substantive artifact or determine what it means. Anchor begins when a candidate artifact is identified for integrity preservation.
Authority First
Before integrity material is generated, Anchor must identify the Source Institution and confirm which artifact is authoritative for the representation being anchored.
Verification Goal
The process exists so a future reviewer can reproduce or validate integrity material and compare a reviewed representation with the Integrity Reference.
Anchoring Sequence
The production Anchoring Process is now:
Identify Authoritative Artifact
↓
Confirm Source Authority
↓
Define Canonical Representation
↓
Define Representation Boundary
↓
Select Integrity Method / Algorithm
↓
Generate Integrity Value
↓
Construct Integrity Reference Candidate
↓
Assign Anchor Identifier + Anchor Version
↓
Stage A — Structural / Institutional Validation
↓
Initial Verification
↓
Canonical HTML + Canonical JSON
↓
Stage B — Publication-Readiness Validation
↓
Publication Gate
↓
Publication / Preservation
↓
Maintenance / Reverification / Lineage
↓
Confirm Source Authority
↓
Define Canonical Representation
↓
Define Representation Boundary
↓
Select Integrity Method / Algorithm
↓
Generate Integrity Value
↓
Construct Integrity Reference Candidate
↓
Assign Anchor Identifier + Anchor Version
↓
Stage A — Structural / Institutional Validation
↓
Initial Verification
↓
Canonical HTML + Canonical JSON
↓
Stage B — Publication-Readiness Validation
↓
Publication Gate
↓
Publication / Preservation
↓
Maintenance / Reverification / Lineage
This sequence is no longer conceptual only; it is aligned with Anchor's completed Validation, Verification, Publication, Versioning, Procedures, and first-production architecture.
1. Identify Authoritative Artifact
Identify the record, package, file, publication, statement, dataset, or other governed object whose integrity should be preserved.
2. Confirm Source Authority
Confirm the Source Institution, Source-System Identifier where one exists, artifact type, and authority boundary before Anchor creates its own Integrity Reference.
3. Define Canonical Representation
Determine the exact representation processed for integrity. For the first production candidate:
Source Artifact → SCRD-SC-CERT-2026-0001
Representation Type → canonical_json
Canonicalization → RFC 8785 JCS
Encoding → UTF-8
Representation Type → canonical_json
Canonicalization → RFC 8785 JCS
Encoding → UTF-8
4. Define Representation Boundary
Explicitly identify what content is covered by the Integrity Reference. For IR #1, the boundary is:
complete SCRD JSON document
Linked Certification Package, SCPR, SCR, SCRD HTML, Atlas, Registry, and Chronicle records remain outside this Representation Boundary unless separately anchored.
5. Select Integrity Method
Select the governed integrity mechanism and algorithm. For IR #1:
Integrity Method → cryptographic_digest
Digest Algorithm → SHA-256
Digest Encoding → lowercase hexadecimal
Digest Algorithm → SHA-256
Digest Encoding → lowercase hexadecimal
SHA-256 is the Suite's initial approved interoperable digest algorithm, not a permanent definition of Anchor.
6. Generate Integrity Value
Generate the Integrity Value from the governed Canonical Representation.
SCRD JSON
↓
RFC 8785 JCS
↓
UTF-8 canonical byte sequence
↓
SHA-256
↓
64-character lowercase hexadecimal Integrity Value
↓
RFC 8785 JCS
↓
UTF-8 canonical byte sequence
↓
SHA-256
↓
64-character lowercase hexadecimal Integrity Value
7. Record Verification Material
Record the metadata needed to reproduce or validate the integrity result, including algorithm information, timestamps, signatures, representation instructions, and external commitment references where applicable.
8. Construct Integrity Reference Candidate
Assemble the Anchor-owned Integrity Reference candidate under the Base Schema. For the first production record:
Anchor Identifier → ANCH-2026-0001
Anchor Version → 1
Source → SCRD-SC-CERT-2026-0001
Relationship → references_source
Representation Type → canonical_json
Integrity Method → cryptographic_digest
Anchor Version → 1
Source → SCRD-SC-CERT-2026-0001
Relationship → references_source
Representation Type → canonical_json
Integrity Method → cryptographic_digest
9. Validate and Verify Construction
Construction now uses the staged production model:
Stage A Validation
↓
Initial Verification
↓
expected successful Verification Result → match
↓
Stage B Publication-Readiness Validation
↓
Initial Verification
↓
expected successful Verification Result → match
↓
Stage B Publication-Readiness Validation
Validation evaluates institutional and schema conformance. Verification tests whether the reconstructed Canonical Representation reproduces the preserved Integrity Value.
10. Publication Gate and Publish / Preserve
A candidate proceeds to publication only after final Validation PASS and Publication Gate approval.
Stage B Validation PASS
↓
Human / Machine consistency confirmed
↓
Publication Gate
↓
APPROVED
↓
Publication
↓
Human / Machine consistency confirmed
↓
Publication Gate
↓
APPROVED
↓
Publication
Publication changes the Anchor Publication State from unpublished to published and makes the approved Anchor Version publicly authoritative for its own Integrity Reference metadata.
11. Maintain / Reverify
Review the Integrity Reference when the Source Artifact changes, a reference breaks, an algorithm becomes unsuitable, verification fails, or later integrity review is institutionally required.
12. Preserve Lineage
Preserve prior material states, Corrections, Versions, verification history, and later Integrity References so the integrity history remains reconstructable over time.
What the Process Produces
The Anchoring Process produces an Anchor-owned Integrity Reference.
Anchor Identifier
Anchor Version
Schema Version
Source Object
Canonical Representation
Representation Boundary
Integrity Method + Algorithm
Integrity Value
Provenance
Relationships
Record State
Verification History
Publication / Maintenance metadata where applicable
Anchor Version
Schema Version
Source Object
Canonical Representation
Representation Boundary
Integrity Method + Algorithm
Integrity Value
Provenance
Relationships
Record State
Verification History
Publication / Maintenance metadata where applicable
The Integrity Reference Base Schema now defines this production structure.
Canonical Representation Comes Before Hashing
A hash is useful only when a later reviewer can determine exactly what representation produced it.
Anchor therefore does not treat:
"Hash this record"
as a sufficient institutional instruction.
The process must first establish:
Which artifact? → Which authoritative source? → Which exact representation? → Which boundary? → Which governed method?
Hashes
Hashing may generate a deterministic Integrity Value for a defined Canonical Representation. Hashing is a mechanism within the process, not the process itself.
Timestamps
Timestamps preserve temporal context and should be labeled by meaning, such as anchoring time, observation time, publication time, or verification time.
Signatures
Signatures may support integrity or origin verification. They do not automatically establish substantive authority, truth, certification, reputation, or trust.
External Commitments
External commitments, including possible future Bitcoin commitments, may strengthen long-term independently reviewable integrity without defining Anchor's institutional identity.
Source Artifact Changes
A Source Artifact may legitimately change after an Integrity Reference is created.
A later Source Artifact Version, Correction, lifecycle change, migration, or new canonical representation does not erase the earlier integrity relationship.
Preserve which representation was anchored, which Integrity Reference covered it, and how later representations relate to that state.
Verification After Anchoring
Later Integrity Verification begins with the preserved Integrity Reference and the artifact representation under review.
Integrity Reference + Reviewed Representation → Reproduce / Validate Integrity Material → Compare → Verification Result
A match supports integrity consistency. A mismatch requires investigation.
A mismatch does not automatically establish tampering, wrongdoing, falsity, or loss of institutional authority.
Authority Boundary
Anchor owns the Integrity Reference.
The Source Institution continues to own the authoritative artifact and its substantive status, meaning, certification, historical interpretation, or trust context.
Reference does not transfer authority.
First Production Application — ANCH-2026-0001
Source Institution → Satoshium Certifier
Source Artifact → SCRD-SC-CERT-2026-0001
Source Version → 1.1
Representation Boundary → complete SCRD JSON document
Representation Type → canonical_json
Canonicalization → RFC 8785 JCS
Encoding → UTF-8
Integrity Method → cryptographic_digest
Algorithm → SHA-256
Digest Encoding → lowercase hexadecimal
Relationship → references_source
Anchor Identifier → ANCH-2026-0001
Anchor Version → 1
Source Artifact → SCRD-SC-CERT-2026-0001
Source Version → 1.1
Representation Boundary → complete SCRD JSON document
Representation Type → canonical_json
Canonicalization → RFC 8785 JCS
Encoding → UTF-8
Integrity Method → cryptographic_digest
Algorithm → SHA-256
Digest Encoding → lowercase hexadecimal
Relationship → references_source
Anchor Identifier → ANCH-2026-0001
Anchor Version → 1
This candidate is assigned but not yet published. It must still complete Stage A Validation, Initial Verification, Stage B Publication-Readiness Validation, and the Publication Gate.
Process Philosophy
Anchoring is not a declaration of truth. It is the governed creation of a durable integrity relationship between an Anchor Integrity Reference and a defined artifact representation.
The process should remain reproducible, reviewable, implementation-neutral, and minimal enough to preserve integrity without duplicating the authoritative record.
Define the representation. Generate the integrity evidence. Preserve the reference. Make later verification possible.
Purpose →
Definitions →
Integrity Preservation →
Back to Anchor →