Registry · Status Architecture

Satoshium Registry Status

Registry Status defines the Registry-controlled condition of a Satoshium Registry Entry, or SREG. It must remain distinct from Registry Lifecycle State and every source-controlled status domain.

The central rule is simple: each institution owns the status values whose meaning it creates.

Constitutional Position

Source Institution → Source-Record Status · Registry → Registry Status · Registry Lifecycle State

Registry may report source-controlled status values, but it does not own or redefine them. Registry owns only Registry Status and Registry Lifecycle State.

Registry Development Condition

Registry is in active institutional implementation, with its architecture, rules, schemas, policies, record types, record profiles, and public pages being formalized for operational use.

Current Institutional Priority

Establish one coherent SREG framework with controlled identifiers, statuses, lifecycle states, versions, relationships, schemas, validation, and publication.

Current Capability

Registry supports the architecture required to identify, classify, catalog, relate, validate, publish, update, correct, supersede, revoke, and preserve SREGs.

Current Limitation

Operational record populations, automated validation, machine-readable indexes, status mappings, and lifecycle automation remain subject to continuing implementation.

Status Ownership

Every status value must remain attached to the institution that defines its meaning.

Certifier owns Certification Status and Certification Outcome.
Attestor owns attestation status and attestation conclusions.
Atlas owns source-resource status for Atlas records.
Chronicle owns event status within Chronicle.
Anchor owns integrity-reference status.
Beacon owns signal status.
Navigator owns workflow status.
Registry owns Registry Status and Registry Lifecycle State.

Status may be referenced across institutions. Authority over that status does not transfer.

Registry Status

Registry Status describes the Registry-controlled operational condition of the SREG. It answers whether Registry considers the entry eligible for active publication, historical publication, restricted publication, or another approved Registry condition.

Registry Lifecycle State

Registry Lifecycle State describes the institutional stage or condition of the SREG over time. It supports creation, maintenance, replacement, revocation, and preservation.

Source-Record Status

Source-Record Status is controlled by the Source Institution and describes the condition of the Authoritative Source Record.

Source-Specific Status

Certification, attestation, tool, media, jurisdiction, signal, workflow, and integrity statuses remain source-specific even when reproduced inside a SREG.

Status Domains Must Remain Distinct

Registry Status ≠ Registry Lifecycle State ≠ Source-Record Status ≠ Certification Status ≠ Certification Outcome ≠ Attestation Status ≠ Tool Implementation Status

Reusing one status value across domains without explicit mapping creates ambiguity and may misrepresent institutional authority.

Illustrative Status Combination

Certification Outcome: Certified
Certification Status: Revoked
Source-Record Status: Published Historical Record
Registry Status: Active Historical Entry
Registry Lifecycle State: Active

This combination is valid because the certification may be revoked while Registry continues to preserve an active historical SREG documenting that certification.

Potential Registry Status Values

Registry Status values should be defined through controlled governance. Potential values may include:

Pending Review;
Active;
Active Historical Entry;
Restricted;
Suspended;
Withdrawn;
Archived.

These values describe Registry publication or recognition of the SREG. They do not describe the truth, validity, or authority of the Source Record.

Registry Lifecycle States

Potential approved lifecycle states may include:

Pending Registration → Registered → Active · Updated · Superseded · Revoked · Archived

These states do not necessarily form one mandatory linear chain. A SREG moves only through the states required by its actual institutional history.

Pending Registration

The source has been identified for possible registration, but the SREG has not yet completed authority, registrability, schema, and publication review.

Registered

Registry has created the SREG, assigned its Registry Identifier, and completed the minimum required registration controls.

Active

The SREG is the current active Registry representation of the referenced Source Record or is intentionally maintained as an active historical entry.

Updated

Registry has published a revised SREG version reflecting new source information, changed Registry metadata, relationships, references, or schema migration.

Superseded

A distinct successor SREG or replacement Registry object has taken its place. The prior entry remains discoverable for historical continuity.

Revoked

Registry has withdrawn the SREG from active Registry recognition because of a Registry-controlled defect, invalid registration, or another documented reason.

Archived

The SREG is preserved outside active operational use.

Archived does not mean deleted. It means preserved with identity, source references, versions, relationships, corrections, and history intact.

Status Transition Requirements

A Registry Status or Lifecycle transition should preserve:

affected Registry Identifier;
prior value;
new value;
effective date;
reason;
authority for the change;
affected Registry Entry Version;
related source-status change, when applicable;
supporting reference;
successor or archival reference, when applicable.

Status Mapping

Registry may map source-controlled statuses to Registry display or workflow behavior, but the mapping must be explicit.

A mapping should identify:

source status domain;
source status value;
Registry interpretation;
Registry Status effect, if any;
Registry Lifecycle effect, if any;
whether human review is required;
effective version;
governing policy.

Mapping does not transfer ownership of the source-controlled status to Registry.

Relationship to Certifier

Certification Package → SCRD → Certification SREG

Certifier remains authoritative for Certification Outcome, Certification Status, the Certification Package, SCPR, SCR, and SCRD.

Registry remains authoritative for the Certification SREG, Registry Status, Registry Lifecycle State, Registry Entry Version, Registry relationships, and Registry publication history.

Relationship to the Suite

Registry connects Suite institutions while preserving status ownership.

Atlas creates jurisdiction intelligence. Certifier creates certification records. Chronicle creates historical events. Anchor creates integrity references. Beacon creates signals. Attestor creates attestations. Navigator creates workflows. Registry creates SREGs.

Validation Requirements

Status validation should confirm:

Registry Status uses an approved Registry-controlled value;
Registry Lifecycle State uses an approved lifecycle value;
Source-Record Status remains attributable to the Source Institution;
source-specific statuses are stored in the correct domains;
status mappings are explicit;
transition history is preserved;
human-readable and machine-readable forms agree;
status values do not imply unsupported authority.

Publication Requirements

Human-readable and machine-readable forms of the same SREG should agree on:

Registry Status;
Registry Lifecycle State;
Source-Record Status;
source-specific status values;
effective dates;
version context;
transition references;
successor, revocation, or archival references.

Future Development

Future status capabilities may include:

machine-readable status enumerations;
status transition records;
source-to-Registry mapping tables;
automated consistency checks;
status history indexes;
cross-institution synchronization;
status-based catalog filters;
lifecycle automation with human review controls.

Future development must preserve institutional status ownership.

Status Principle

Source Institutions own source status. Registry owns Registry Status. Registry Lifecycle State describes the SREG. Historical preservation does not require pretending that the source remains active.

Back to Registry → Open Lifecycle → Open Schemas →