Registry · Canonical Operational Object

Satoshium Registry Entry Model

The Registry Entry Model defines the Satoshium Registry Entry, or SREG, as the canonical operational object of Satoshium Registry.

A SREG identifies, classifies, references, connects, versions, and preserves the discoverability of an authoritative source record without transferring authority away from the institution that created it.

Constitutional Position

The SREG implements the Satoshium Suite constitutional hierarchy at the Registry institutional layer.

Suite Standards → Suite Methodology → Suite Interoperability → Registry Implementation → SREG

Suite Standards define shared expectations. Suite Methodology defines repeatable implementation principles. Suite Interoperability preserves institutional boundaries. Registry applies those foundations through the SREG.

What Is an SREG?

A SREG is an independently maintained Registry record that identifies, classifies, references, and connects an Authoritative Source Record.

Why Registry Creates SREGs

Registry creates SREGs so records produced by Suite institutions can remain publicly discoverable, version-aware, related, and traceable without losing source ownership or institutional authority.

Canonical Object

The SREG is Registry's canonical operational object. Other institutions retain their own canonical objects, such as the Certification Package, Historical Event, Integrity Reference, Discovery Signal, Trust Statement, and Workflow Definition.

Registry Authority

Registry is authoritative for the SREG, its identifier, classification, Registry status, Registry lifecycle, relationships, versions, corrections, and public catalog presentation.

Canonical Operational Hierarchy

The Registry Entry Model is organized through four distinct layers.

Satoshium Registry → Registry Entry (SREG) → Registry Record Type → Authoritative Source Record

Satoshium Registry

The institution responsible for the public catalog and Registry operations.

Registry Entry (SREG)

The canonical Registry object that maintains Registry-owned information about the record being cataloged.

Registry Record Type

The controlled primary classification assigned to the SREG.

Authoritative Source Record

The record created and maintained by the originating institution.

Source Authority

A SREG does not inherit the authority of the Source Record.

The Source Institution remains authoritative for:

source-record content;
source-record identifier;
source-record version;
source-record status;
certification outcomes;
attestation conclusions;
historical event content;
integrity references;
discovery signals;
jurisdiction intelligence;
workflow definitions.

Registry may report or reference source-controlled values. Registry does not redefine them.

Certification Relationship

The first operational Certifier-to-Registry relationship follows this path:

Atlas Resource → Certifier Evaluation → Certification Package → SCRD → SREG

The Certification Package remains Certifier's canonical certification object. The SCRD remains a Certifier-owned certified record. Registry creates an independent SREG that catalogs and references those records.

This is one interoperability path, not the limit of Registry scope. Registry may also catalog Atlas resources, Chronicle events, Anchor records, Beacon signals, Attestor trust statements, Navigator workflows, tools, media, and other approved Source Records.

Registry References Rather Than Replaces

A SREG may reference a Source Record, Certification Package, SCRD, repository, public page, integrity reference, attestation, historical event, discovery signal, workflow definition, or related SREG.

Registry preserves the structured path back to authority. It does not duplicate every source, absorb source ownership, or create a substitute source record.

This approach preserves provenance, limits record drift, strengthens interoperability, and allows each Suite institution to retain its own responsibility.

Registry Identifier

Every SREG receives a stable and unique Registry Identifier that identifies the SREG itself.

Registry Record Type

Every SREG receives a controlled Record Type that governs classification, validation, profile application, discoverability, and relationship behavior.

Source Institution

Every SREG identifies the institution that created and maintains the Authoritative Source Record.

Source-System Identifier

Every SREG preserves the source identifier when one exists. The source identifier remains distinct from the Registry Identifier.

Source Record

Every SREG identifies and references the Authoritative Source Record being cataloged.

Registry and Source Status

Every SREG distinguishes Registry Status from Source-Record Status and other institution-controlled status values.

Versions

Every SREG preserves applicable Registry Entry, schema, Record-Type Profile, and Source-Record version information.

Relationships

Every SREG may preserve typed relationships to other SREGs, Source Records, institutions, schemas, events, integrity references, attestations, and workflows.

Public References

Every SREG should preserve approved public locations, canonical URLs, repository paths, machine-readable records, or other durable references.

Lifecycle History

Every SREG should preserve registration, update, correction, supersession, revocation, and archival history as applicable.

Conceptual SREG Fields

The machine-readable Registry Schema Specification defines the authoritative field names, data types, required values, and validation rules. The Entry Model establishes the conceptual information that a complete SREG must support.

Registry Identifier · Registry Record Type · Title · Source Institution · Source-System Identifier · Authoritative Source Record · Source-Record Version · Source-Record Status · Registry Status · Registry Lifecycle State · SREG Version · Schema Version · Public References · Relationships · Registration Date · Last Updated · Correction History · Supersession · Revocation · Archival

Schema Architecture

SREGs are implemented through a shared schema hierarchy.

Suite Schema Standard → Registry Schema Specification → SREG Base Schema → Record-Type Profile → Published SREG

The SREG Base Schema defines the common structure. Record-Type Profiles add type-specific requirements without creating unrelated Registry record models.

Registry Status and Source Status

The condition of the SREG and the condition of the Source Record must remain separate.

Certification Outcome: Certified · Certification Status: Revoked · Registry Status: Active

In this example, the certification is revoked, but the SREG remains active as a public historical catalog entry that accurately reports the source condition.

Version and Correction Model

A SREG may change because Registry-owned information changes, because the Source Record changes, or because the applicable schema evolves.

Those changes must remain distinguishable.

Prior SREG Version → Documented Change → Replacement SREG Version

Material corrections should preserve what changed, why it changed, when it changed, which version was affected, and which version replaced it.

Human-Readable and Machine-Readable Forms

Registry should publish equivalent human-readable and machine-readable representations of the same SREG.

Human-readable Registry Entry page.
Machine-readable SREG JSON record.
Catalog and relationship indexes.
Version and correction history.

Official representations of the same SREG must agree on identity, classification, status, version, source, and relationships.

Long-Term Discoverability

SREGs allow records to remain identifiable and understandable after public pages move, schemas evolve, Source Records change, institutions mature, or new Suite systems are introduced.

Registry preserves the identity, provenance, source references, relationships, versions, and historical context necessary to find and interpret the record later.

Entry Model Principle

The SREG is not a copy of institutional authority. It is Registry's durable, structured representation of how that authority may be found and understood.

The source retains authority. The SREG preserves identity, classification, relationships, versions, and discovery.

Back to Registry → Open Record Types → Open Schemas →