Registry · Source Authority

Satoshium Registry Source Authority

Source Authority defines how Satoshium Registry identifies the institution responsible for an Authoritative Source Record and preserves the path back to that institution without transferring or recreating its authority.

Registry may catalog a source. It may not become the source merely by registering it.

Constitutional Position

Source Authority operates within the Satoshium Suite constitutional hierarchy and the Registry's canonical operational model.

Suite StandardsSuite MethodologySuite InteroperabilitySource InstitutionAuthoritative Source RecordSREG
The Source Institution creates and controls the Source Record. Registry creates and controls the SREG that catalogs it.

Why Source Authority Matters

Registry must know who is responsible for a source before it can represent that source accurately.

Without clear authority, a SREG may misidentify ownership, reproduce an unofficial copy, preserve outdated information, or imply institutional approval that does not exist.

The Core Question

Source Authority asks:

Which institution created, issued, maintains, or otherwise controls the authoritative record being registered?

Registry's Responsibility

Registry must identify, document, and preserve the Source Institution, Source-System Identifier, canonical source reference, source version, and available source-status information.

Registry's Limitation

Registry does not create source authority, legal authority, ownership, certification authority, attestation authority, governmental authority, or editorial authority merely by cataloging a record.

Canonical Authority Relationship

Source InstitutionAuthoritative Source RecordRegistry ReferenceSREG

The Source Institution owns the source-domain meaning of the record. Registry preserves the structured public path back to it.

Source Authority Determination

Registry should determine Source Authority by reviewing the strongest available evidence of institutional responsibility.

  • canonical institutional publication;
  • official repository ownership;
  • signed or issued institutional artifact;
  • documented identifier assignment;
  • governing policy or institutional statement;
  • recognized publication channel;
  • record metadata identifying the issuer or maintainer;
  • version history or release history;
  • corresponding machine-readable source record;
  • archival evidence preserving prior institutional control.

Primary Source Institution

The institution with direct responsibility for creating, issuing, publishing, or maintaining the Authoritative Source Record.

Supporting Institution

An institution that provides evidence, hosting, preservation, publication, or interoperability support without owning the Source Record's institutional meaning.

Platform or Repository

A technical service may host or distribute a record without becoming the Source Institution.

Rights Holder

Ownership or licensing authority may belong to a rights holder distinct from the Source Institution that created or issued the record.

Required Authority Fields

A SREG should preserve the following authority information when applicable:

  • Source Institution name;
  • Source Institution identifier;
  • Authoritative Source Record title or name;
  • Source-System Identifier;
  • canonical source reference;
  • source object type;
  • source version;
  • source publication or issuance date;
  • source effective date;
  • Source-Record Status;
  • publisher or repository;
  • rights or licensing reference;
  • supporting authority evidence;
  • authority determination date;
  • Registry review reference.

Authority Evidence

Registry should preserve enough evidence to explain why a particular institution was identified as the Source Institution.

Authority evidence supports the Registry determination. It does not replace the Source Institution's own authority.

Evidence may be direct, corroborating, historical, or archival. The evidence type and confidence should be clear when authority is not self-evident.

Direct Authority

The Source Institution publishes or issues the record through its own canonical channel.

Delegated Publication

A Source Institution authorizes another platform, repository, or publisher to distribute the record while retaining institutional authority.

Historical Authority

The original Source Institution may no longer operate, but historical records establish who created or controlled the source.

External Authority

Registry may catalog approved external sources when institutional ownership, provenance, registrability, and scope are sufficiently established.

Multiple Sources

Multiple institutions may publish information about the same subject. Registry must determine whether they represent:

  • the same Source Record;
  • different versions of one Source Record;
  • distinct Source Records about the same subject;
  • a canonical source and one or more mirrors;
  • an original source and derivative records;
  • competing institutional claims;
  • historical predecessor and successor records.
Similar subject matter does not make two records the same source object.

Conflicting Authority Claims

When two or more institutions claim authority over the same Source Record, Registry should not silently choose one without documented review.

Registry may:

  • delay registration;
  • mark the authority determination as unresolved;
  • register distinct records when the source objects are genuinely separate;
  • preserve competing claims as structured relationships;
  • request additional institutional evidence;
  • record a provisional determination;
  • refer the matter through Registry governance.

Mirrors, Copies, and Derivatives

A mirror, copy, transcript, export, cached page, archived snapshot, translated version, or derived representation may support discovery or preservation.

It should not be treated as the Authoritative Source Record unless the Source Institution explicitly designates it as authoritative.

A preserved copy may be important. A preserved copy is not automatically the canonical source.

Unavailable or Removed Sources

A Source Record may become unavailable because a page moved, a repository was deleted, access was restricted, a platform removed content, or an institution ceased operation.

Registry may preserve:

  • the last known Source Institution;
  • the last known canonical reference;
  • the Source-System Identifier;
  • the last known source version;
  • archival references;
  • integrity references;
  • historical relationships;
  • the date availability changed;
  • the reason for unavailability, when known.

Source unavailability does not automatically erase prior authority or require deletion of the SREG.

Authority Changes

Institutional responsibility for a Source Record may change through:

  • organizational succession;
  • repository transfer;
  • publisher migration;
  • merger or acquisition;
  • governance reassignment;
  • formal delegation;
  • institutional dissolution;
  • archival transfer.

Registry should preserve both prior and current authority context rather than silently overwriting the historical record.

Authority Change

The institution responsible for the same continuing Source Record changes.

Source Replacement

A new Source Record replaces the prior object and may require supersession or a new SREG.

Institutional Succession

A successor institution assumes responsibility for records created by a predecessor.

Archival Custody

An archive preserves the record without necessarily inheriting the original institution's substantive authority.

Source Authority Review

A source-authority review should document:

  • the proposed Source Institution;
  • the proposed Authoritative Source Record;
  • supporting authority evidence;
  • the canonical reference;
  • known mirrors or derivatives;
  • known competing claims;
  • historical authority context;
  • confidence or certainty;
  • review outcome;
  • review date;
  • reviewer or process;
  • required follow-up.

Source Authority Outcomes

Potential review outcomes may include:

  • Confirmed — Source Institution and Source Record are sufficiently established.
  • Confirmed with Conditions — authority is established, but limitations or review conditions remain.
  • Provisional — the best available authority is identified pending additional evidence.
  • Ambiguous — multiple plausible authority claims remain unresolved.
  • Insufficient — available evidence does not support registration.
  • Rejected — the proposed authority claim is materially unsupported or incorrect.
These values describe Registry's authority review. They do not create or revoke source authority.

Relationship to Registrability

Source IdentifiedAuthority ReviewedAuthority OutcomeRegistrability Review

Source Authority is a prerequisite for Registrability.

A source should not proceed to operational SREG creation when Registry cannot identify who controls the Source Record or cannot explain the basis for its authority determination.

Relationship to Provenance

Source Authority identifies who controls the Source Record.

Provenance preserves the traceable path from the SREG back through references, versions, custody, publication, and institutional history.

Authority answers who. Provenance explains the path.

Relationship to Validation

Source-authority validation should confirm:

  • the Source Institution is identified;
  • the Authoritative Source Record is identifiable;
  • the source reference is attributable;
  • the Source-System Identifier is preserved when available;
  • mirrors and derivatives are not misrepresented as canonical sources;
  • rights and ownership are not inferred without support;
  • authority changes are historically preserved;
  • human-readable and machine-readable SREG forms agree.
Registry validation confirms the structure and support for its authority determination. It does not certify the ultimate truth of the Source Record.

Suite Institution Examples

Atlas

Atlas is authoritative for Atlas jurisdiction resources, canonical jurisdiction records, evidence layers, and Atlas machine-readable packages.

Certifier

Certifier is authoritative for Certification Packages, SCPR, SCR, SCRD, Certification Outcome, and Certification Status.

Chronicle

Chronicle is authoritative for Chronicle-created historical events and institutional chronology records.

Anchor

Anchor is authoritative for Anchor-created integrity references, hashes, timestamps, signatures, and verification points.

Beacon

Beacon is authoritative for Beacon-created signals and discovery metadata.

Attestor

Attestor is authoritative for attestations, trust statements, validation records, and Attestor-controlled status.

Navigator

Navigator is authoritative for Navigator-created workflow definitions and coordination records.

Registry

Registry is authoritative for SREGs and Registry-owned metadata, not for the substantive source objects created by other institutions.

What Source Authority Does Not Establish

  • It does not certify the Source Record.
  • It does not verify every substantive claim in the source.
  • It does not establish legal ownership without supporting authority.
  • It does not grant licensing or reuse rights.
  • It does not make a mirror canonical.
  • It does not convert a platform into the Source Institution.
  • It does not resolve governmental or territorial disputes.
  • It does not transfer authority to Registry.
  • It does not guarantee continued source availability.
  • It does not eliminate the need for provenance and validation.

Source Authority Principle

Registry must be able to explain who controls the source, what record is authoritative, where that record can be found, and what evidence supports the determination.

The source institution holds authority. Registry preserves the structured path back to it.
Back to Registry →Open Entry Model →Open Integration →

Authority begins at the source. Registry preserves the path back to it.