Registry · Canonical Public Record Institution

Satoshium Registry

Satoshium Registry is the Suite institution responsible for canonical registration, durable SREG identity, Registry classification, provenance, validation, publication, versioning, corrections, lifecycle, public discovery, institutional history, and transparency.

Registry catalogs authoritative records without taking authority away from the institutions that created them. Its canonical operational object is the Satoshium Registry Entry, or SREG.

Institutional Position

Registry operates beneath Suite Standards, Suite Methodology, and Suite Interoperability. Those Suite-wide foundations define shared expectations, implementation principles, and institutional boundaries. Registry applies them through its own Scope, Definitions, Rules, Policies, Procedures, Governance, schemas, Controlled Values, records, and public operations.

Suite Standards Suite Methodology Suite Interoperability Registry Implementation SREG
Source Institutions retain authority over their Source Records. Registry retains authority over the SREG, its Registry Identifier, Registry classification, Registry-owned metadata, relationships, versions, status, lifecycle, publication, Catalog presentation, Corrections, and History.

Institutional Foundation

These pages define why Registry exists, what it governs, the vocabulary it uses, and the constitutional requirements beneath every Registry action.

Foundation

Purpose

Defines why Registry exists, the public-record problem it addresses, and its institutional mission.

Open Purpose →
Foundation

Scope

Defines what Registry may govern, register, publish, preserve, and what remains outside Registry authority.

Open Scope →
Foundation

Definitions

Establishes the canonical vocabulary and distinctions used across every Registry framework and record.

Open Definitions →
Public Guidance

FAQ

Answers common questions about SREG identity, source authority, registrability, schemas, Validation, Publication, Lifecycle, interoperability, and Registry operations.

Open FAQ →
Foundation

Rules

Defines binding Registry requirements for identity, authority, classification, continuity, and preservation.

Open Rules →
Foundation

Policies

Defines governed institutional principles, decision criteria, and operating conditions beneath Registry Rules.

Open Policies →
Foundation

Procedures

Defines the repeatable operational sequences through which Registry performs its authorized work.

Open Procedures →
Foundation

Governance

Defines authority, roles, approvals, decision rights, exceptions, conflicts, and institutional accountability.

Open Governance →
Foundation

Controlled Values

Defines the governed codes, labels, statuses, outcomes, relationship types, and other approved values.

Open Controlled Values →

Canonical Records and Structure

These pages define the SREG, its classifications, schemas, authority references, identifiers, relationships, and provenance.

Records

Records

Explains SREGs, supporting Registry Records, Source Records, and the larger Registry record architecture.

Open Records →
Records

Entry Model

Defines the SREG as Registry’s canonical operational object and its relationship to authoritative sources.

Open Entry Model →
Records

Record Types

Defines the governed classifications assigned to SREGs and the boundaries of each Registry record class.

Open Record Types →
Records

Schemas

Defines the SREG Base Schema, Registry Schema Specification, and Record-Type Profile architecture.

Open Schemas →
Authority

Source Authority

Defines how Registry identifies and preserves the authority responsible for each Source Record.

Open Source Authority →
Admission

Registrability

Defines how Registry determines whether a specific object qualifies for registration as a SREG.

Open Registrability →
Identity

Identifiers

Defines permanent Registry Identifiers, Source-System Identifiers, namespaces, states, and resolution.

Open Identifiers →
Context

Relationships

Defines typed, directed, governed connections among SREGs, sources, institutions, versions, and artifacts.

Open Relationships →
Context

Provenance

Defines origin, Source Institution, custody, derivation, generation, integrity, and preservation lineage.

Open Provenance →

Operational Control

These pages govern how SREGs are validated, published, versioned, corrected, and maintained through Registry Status and Lifecycle.

Control

Validation

Defines how Registry evaluates SREG conformance to Rules, Policies, schemas, profiles, and Controlled Values.

Open Validation →
Control

Publication

Defines official human-readable and machine-readable release, readiness, notices, restrictions, and resolution.

Open Publication →
Control

Versioning

Defines Registry Entry Versions and their separation from Source-Record, schema, profile, and Catalog versions.

Open Versioning →
Control

Corrections

Defines transparent correction of Registry-owned records while preserving prior states and source authority.

Open Corrections →
Control

Status

Defines the current Registry condition of a SREG and its distinction from source and institutional statuses.

Open Status →
Control

Lifecycle

Defines the stages and permitted transitions through which a SREG moves during its institutional life.

Open Lifecycle →

Public Discovery and Institutional Memory

These pages make Registry records discoverable, historically accountable, transparent, and interoperable across the Suite.

Public Directory

Registered Items

Provides the public directory of completed Satoshium Registry Entries and resolves each listed item to its canonical SREG package.

Open Registered Items →
Public Layer

Catalog

Defines how published SREGs are browsed, searched, filtered, resolved, related, and historically presented.

Open Catalog →
Institutional Memory

History

Defines the chronological, versioned, attributable, and resolvable history of Registry objects and decisions.

Open History →
Accountability

Transparency

Defines how Registry makes authority, conditions, limitations, Corrections, versions, and history visible.

Open Transparency →
Suite Connection

Integration

Defines how Registry exchanges and references records across Suite institutions without merging authority.

Open Integration →

Canonical Operational Hierarchy

Registry development centers on a four-layer model that preserves institutional separation while creating a durable public catalog.

Satoshium Registry Registry Entry (SREG) Registry Record Type Authoritative Source Record
Registry owns the SREG and Registry-controlled representation. The Source Institution retains authority over the Authoritative Source Record.

Registry Method

Registry applies Suite Methodology through a repeatable institutional process designed for review, machine readability, interoperability, preservation, and maintenance.

Identify or receive source → confirm Source Authority → determine Scope and Registrability → assign Record Type and Registry Identifier → preserve Source-System Identifier → establish provenance and relationships → construct and validate SREG → publish → maintain versions, Status, Lifecycle, Corrections, Catalog presence, History, and Transparency.

Suite Relationship

Registry strengthens Satoshium Suite by connecting authoritative institutional objects without replacing the institutions that created them.

  • Atlas creates jurisdiction intelligence and canonical jurisdiction resources.
  • Certifier creates certifications and canonical certification artifacts.
  • Registry creates SREGs and maintains the canonical public Catalog.
  • Chronicle preserves Chronicle-created historical events and institutional chronology.
  • Anchor creates integrity references and durable verification records.
  • Beacon creates signals and discovery metadata.
  • Attestor creates attestations and trust statements.
  • Navigator coordinates workflows and cross-system operational activity.

Registry preserves discovery by preserving the path back to authority.