Registry · Registrability

Satoshium Registry Registrability

Registrability defines the institutional threshold an Authoritative Source Record must satisfy before Satoshium Registry may create, validate, and publish a Satoshium Registry Entry.

Not every identifiable source should become a SREG. Registration requires authority, scope, classification, minimum metadata, and a durable reason for inclusion.

Constitutional Position

Registrability operates after Source Authority review and before operational SREG construction.

Source Identified → Source Authority Confirmed → Registrability Determined → SREG Constructed → Validated and Published

Source Authority answers who controls the source. Registrability determines whether Registry should create a SREG for it.

Why Registrability Matters

A Registry that catalogs everything without threshold or discipline becomes noisy, inconsistent, and difficult to trust.

Registrability protects the quality, coherence, and long-term usefulness of the Registry catalog.

The Core Question

Registrability asks:

Does this Source Record possess sufficient authority, identity, scope, structure, and institutional relevance to justify creation of a SREG?

Registry's Responsibility

Registry must evaluate proposed records consistently and document why a record was accepted, accepted with conditions, deferred, or rejected.

Registry's Limitation

A Registrability determination does not certify the Source Record, endorse its content, establish legal authority, or confirm every substantive claim.

Canonical Registrability Threshold

Authority + Identity + Scope + Record Type + Minimum Metadata + Durable Relevance → Registrable

The exact threshold may vary by Record Type, but every operational SREG should satisfy the shared institutional minimum.

Core Registrability Requirements

a sufficiently identified Source Institution;
a sufficiently identified Authoritative Source Record;
a supported Source Authority determination;
a clear reason the record belongs within Registry scope;
an approved Registry Record Type;
minimum metadata required by the SREG Base Schema;
minimum fields required by the applicable Record-Type Profile;
a durable canonical or archival reference;
enough provenance to trace the record back to its source;
no unresolved defect that would materially misrepresent the source;
no prohibited legal, privacy, safety, or security condition;
a documented Registrability outcome.

Authority Requirement

The Source Institution must be identified with enough confidence to support attribution and preserve institutional responsibility.

Identity Requirement

The Source Record must be distinguishable from related records, versions, mirrors, derivatives, and subjects.

Scope Requirement

The proposed record must fall within Registry's approved institutional scope.

Classification Requirement

One approved primary Registry Record Type must accurately classify the SREG.

Metadata Requirement

Required Base Schema and Record-Type Profile fields must be available or capable of documented completion.

Durability Requirement

The source should possess enough institutional relevance, persistence, or historical significance to justify durable cataloging.

Registry Scope Review

A proposed source should align with one or more Registry purposes:

public discoverability;
institutional continuity;
cross-Suite interoperability;
preservation of identity and provenance;
classification of authoritative records;
relationship mapping;
version and lifecycle tracking;
historical preservation;
machine-readable publication;
support for future workflows and queries.

A source that cannot reasonably serve an approved Registry purpose may be outside scope even when it is legitimate and authoritative.

Approved Source Categories

Potential registrable source categories include:

Suite institutional records;
Atlas jurisdiction resources;
Certifier certification artifacts;
Chronicle historical events;
Anchor integrity references;
Beacon signals;
Attestor attestations;
Navigator workflow definitions;
approved tools and systems;
approved media records;
approved external records;
historical records with durable institutional relevance.

Inclusion in a general category does not guarantee that every individual record is registrable.

Public and Non-Public Sources

Public availability may support discoverability, but it is not the only possible basis for registration.

Registry may consider:

public Source Records;
restricted institutional records;
historical records preserved through archives;
machine-readable records without public presentation;
public summaries referencing controlled source artifacts;
records whose metadata may be public even when content is restricted.

Restricted registration requires clear authority, access controls, rights review, and publication boundaries.

Public Registrability

The SREG and its essential metadata may be published openly.

Restricted Registrability

The SREG may be created with controlled or limited publication when justified by rights, privacy, safety, security, or institutional policy.

Historical Registrability

A record may remain registrable after retirement, withdrawal, revocation, unavailability, or institutional dissolution.

Provisional Registrability

Registry may defer final publication while preserving a documented pending review state.

Minimum Metadata

The shared minimum should normally include:

proposed title;
proposed Registry Record Type;
Source Institution;
Authoritative Source Record;
Source-System Identifier, when available;
canonical or archival reference;
source object description;
Source-Record Status, when available;
source version, when available;
source publication or effective date, when available;
provenance information;
applicable Record-Type Profile;
Registrability review outcome;
review date and supporting references.

Record-Type Profiles may require additional fields.

Durable Relevance

Registry should prioritize records that provide enduring value beyond a temporary mention, isolated draft, or transient technical artifact.

Durable relevance may arise from:

institutional authority;
operational use;
historical significance;
cross-Suite relationships;
public accountability;
version or lifecycle importance;
future workflow dependency;
preservation need;
machine-readable interoperability;
continued discovery value.

Duplicate and Redundant Sources

Registry should determine whether a proposed source is:

already represented by an existing SREG;
a new version of an existing Source Record;
a mirror or duplicate publication;
a derivative that merits its own SREG;
a distinct record concerning the same subject;
a successor requiring supersession;
an archival representation of an unavailable source.

Duplicate publication should not create duplicate Registry identity.

Potentially Non-Registrable Sources

A proposed source may be non-registrable when:

Source Authority cannot be established;
the source object cannot be identified reliably;
the record falls outside Registry scope;
no approved Record Type applies;
minimum metadata is unavailable;
the proposal is merely a duplicate or mirror;
the source is too transient to justify durable identity;
the record would materially misrepresent institutional authority;
publication would violate rights, privacy, safety, or security obligations;
the proposal seeks endorsement rather than cataloging;
the record is fabricated, deceptive, or materially unsupported;
the proposed SREG would create unresolved contradiction with existing Registry records.

Registrability Review Process

Receive Proposal → Confirm Source Authority → Check Scope → Identify Record Type → Review Metadata → Check Duplicates and Conflicts → Record Outcome

A positive outcome authorizes SREG construction. It does not complete validation or publication.

Registrability Review Record

A review should preserve:

proposed Source Institution;
proposed Source Record;
Source Authority outcome;
scope determination;
proposed Record Type;
minimum metadata assessment;
duplicate and conflict review;
rights, privacy, safety, and security review;
durable-relevance assessment;
review outcome;
conditions or limitations;
review date;
reviewer or process;
supporting references;
required follow-up.

Registrability Outcomes

Registrable — the source satisfies the required threshold.
Registrable with Conditions — the source may proceed subject to documented limitations or follow-up.
Provisionally Registrable — the source may proceed only within a controlled pending state.
Deferred — the source may become registrable after additional evidence, metadata, or governance review.
Non-Registrable — the source does not satisfy the current threshold.
Rejected — the proposal is materially unsupported, deceptive, prohibited, or outside institutional scope.

A Registrability outcome governs whether Registry proceeds. It does not determine the truth or substantive merit of the Source Record.

Registrable

Registry may proceed to identifier assignment and SREG construction.

Registrable with Conditions

Registry may proceed while preserving required limitations, review dates, or publication controls.

Deferred

Registry pauses the proposal pending evidence, metadata, classification, or governance action.

Non-Registrable

Registry does not create an operational SREG under the current proposal.

Conditional Registrability

Conditions may include:

additional authority evidence;
restricted publication;
future metadata completion;
provisional classification;
scheduled review;
source-version confirmation;
rights clarification;
relationship reconciliation;
duplicate resolution;
governance approval.

Conditions should be explicit, attributable, versioned, and reviewable.

Historical and Unavailable Records

A record may remain registrable even when it is no longer active or publicly available.

Historical registrability may be supported by:

archival copies;
integrity references;
prior canonical URLs;
version history;
institutional release records;
Chronicle events;
successor references;
documented source withdrawal or retirement.

Historical value may strengthen registrability even when current availability is limited.

External Records

External records may be registrable when:

the Source Institution is identifiable;
the source is within Registry scope;
an approved Record Type applies;
the source has durable relevance;
minimum metadata is available;
provenance can be preserved;
registration does not imply endorsement or affiliation;
rights and publication boundaries are respected.

Relationship to Identifier Assignment

Registry should assign a permanent Registry Identifier only after a positive Registrability outcome.

Registrability authorizes identity creation. Identifier assignment does not retroactively make a source registrable.

Relationship to Validation

Registrability review determines whether Registry should create the SREG.

Validation determines whether the constructed SREG satisfies the applicable schema, profile, identifier, status, version, relationship, provenance, and publication requirements.

Registrability comes before construction. Validation comes after construction.

Relationship to Registry Lifecycle

Proposed entries may begin in a pending state while Registrability is under review.

A positive outcome may allow progression toward Registered or Active status. Deferred, non-registrable, or rejected proposals should not be presented as operational SREGs.

Relationship to Corrections

A Registrability determination may require correction when:

Source Authority was misidentified;
the source was outside scope;
the wrong Record Type was selected;
duplicate identity was overlooked;
minimum metadata was materially incomplete;
rights or restrictions were misstated;
the review outcome was recorded incorrectly.

Corrections should preserve the original decision, the corrected decision, supporting evidence, date, reason, and affected Registry version.

Validation Requirements

A Registrability review should confirm:

Source Authority review is complete or explicitly provisional;
the source falls within Registry scope;
one approved Record Type applies;
minimum metadata is present;
required references are available;
duplicate and conflict checks were performed;
conditions and limitations are explicit;
the outcome is attributable and dated;
the outcome is consistent across human-readable and machine-readable records.

What Registrability Does Not Establish

It does not certify the Source Record.
It does not confirm every substantive claim.
It does not establish legal ownership.
It does not grant licensing rights.
It does not create governmental authority.
It does not create endorsement or affiliation.
It does not guarantee permanent availability.
It does not guarantee publication.
It does not replace schema validation.
It does not transfer source authority to Registry.

Registrability Principle

Registry should create a SREG only when the Source Record can be attributed, classified, described, traced, and preserved without misrepresenting the authority or meaning of the source.

Authority makes the source attributable. Registrability determines whether Registry should create the SREG.

Back to Registry → Open Source Authority → Open Entry Model →