Why Definitions Matter
Registry depends on precise distinctions between institutions, objects, identifiers, authority, status, lifecycle, versions, validation, publication, and historical records.
Satoshium Registry Definitions establishes the canonical institutional vocabulary used across Registry architecture, operations, schemas, publications, records, and public documentation.
Definitions preserve shared meaning. They distinguish similar terms, prevent authority drift, and ensure that human-readable and machine-readable Registry materials describe the same institutional concepts.
Registry Definitions operates beneath Suite Standards and Suite Methodology and supports every Registry framework, including Scope, Rules, Policies, Procedures, Schemas, Controlled Values, Validation, Publication, Governance, Catalog, History, and Transparency.
Registry depends on precise distinctions between institutions, objects, identifiers, authority, status, lifecycle, versions, validation, publication, and historical records.
Definitions asks:
Registry must define its canonical vocabulary, maintain those definitions, preserve prior meanings, and prevent silent semantic change.
Registry Definitions must not redefine Source Institution terminology or another Suite institution's authoritative concepts outside Registry scope.
A governed Registry definition should identify:
One current institutional definition governs Registry usage.
Similar terms remain separated when their authority or meaning differs.
Material definition changes preserve prior meanings and effective periods.
Definitions support schemas, Procedures, Validation, Publication, and records.
This layered model distinguishes the Registry institution, its canonical operational object, the Registry classification applied to that object, and the Source Record whose authority remains with its originating institution.
The coordinated institutional environment containing Satoshium Registry and the other Suite institutions, governed by Suite Standards, Suite Methodology, and Suite Interoperability.
The Suite institution responsible for canonical registration, SREG identity, Registry classification, Registry-owned metadata, Registry Relationships, Validation, Publication, Versioning, Corrections, Status, Lifecycle, Catalog presentation, History, Transparency, and related institutional Governance.
Satoshium Registry understood as an enduring institutional authority, distinct from any individual SREG, web page, schema, Catalog, or software implementation.
A defined institution within Satoshium Suite that holds authority over a distinct functional domain, such as Atlas, Certifier, Registry, Chronicle, Anchor, Beacon, Attestor, or Navigator.
The institution, organization, authority, system, or recognized origin responsible for the authoritative meaning of a Source Record.
A Source Institution or governing authority outside Satoshium Suite whose records, identifiers, rights, or decisions may be referenced by Registry without becoming Registry-owned.
The canonical Registry operational object used to identify, classify, describe, relate, version, publish, correct, preserve, and resolve a registrable Source Record or Registry-governed object.
The full-form name for a SREG. Within Registry architecture, “Registry Entry” and “SREG” refer to the same canonical operational object.
A general term for a record maintained by Registry. Depending on context, it may refer to a SREG or to a Registry-owned supporting record such as a Validation Record, Publication Record, Correction Record, History Record, Governance Decision Record, Scope Record, or Transparency Record.
A governed Registry classification assigned to a SREG, such as Tool, Jurisdiction, Media, Certification, Attestation, Signal, Event, Integrity Reference, Workflow, Institution, Schema, Policy, Procedure, or Governance Decision.
A governed schema specialization defining the additional fields, Controlled Values, relationships, Validation rules, and Publication requirements applicable to a particular Registry Record Type.
Any object governed or maintained directly by Registry, including SREGs, supporting Registry Records, schemas, profiles, Controlled-Value Sets, Catalog indexes, Policies, Procedures, and Governance materials.
A record, artifact, resource, decision, event, package, statement, signal, or other source-domain object created or controlled by a Source Institution and represented by Registry without transferring its authority.
The Source Record recognized as the authoritative source-domain object to which a SREG points. Its substantive meaning remains under Source Institution authority.
The preferred authoritative source location or representation identified by the Source Institution or supported by Registry provenance.
An artifact generated, transformed, summarized, converted, or otherwise derived from an original or canonical Source Record.
A machine-created or process-created artifact produced through an approved generation method, often accompanied by a generation manifest or integrity reference.
The Registry's recorded description or reference to a Source Record. A Source Representation is not the Source Record itself and does not transfer Source Authority.
The institutional authority responsible for the substantive meaning, status, outcome, rights, or source-domain lifecycle of a Source Record.
The authority held by Satoshium Registry over SREG identity, Registry-owned fields, classification, Validation, Publication, Versioning, Corrections, Status, Lifecycle, Catalog presentation, History, and Governance.
The institution, Governance decision, source evidence, or authorized process responsible for establishing or maintaining a Registry Relationship.
The role, institution, governing body, or authorized process empowered to approve a Registry decision.
Authority exercised by a role, process, or institution under a documented delegation from the authority that retains ultimate accountability.
The defined limit separating Registry authority from Source Institution, other Suite institution, external legal, regulatory, governmental, or rights-holder authority.
The institutional, operational, technical, object, field, action, geographic, temporal, and authority boundaries within which Registry may act.
A formal or operational decision establishing whether an object, responsibility, field, or action falls within Registry authority.
A governed result of Scope Determination, such as Within Scope, Within Scope with Conditions, Shared or Coordinated Scope, Restricted Scope, Outside Scope, or Indeterminate.
A condition in which Registry has a defined registration, cataloging, publication, or preservation role while another institution retains related substantive authority.
A condition in which an object remains within Registry's institutional domain but access, Publication, indexing, or disclosure is limited.
The determination of whether a specific object satisfies Registry requirements for registration as a SREG.
The governed result of Registrability review, such as Registrable, Conditionally Registrable, Provisionally Registrable, Restricted Registrable, Historical Registrable, Not Registrable, Indeterminate, or Not Evaluated.
The permanent, unique, non-reused identifier assigned by Registry to a SREG or other approved Registry object.
A Registry Identifier assigned specifically to a Satoshium Registry Entry.
An identifier assigned by the Source Institution or source system to the Authoritative Source Record.
The institutional namespace or system within which an identifier is assigned and interpreted.
The governed condition of an identifier, such as Reserved, Assigned, Published, Superseded, Revoked, or Archived.
The process by which a Registry Identifier resolves to the official current Registry context while preserving access to prior and historical states.
A non-canonical alternate label, identifier, title, code, or historical reference preserved for discovery, compatibility, or interpretation.
The common structural schema defining fields and requirements shared across all Satoshium Registry Entries.
The Registry-level specification governing how schemas, fields, types, constraints, versions, and machine-readable representations are defined.
The version assigned to a schema definition used to interpret and validate Registry records.
A governed canonical value, code, label, status, outcome, type, or notice approved for use within a defined Registry field or value set.
A governed collection of related Controlled Values, definitions, codes, labels, usage rules, versions, aliases, and historical replacements.
The current authoritative Registry meaning assigned to a term.
A typed, directed or governed association between Registry Identifiers, Source-System Identifiers, Source Records, institutions, versions, or related objects.
The governed meaning assigned to a Registry Relationship, such as sourced from, references, certifies, attests to, supersedes, derived from, or archived as.
The governed current condition of a Registry Relationship, such as Active, Historical, Provisional, Disputed, Superseded, Revoked, or Invalid.
The governed reciprocal expression of a directed relationship, such as “sourced from” and “source of.”
A relationship whose meaning applies identically in both directions when explicitly defined as symmetric by Registry Governance.
The temporal, version, authority, evidence, or scope conditions under which a Registry Relationship applies.
The recorded origin, authority, source lineage, custody, derivation, transformation, publication, and preservation history of a Registry object or Source Record representation.
The possession, storage, stewardship, or preservation of a record or artifact. Custody does not by itself establish Source Authority.
Custody held by the original creator or originating institution.
Custody held for preservation of a record or artifact after or apart from its original operational use.
A machine-readable or human-readable record describing how a generated artifact was produced, including source inputs, process, date, version, and integrity information.
A record or value used to support integrity verification of an artifact, record, version, or publication.
The process of evaluating whether a SREG or Registry object conforms to applicable Registry Rules, Policies, Procedures, schemas, profiles, Controlled Values, and Publication requirements.
A Registry-owned record documenting the object validated, requirements applied, date, findings, exceptions, outcome, and related action.
The governed result of Registry Validation, such as Valid, Valid with Warnings, Conditionally Valid, Invalid, Indeterminate, or Not Evaluated.
A Validation finding that prevents approval, Publication, or continued operation until resolved or governed through an authorized process.
A non-blocking Validation finding that must remain visible or be reviewed but does not necessarily prevent Publication.
A documented and authorized departure from an otherwise applicable Validation requirement.
A Validation observation recorded for context, future review, or transparency without constituting an error or warning.
The authorized release of a SREG or Registry object as an official human-readable, machine-readable, downloadable, indexed, or historical Registry representation.
A Registry-owned record documenting publication authority, date, version, canonical URLs, Validation outcome, notices, restrictions, and related history.
The governed determination of whether a Registry object satisfies the requirements for Publication.
The governed result of Publication review, such as Ready, Ready with Notices, Restricted, or Not Ready.
The official Registry presentation designed for human interpretation.
The official Registry representation designed for structured processing by systems.
A visible Registry statement identifying a material condition, warning, restriction, Correction, supersession, revocation, archival state, or limitation.
The version assigned by Registry to a distinct state of a SREG.
The version assigned by the Source Institution or source system to the Authoritative Source Record.
The version assigned to a generated or published Registry Catalog collection, distinct from the versions of individual SREGs.
The version assigned to a canonical Registry definition or Definitions set.
A material change that alters structure, meaning, compatibility, authority, or interpretation sufficiently to require a major version increment.
A backward-compatible material addition or refinement that does not replace the prior fundamental meaning or structure.
A limited correction or refinement that preserves the existing meaning, structure, and compatibility of the record.
The governed replacement of a Registry object, version, decision, Policy, Procedure, schema, profile, or value by a successor while preserving the prior object historically.
An authorized change to a Registry-owned field, record, representation, or historical statement made to remedy an identified error or omission.
A Registry-owned record documenting the affected object or version, prior value, corrected value, reason, authority, evidence, date, and resulting version.
The Registry role, institution, Governance decision, or authorized process empowered to approve a Correction.
A Correction made under Source Institution authority to the Source Record itself, distinct from a Registry Correction.
A material change made without preserving or disclosing the prior state, Correction authority, or change history. Silent material Correction is not permitted within Registry.
The current Registry condition of a SREG, such as Pending, Active, Restricted, Disputed, Superseded, Revoked, Retired, or Archived.
The stage occupied by a SREG within the Registry lifecycle, such as Proposed, Under Review, Registered, Published, Updated, Superseded, Revoked, Retired, or Archived.
The source-domain status assigned to the Authoritative Source Record by the Source Institution.
An authorized movement from one Registry Lifecycle State to another.
The authorized withdrawal of a SREG, relationship, identifier use, exception, or other Registry object from valid active operation.
The intentional removal of a Registry object from active operational use without necessarily declaring it invalid.
The transition of a Registry object or artifact into a preserved historical condition with continued contextual resolution.
The institutional framework through which Registry authority, decision rights, roles, approvals, changes, exceptions, conflicts, delegations, reviews, and accountability are controlled.
An authorized institutional decision affecting Registry Rules, Policies, Procedures, schemas, profiles, Controlled Values, Scope, operations, or other governed materials.
A Registry-owned record documenting a Governance Decision, authority, rationale, evidence, date, scope, conditions, implementation, and history.
A binding Registry requirement governing institutional or operational conduct.
A governed statement defining institutional principles, requirements, decision criteria, or operating conditions under Registry Rules.
A governed operational sequence describing how Registry implements an approved Rule, Policy, framework, or decision.
An authorized, limited, documented departure from an applicable Registry requirement that does not silently amend the underlying Rule or Policy.
A documented grant of defined decision or action authority to a role, process, or institution while accountability remains traceable to the delegating authority.
The public discovery and resolution layer through which published SREGs are organized, browsed, searched, filtered, related, versioned, and accessed.
The discovery-oriented representation of a published SREG within the Registry Catalog.
Registry-owned metadata used to support discovery, filtering, ordering, indexing, notices, and Catalog presentation without changing canonical SREG meaning.
A governed grouping of SREGs by Record Type, Source Institution, Status, Lifecycle, publication period, historical condition, or other approved classification.
The governed act of placing a published SREG into current or historical Catalog views.
The chronological, versioned, attributable, and resolvable institutional history of Registry objects, actions, decisions, versions, Corrections, transitions, Publications, Catalog releases, and Governance changes.
A Registry-owned record documenting a material Registry event, prior state, new state, date, authority, version context, evidence, and historical resolution.
A governed classification describing the kind of institutional event recorded in Registry History.
A prior state of a Registry object preserved for interpretation, accountability, provenance, or archival resolution.
A preserved prior publication, record, schema, profile, Policy, Procedure, Controlled-Value Set, Catalog, or other artifact retained as part of Registry History.
The ability to locate and interpret a prior Registry state or artifact through stable identifiers, versions, relationships, or archival paths.
The institutional framework through which Registry makes its authority, requirements, decisions, conditions, limitations, versions, Corrections, restrictions, and history visible and accountable.
A Registry-owned record documenting the subject, Disclosure Level, public fields, restricted fields, authority, basis, effective date, review date, and change history of a transparency decision.
The governed visibility condition applied to information, such as Public Disclosure, Public Summary, Controlled Access, Internal Record, or Non-Disclosure.
A limited public disclosure that communicates material facts while withholding restricted supporting information.
A governed limitation on access, Publication, indexing, reuse, disclosure, or resolution arising from privacy, rights, safety, security, contractual, legal, Source Institution, or institutional requirements.
The authorized removal of a Registry Publication or public representation from current public availability while preserving appropriate historical accountability.
The Suite-level framework defining how institutions exchange, reference, preserve, and coordinate records while maintaining authority boundaries.
The Registry implementation of Suite Interoperability through identifiers, schemas, profiles, Controlled Values, relationships, provenance, mappings, Publications, and workflows.
A documented correspondence between Registry values, fields, identifiers, or concepts and those of another system or institution.
A mapping that identifies corresponding or related meanings while preserving known differences and authority boundaries.
A governed technical or institutional connection through which Registry exchanges, references, receives, publishes, or coordinates records with another Suite or external system.
Definitions and Controlled Values serve related but distinct purposes.
Registry may preserve:
Aliases and deprecated terms should not replace current canonical terminology in new Registry materials.
A material definition change should preserve:
Validation should confirm:
Registry Governance should control:
Definitions should be reviewed when:
Scope defines Registry authority and boundaries.
Definitions provides the canonical meanings required to describe those boundaries consistently.
Schemas define fields, types, structure, and constraints.
Definitions explains the institutional meaning of the concepts represented by those fields.
Policies and Procedures should use canonical Registry terminology.
They may apply Definitions but should not silently redefine foundational terms through operational language.
Transparency depends on definitions that make authority, limitations, conditions, and historical changes understandable.
Public materials should not require users to infer the difference between Registry-owned concepts and source-owned concepts.
Registry Definitions should provide stable, precise, versioned institutional meanings that preserve authority boundaries, operational consistency, historical interpretation, and semantic alignment across every Registry form.