Anchor · Schemas

Satoshium Anchor · Schemas

Schema Architecture converts Anchor's canonical object—the Integrity Reference—from institutional concept into a formal machine-readable production structure.

The first schema is the Integrity Reference Base Schema, expressed in Markdown and JSON Schema Draft 2020-12.

Schema Principle

Structure the record now. Freeze policy only when downstream architecture proves it necessary.

Integrity Reference Base Schema

Defines the structural minimum for an Anchor Integrity Reference, including identity, Source, representation, integrity methods, provenance, relationships, state, Verification history, Corrections, Publication, and Maintenance.

1.0-draft · Production Reconciled

JSON Schema

Machine-readable schema using JSON Schema Draft 2020-12. The minimum Controlled Values proven necessary by the first production candidate are now schema-enforced.

Created

Markdown Specification

Human-readable companion explaining the meaning, authority boundary, required structure, extensibility, and intentionally unfrozen policy.

Created

Future Profiles

Method-specific or artifact-specific profiles may later extend the Base Schema when production proves that additional constraints are necessary.

Deferred

Top-Level Structure

Integrity Reference
├── anchor_identifier
├── anchor_version
├── schema_version
├── source
├── representation
├── integrity
├── provenance
├── relationships
├── record_state
├── verification_history
├── corrections
├── publication
├── maintenance
└── notes

Required Structural Core

anchor_identifier
anchor_version
schema_version
source
representation
integrity
provenance
relationships
record_state

schema_version is now required because formal Anchor Validation must identify the applicable schema for every production candidate.

Source

Preserves Source Institution, Source Artifact type, Source-System Identifier, Source Version, and canonical Source location where applicable.

Representation

Preserves Representation Type, Representation Boundary, canonicalization method, and representation metadata needed for reproducibility.

Integrity

Supports one or more Integrity Methods, algorithm metadata, Integrity Values, signatures, Verification Material, and external commitments.

Provenance

Formalizes Source, representation, generation, and optional Anchor-record provenance layers.

Relationships

Provides a repeatable machine-readable structure for internal Anchor, cross-Suite, and external commitment relationships.

Record State

Keeps Integrity State, Publication State, and Lifecycle State distinct rather than collapsing them into a generic status. Lifecycle State now uses the frozen initial production vocabulary.

Controlled Values — Minimum Production Set Enforced

The first production candidate has now proven which Controlled Values must be enforced before IR #1 is constructed.

representation_type → canonical_json
method_type → cryptographic_digest
integrity_state → current
verification_result → match
publication_state → unpublished · published
lifecycle_state → draft · active · superseded · withdrawn · archived
relationship_type → references_source

The relationships array must contain at least one references_source relationship.

Additional tokens remain unfrozen until production proves they are necessary.

Minimum Production Set Enforced

Structural Strictness

Governed objects reject unspecified fields where practical. Extension-oriented method data remains open where future technologies require method-specific information.

Stable institutional structure + controlled implementation extensibility

External Commitments

The Base Schema supports external commitment evidence without defining Anchor around any one technology.

Integrity Reference
↓
Integrity Method
↓
External Commitment
↓
external system + external identifier + proof material

Bitcoin-specific requirements remain deferred until Bitcoin commitment policy is formally adopted.

Schema Authority Boundary

The schema structures Anchor's Integrity Reference. It does not restructure or take ownership of the Source Artifact.

Reference does not transfer authority.

First Production Schema Position

The Base Schema is now aligned with the selected first Source Artifact:

SCRD-SC-CERT-2026-0001
Satoshium Certified Record
Version 1.1
Representation Type → canonical_json

The next unresolved production dependency is the exact canonicalization / serialization method and digest algorithm that will produce the Canonical Representation and first Integrity Value.

Source JSON
↓
canonicalization / serialization rule
↓
Canonical Representation
↓
cryptographic_digest
↓
Integrity Value

Schema Architecture Principle

The Base Schema should be stable enough to support real production design while flexible enough to absorb what the first Integrity Reference teaches us.

Structure first. Test with reality. Tighten only where evidence demands it.

Identifiers → Controlled Values → Relationships → Provenance → Back to Anchor →