Registry · Catalog
Satoshium Registry Catalog
The Satoshium Registry Catalog is the public discovery and resolution layer
through which published Satoshium Registry Entries are organized, browsed,
filtered, related, versioned, and accessed.
The Catalog presents Registry-owned SREGs while preserving direct attribution
to the Authoritative Source Records and Source Institutions they reference.
Constitutional Position
The Catalog sits above published SREGs and provides the public interface through
which Registry identity, classification, status, relationships, provenance,
versions, corrections, and history become discoverable.
Authoritative Source Record
→
SREG
→
Validation
→
Publication
→
Registry Catalog
Registry owns the Catalog presentation.
Source Institutions retain authority over their Source Records.
Why the Catalog Matters
Publication makes an individual SREG available. The Catalog makes the wider
body of published Registry records discoverable as one coherent institutional system.
The Core Question
The Catalog asks:
How should a user or system find, understand, compare, and resolve published SREGs?
Registry's Responsibility
Registry must provide stable identity resolution, accurate catalog metadata,
governed filtering, version awareness, relationship navigation, and historical continuity.
Registry's Limitation
Catalog inclusion does not certify, endorse, own, or replace the underlying Source Record.
Canonical Catalog Model
Published SREGs
→
Catalog Metadata
→
Browse, Search, Filter, Resolve
→
Canonical SREG Page
Catalog Functions
- browse published SREGs;
- search by identifier, title, source, institution, or keyword;
- filter by Record Type;
- filter by Registry Status;
- filter by Registry Lifecycle State;
- filter by Source Institution;
- filter by publication date or update date;
- resolve Registry Identifiers;
- navigate typed relationships;
- view current and historical versions;
- view corrections, notices, restrictions, and supersession;
- access machine-readable records and downloadable artifacts;
- support Suite and external-system discovery.
Browse
Presents ordered collections of published SREGs by institutional category.
Search
Finds SREGs through identifiers, titles, source references, and indexed metadata.
Filter
Narrows results through governed fields and Controlled Values.
Resolve
Connects a Registry Identifier to its canonical current and historical Registry context.
Catalog Entry
Each Catalog result should represent one published SREG and may display:
- Registry Identifier;
- title;
- short description;
- Registry Record Type;
- Source Institution;
- Source-System Identifier;
- Registry Status;
- Registry Lifecycle State;
- Registry Entry Version;
- publication date;
- last update date;
- restriction or notice indicators;
- canonical SREG link;
- machine-readable record link.
Illustrative Catalog Entry
registry_identifier: "SREG-JUR-2026-0001"
title: "El Salvador"
record_type: "jurisdiction"
source_institution: "Satoshium Atlas"
source_system_identifier: "atlas-jurisdiction-el-salvador"
registry_status: "active"
registry_lifecycle_state: "published"
registry_entry_version: "1.0.0"
Primary Catalog Views
- All Records — complete current public catalog.
- By Record Type — grouped by approved Registry Record Type.
- By Source Institution — grouped by Source Institution.
- By Status — grouped by current Registry Status.
- By Lifecycle — grouped by Registry Lifecycle State.
- Recently Published — ordered by first-publication date.
- Recently Updated — ordered by latest material update.
- Corrections and Notices — records with material public notices.
- Historical Records — superseded, revoked, retired, or archived SREGs.
Record-Type Collections
Catalog collections may include:
- Tools;
- Jurisdictions;
- Media;
- Certifications;
- Attestations;
- Signals;
- Events;
- Integrity References;
- Workflows;
- Institutions;
- Schemas;
- Policies;
- Procedures;
- Governance Decisions.
Catalog collections reflect Registry classifications.
They do not redefine the Source Records placed within them.
Searchable Fields
Catalog search may index:
- Registry Identifier;
- Source-System Identifier;
- title;
- alternate titles;
- description;
- Record Type;
- Source Institution;
- canonical source URL;
- jurisdiction;
- keywords;
- relationships;
- Registry Status;
- Registry Lifecycle State;
- version;
- publication date;
- correction and notice metadata.
Search Behavior
Search should:
- prioritize exact Registry Identifier matches;
- preserve Source-System Identifier matches;
- distinguish current from historical SREGs;
- surface active records before historical records when relevance is comparable;
- expose disputed, restricted, superseded, revoked, and archived conditions;
- avoid presenting aliases as canonical identity;
- preserve source attribution in results;
- support machine-readable query and response patterns when implemented.
Catalog Filters
Filters should use governed Controlled Values where applicable.
- Registry Record Type;
- Registry Status;
- Registry Lifecycle State;
- Source Institution;
- Access Condition;
- Validation Outcome;
- Publication Readiness Outcome;
- publication date range;
- last update date range;
- version condition;
- notice type;
- historical condition.
Canonical Resolution
Every published Registry Identifier should resolve to its canonical current SREG context.
https://satoshium.us/registry/catalog/SREG-JUR-2026-0001/
The canonical page should expose:
- current Registry Entry Version;
- current Registry Status;
- current Registry Lifecycle State;
- Source Institution;
- Authoritative Source Record;
- machine-readable form;
- relationships;
- provenance;
- corrections;
- historical versions;
- supersession or archival notices.
Machine-Readable Catalog
Registry may publish a machine-readable catalog index containing:
- Catalog Version;
- generation date;
- included Registry Identifiers;
- current Registry Entry Versions;
- Record Types;
- Source Institutions;
- statuses;
- lifecycle states;
- canonical URLs;
- machine-readable URLs;
- publication dates;
- update dates;
- notices and restrictions;
- integrity or generation references.
https://satoshium.us/registry/catalog/index.json
Catalog Versioning
The Catalog itself may be versioned independently from individual SREGs.
Catalog version records should preserve:
- Catalog Version;
- generation date;
- included records;
- added SREGs;
- updated SREGs;
- removed-from-current-view SREGs;
- schema or index-format version;
- generation method;
- integrity reference;
- prior Catalog Version.
Catalog Version describes the indexed collection.
Registry Entry Version describes an individual SREG.
Current and Historical Catalog Views
The current Catalog should prioritize current operational SREGs.
Historical views should preserve:
- superseded SREGs;
- revoked SREGs;
- retired SREGs;
- archived SREGs;
- prior Registry Entry Versions;
- prior Catalog Versions;
- correction history;
- former classifications;
- former status and lifecycle values;
- former canonical paths where applicable.
Relationship Navigation
Catalog pages may provide navigable relationships such as:
- Source Record and Source Institution;
- certification and certified subject;
- attestation and attested subject;
- jurisdiction and related certifications;
- event and documented records;
- signal and announced record;
- integrity reference and protected artifact;
- workflow and dependent records;
- predecessor and successor SREGs;
- current and historical versions;
- derived and archival artifacts.
Notices and Conditions
Catalog results and SREG pages should visibly identify material conditions such as:
- provisional publication;
- restricted access;
- source unavailable;
- validation warning;
- correction issued;
- disputed relationship;
- superseded entry;
- revoked entry;
- retired entry;
- archived entry;
- external-source disclaimer;
- rights or reuse limitation;
- governance exception;
- migration notice.
Restricted Catalog Entries
Restricted SREGs may appear with limited public metadata when appropriate.
A restricted Catalog entry may expose:
- Registry Identifier;
- title or generalized title;
- Record Type;
- Source Institution;
- Registry Status;
- Registry Lifecycle State;
- restriction notice;
- public provenance summary;
- review date or access condition.
Restricted content must not be exposed through search indexes, machine-readable
Catalog files, cached excerpts, or downloadable artifacts.
Catalog Ordering
Catalog views may support ordering by:
- Registry Identifier;
- title;
- Record Type;
- Source Institution;
- first-publication date;
- last-update date;
- Registry Status;
- Registry Lifecycle State;
- relevance;
- historical sequence.
Ordering should support discovery without implying institutional rank,
endorsement, quality, or substantive importance unless explicitly governed.
Catalog Metadata
Catalog-specific metadata may include:
- Catalog inclusion date;
- Catalog display title;
- Catalog summary;
- search keywords;
- browse collections;
- filter facets;
- sort values;
- thumbnail or visual reference;
- featured or highlighted condition;
- indexing status;
- last indexed date;
- Catalog Version.
Catalog metadata supports discovery.
It must not silently change canonical SREG meaning.
Catalog Inclusion
A SREG should enter the public Catalog only when:
- required Validation permits publication;
- official Publication is complete;
- canonical resolution is functioning;
- Catalog metadata is complete;
- Controlled Values are valid;
- notices and restrictions are correctly represented;
- machine-readable and human-readable forms agree;
- search and filter fields are safe for indexing.
Catalog Removal from Current Views
A SREG may be removed from current browse views when it becomes:
- superseded;
- revoked;
- retired;
- archived;
- withdrawn from public access;
- restricted from indexing;
- invalidly published.
Removal from current views should not erase canonical resolution or historical
Catalog presence unless access itself must be restricted.
Catalog Validation
Validation should confirm:
- Catalog entry points to the correct Registry Identifier;
- title and Record Type match the SREG;
- Source Institution is accurate;
- Registry Status and Lifecycle State are current;
- Registry Entry Version is current;
- canonical and machine-readable URLs resolve;
- filters use approved Controlled Values;
- notices and restrictions are visible;
- historical SREGs are not presented as current;
- restricted fields are not indexed;
- Catalog metadata does not contradict canonical SREG content;
- current and historical views remain distinguishable.
Invalid Catalog Conditions
- Catalog entry resolves to the wrong SREG;
- duplicate canonical Catalog entry;
- missing Registry Identifier;
- incorrect Record Type;
- incorrect Source Institution;
- stale Registry Status or Lifecycle State;
- historical version presented as current;
- broken canonical or machine-readable URL;
- restricted information exposed;
- unapproved filter value;
- Catalog summary contradicts the SREG;
- superseded or revoked SREG presented without notice;
- Catalog metadata silently alters canonical meaning.
Relationship to Publication
Publication creates the official SREG.
The Catalog indexes and presents that published SREG for discovery and resolution.
Publication establishes availability.
The Catalog establishes discoverability.
Relationship to Identifiers
The Catalog uses Registry Identifiers as the canonical resolution keys for SREGs.
Search aliases and Source-System Identifiers may help discovery but must not replace
the canonical Registry Identifier.
Relationship to Relationships
The Catalog makes typed Registry Relationships navigable across SREG pages and collections.
Relationship navigation should preserve:
- direction;
- identifier domains;
- Relationship Authority;
- Relationship Status;
- version context;
- temporal context;
- correction history.
Relationship to Controlled Values
Catalog filters, facets, labels, notices, and collection names should use approved
Controlled Values whenever the underlying field is governed.
Relationship to Beacon
Beacon may announce newly published, updated, corrected, superseded, or archived SREGs.
Beacon signals may link into the Catalog.
Registry remains authoritative for Catalog entries and SREGs.
Relationship to Chronicle
Chronicle may record historically significant Catalog releases, major Registry
publication milestones, or material institutional transitions.
Registry remains authoritative for Catalog Versions and inclusion history.
Chronicle remains authoritative for Chronicle-created event records.
Relationship to Governance
Registry Governance should control:
- Catalog inclusion requirements;
- Catalog metadata fields;
- browse collections;
- search behavior;
- filter facets;
- ordering rules;
- featured conditions;
- restricted indexing;
- Catalog versioning;
- historical Catalog views;
- machine-readable Catalog publication;
- Catalog correction and withdrawal.
What the Catalog Does Not Establish
- It does not create Source Authority.
- It does not certify Source Records.
- It does not create attestations.
- It does not transfer ownership.
- It does not establish endorsement or affiliation.
- It does not make Catalog order a measure of importance.
- It does not replace the canonical SREG.
- It does not replace the Authoritative Source Record.
- It does not permit restricted information to be indexed.
- It does not erase historical Catalog presence.
Catalog Principle
The Registry Catalog should make published SREGs easy to discover and resolve
while preserving canonical identity, source attribution, version history,
governed classifications, material notices, and institutional boundaries.
Publication makes a record available.
The Catalog makes the Registry discoverable.
Resolution preserves identity.
Back to Registry →
Open Publication →
Open Controlled Values →
A Registry becomes useful when every durable identity can be found, understood, and followed through time.