Registry · Controlled Classifications

Satoshium Registry Record Types

Registry Record Types define the controlled primary classifications assigned to Satoshium Registry Entries, or SREGs.

Record Types organize Registry without replacing the Authoritative Source Record or transferring authority away from the Source Institution.

Constitutional Position

Registry Record Types operate beneath the Satoshium Suite constitutional hierarchy.

Suite Standards → Registry Rules → Record Type Governance → Record-Type Profile → Published SREG
Record Types classify SREGs. They do not define the authority or substantive meaning of the Source Record.

Canonical Operational Hierarchy

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

Each SREG receives one primary Registry Record Type. The Record Type governs classification, applicable profile requirements, discoverability, and relationship behavior.

Tool

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

Examples may include Atlas, Certifier, Registry, Chronicle, Anchor, Beacon, Attestor, Navigator, or approved external tools.

Jurisdiction

Jurisdiction Records catalog authoritative jurisdiction resources for countries, states, provinces, territories, regions, municipalities, and other approved geographic or governmental classifications.

Media

Media Records catalog videos, images, audio resources, transcripts, thumbnails, media pages, and other public-facing media artifacts.

Certification

Certification Records catalog Certifier-owned certification artifacts such as Certification Packages, SCRDs, receipts, reports, and related certification records.

Registry does not create the Certification Outcome.

Attestation

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

Signal

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

Additional and Future Record Types

Registry may introduce additional Record Types when a genuine operational need exists.

Potential future Record Types may include:

  • Historical Event;
  • Integrity Reference;
  • Workflow Definition;
  • Schema;
  • Policy;
  • Governance;
  • Preservation;
  • Reference;
  • Evidence;
  • Research;
  • External Institutional Record.
A future Record Type must be approved through Registry governance before use in an operational SREG.

One Primary Record Type

Every operational SREG must receive one primary Registry Record Type.

Secondary classifications may be permitted by the applicable Record-Type Profile, but they must not conflict with the primary type.

Record Type defines the primary Registry classification. Relationships connect the SREG to other objects.

Record-Type Profiles

Each approved Record Type should have a corresponding Record-Type Profile.

A Record-Type Profile may define:

  • required fields;
  • optional fields;
  • controlled classifications;
  • required relationships;
  • permitted relationships;
  • identifier expectations;
  • status values;
  • lifecycle requirements;
  • public reference requirements;
  • validation rules.
The SREG Base Schema defines the shared structure. The Record-Type Profile adds type-specific requirements.

Schema Relationship

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

Record Types should not create unrelated Registry record models. They extend the shared SREG architecture through controlled profiles.

Classification Authority

Registry is authoritative for assigning the Registry Record Type to the SREG.

The Source Institution remains authoritative for the Source Record's own classification, meaning, status, and content.

Registry classification describes how Registry catalogs the record. It does not redefine what the Source Record is.

Record Type and Source Institution

Record Type and Source Institution are separate fields.

The same Source Institution may produce records cataloged under multiple Record Types.

Atlas may be cataloged as a Tool. An Atlas jurisdiction resource may be cataloged as a Jurisdiction. An Atlas media artifact may be cataloged as Media.

Record Type and Relationships

Record Type determines the primary classification of the SREG. Relationships describe how the SREG connects to other objects.

Examples include:

  • Tool SREG → produces → Jurisdiction SREG;
  • Jurisdiction SREG → related to → Media SREG;
  • Certification SREG → references → Jurisdiction SREG;
  • Attestation SREG → attests to → Certification SREG;
  • Signal SREG → discovers → Media SREG;
  • SREG → anchored by → Integrity Reference.

Relationships must use approved relationship types and preserve direction where applicable.

Record Type Changes

A Record Type change may be material because it can affect:

  • schema validation;
  • required fields;
  • relationships;
  • discovery;
  • public interpretation;
  • lifecycle behavior;
  • interoperability.

A material Record Type change should follow the applicable Update or Correction Policy and may require supersession when Registry identity changes fundamentally.

Record Type Approval

A new Record Type should be approved only when:

  • existing types cannot accurately classify the source object;
  • a distinct institutional object exists;
  • the type has clear scope and boundaries;
  • a Record-Type Profile can be defined;
  • schema validation can be supported;
  • relationship behavior can be documented;
  • interoperability consequences are understood;
  • governance approval is recorded.
Record Type expansion should reflect architectural need, not convenience.

Record Type Validation

Before publication, Registry should confirm:

  • the primary Record Type is approved;
  • the selected type accurately fits the Source Record;
  • the applicable profile version is identified;
  • required fields are present;
  • required relationships are present;
  • controlled values are valid;
  • the SREG satisfies the applicable schema;
  • human-readable and machine-readable forms agree.

Why Record Types Matter

Record Types give Registry a controlled way to organize different kinds of institutional objects without collapsing them into one undifferentiated catalog.

They improve:

  • discoverability;
  • schema consistency;
  • relationship clarity;
  • validation;
  • interoperability;
  • long-term maintenance.
Information may take many forms. Registry Record Types preserve those distinctions within one shared SREG model.
Back to Registry → Open Entry Model → Open Schemas →
Record Types organize the catalog. Source Institutions preserve authority.