Registry · Operational Records

Satoshium Registry Records

Registry Records are Satoshium Registry Entries, or SREGs, that identify, classify, reference, relate, version, and preserve Authoritative Source Records.

Registry maintains the SREG. The Source Institution retains authority over the Source Record.

Constitutional Position

Suite Standards → Suite Methodology → Suite Interoperability → Registry Institutional Implementation → SREG
Registry Records implement Suite-wide expectations through Registry-owned identifiers, classifications, references, relationships, statuses, versions, corrections, lifecycle controls, and publication.

What Is a Registry Record?

A Registry Record is an operational SREG maintained by Satoshium Registry.

It is not the Authoritative Source Record itself. It is Registry's structured, public, version-aware representation of how that source record can be identified, classified, found, related, and understood.

Registry Record = Satoshium Registry Entry (SREG)

Canonical Operational Hierarchy

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

The SREG is Registry's canonical operational object. The Record Type classifies the SREG. The Authoritative Source Record remains owned by the originating institution.

Tool Records

Tool SREGs catalog systems, services, frameworks, platforms, institutions, and operational components.

Jurisdiction Records

Jurisdiction SREGs catalog authoritative jurisdiction resources for countries, states, provinces, territories, regions, municipalities, and other approved classes.

Media Records

Media SREGs catalog videos, images, audio resources, transcripts, thumbnails, media pages, and other approved media artifacts.

Certification Records

Certification SREGs catalog Certifier-owned Certification Packages, SCRDs, reports, receipts, and related certification artifacts.

Attestation Records

Attestation SREGs catalog Attestor-owned trust statements, attestations, validations, and supporting verification references.

Signal Records

Signal SREGs catalog Beacon-owned discovery signals, announcements, visibility metadata, and other approved discovery-oriented records.

What Registry Records Answer

  • What Source Record exists?
  • Which institution created it?
  • What Registry Identifier identifies the SREG?
  • What Source-System Identifier identifies the Source Record?
  • What Record Type applies?
  • Where can the source be found?
  • What is the Registry Status?
  • What is the Registry Lifecycle State?
  • What is the Source-Record Status?
  • Which versions apply?
  • What relationships exist?
  • What corrections or historical changes occurred?

Registry Identifier

Identifies the SREG and remains distinct from the Source-System Identifier.

Source Attribution

Identifies the Source Institution and Authoritative Source Record.

Record Type

Assigns one approved primary classification to the SREG.

Status

Preserves Registry Status separately from Source-Record Status.

Lifecycle

Preserves the institutional condition and history of the SREG.

Versions

Preserves Registry Entry, schema, profile, specification, and source versions.

References

Preserves canonical source locations, repository paths, public pages, and machine-readable records.

Relationships

Preserves typed links among SREGs, Source Records, institutions, certifications, events, attestations, integrity references, signals, and workflows.

Source Authority and Registry Authority

Registry is authoritative for:

  • Registry Identifier;
  • Registry Record Type;
  • Registry Status;
  • Registry Lifecycle State;
  • Registry Entry Version;
  • Registry relationships;
  • Registry correction history;
  • Registry publication.

The Source Institution remains authoritative for:

  • Source Record content;
  • Source-System Identifier;
  • Source-Record version;
  • Source-Record Status;
  • institutional meaning;
  • certification or attestation outcomes;
  • ownership and rights.

Registry Record Method

Identify or Receive Source Record → Confirm Source Authority → Determine Registrability → Assign Record Type → Assign Registry Identifier → Establish References and Relationships → Construct SREG → Validate → Publish → Maintain

This method preserves a repeatable path from an authoritative source object to an operational Registry Record.

Schema Architecture

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

Every operational Registry Record should conform to the SREG Base Schema and the applicable Record-Type Profile.

Human-Readable and Machine-Readable Forms

A Registry Record may be published through:

  • human-readable Registry Entry page;
  • machine-readable SREG JSON;
  • catalog index;
  • relationship index;
  • version history;
  • correction history;
  • supersession, revocation, or archival record.
Official forms of the same SREG must agree on identity, classification, source, status, lifecycle, versions, references, and relationships.

Registry Record Lifecycle

Registry Records do not follow one mandatory linear sequence, but may move through approved lifecycle states such as:

Pending Registration · Registered · Active · Updated · Superseded · Revoked · Archived

Lifecycle describes the condition of the SREG. It does not replace the lifecycle or status of the Source Record.

Updates and Corrections

Registry Records may change because:

  • Registry-owned metadata improves;
  • public references change;
  • relationships evolve;
  • the Source Record publishes a new version;
  • the Source-Record Status changes;
  • a Registry-owned error is corrected;
  • schema migration occurs;
  • the Record-Type Profile changes.

Updates, corrections, supersession, and revocation must remain distinct and preserve prior versions where material.

Validation Requirements

Before publication, Registry should confirm:

  • the Source Institution is identified;
  • the Authoritative Source Record exists or is historically documented;
  • the Registry Identifier is valid;
  • the Source-System Identifier is preserved when available;
  • the Record Type is approved;
  • required metadata is complete;
  • required references and relationships exist;
  • Registry and source status values remain separate;
  • version metadata is complete;
  • the applicable schema validates;
  • official publication forms agree.

Registry Records Do Not

  • replace Source Records;
  • create certification authority;
  • create attestation conclusions;
  • establish ownership or legal rights;
  • rewrite Source-System Identifiers;
  • merge institutional responsibilities;
  • guarantee continued availability of external resources;
  • create truth merely through registration.

Records Principle

Registry Records create durable institutional structure around authoritative source objects without absorbing their authority.

The Source Record carries institutional meaning. The SREG preserves identity, classification, relationships, versions, and the path back to the source.
Back to Registry → Open Entry Model → Open Record Types →
Source records hold authority. Registry Records preserve the structured path back to them.