Core Principle
Stable objects
+ clear authority boundaries
+ durable references
+ repeatable workflows
= interoperable institutions
+ clear authority boundaries
+ durable references
+ repeatable workflows
= interoperable institutions
Suite · Interoperability
Satoshium Suite Interoperability
Suite Interoperability defines how Atlas, Certifier, Registry, Chronicle, Anchor, Beacon, Attestor, and Navigator cooperate through stable references without collapsing their institutional responsibilities into one system.
Each institution preserves its own canonical object, identifier, lifecycle, governance, and authority. Reference does not transfer authority.
Atlas
Authoritative intelligence and subject records.
Canonical role → authoritative intelligence
Certifier
Evidence-based certification and canonical Certification Packages.
Canonical object → Certification Package
Registry
Registration and cataloging through independent Satoshium Registry Entries.
Canonical object → SREG
Chronicle
Historical preservation through canonical Chronicle Entries representing qualifying Occurrences.
Canonical object → Chronicle Entry
Anchor
Integrity preservation through durable Integrity References for governed representations of authoritative artifacts.
Canonical object → Integrity Reference
Beacon
Discovery and discoverability for Suite records and signals.
Canonical object → Discovery Signal / Metadata
Attestor
Trust statements based on supported authoritative references.
Canonical object → Trust Statement
Navigator
Workflow orchestration across Suite records and institutional processes.
Canonical object → Workflow Definition
Production-Proven Interoperability
The inaugural Certifier production record has now produced independent downstream objects in Registry, Chronicle, and Anchor.
| Institution | Production Object | Institutional Role |
|---|---|---|
| Certifier | SC-CERT-2026-0001 | Certification Package / certification authority |
| Registry | SREG-2026-0001 | Registry-owned catalog record |
| Chronicle | CHR-2026-0001 | Chronicle-owned historical-preservation entry |
| Anchor | ANCH-2026-0001 | Anchor-owned Integrity Reference |
Important Structural Distinction
SC-CERT-2026-0001
SREG-2026-0001
CHR-2026-0001
ANCH-2026-0001
SREG-2026-0001
CHR-2026-0001
ANCH-2026-0001
These identifiers do not describe one object moving through four systems. They identify four institution-owned objects connected by governed relationships and provenance.
Anchor Relationship
Anchor does not automatically preserve every Certification Package or every Suite object. A specific authoritative artifact and governed representation boundary are selected first.
SCRD-SC-CERT-2026-0001
↓ defined canonical representation
RFC 8785 JCS / UTF-8
↓ SHA-256
ANCH-2026-0001
↓ defined canonical representation
RFC 8785 JCS / UTF-8
↓ SHA-256
ANCH-2026-0001
Canonical Suite Flow
Atlas provides authoritative intelligence.
Certifier certifies a defined subject.
Registry catalogs authoritative records.
Chronicle preserves qualifying historical Occurrences.
Anchor preserves governed Integrity References.
Beacon publishes Discovery Signals.
Attestor produces Trust Statements.
Navigator orchestrates workflows.
Certifier certifies a defined subject.
Registry catalogs authoritative records.
Chronicle preserves qualifying historical Occurrences.
Anchor preserves governed Integrity References.
Beacon publishes Discovery Signals.
Attestor produces Trust Statements.
Navigator orchestrates workflows.
What Interoperability Does Not Do
Interoperability does not create a shared authority, duplicate institutional objects, make every downstream system mandatory, or require old records to be rewritten whenever a new related object is later created.
Interoperability connects responsibilities. It does not erase boundaries.
Back to Suite →