Satoshium Registry Governance

Governance Framework

Governance Domains

• constitutional alignment;
• Registry authority and scope;
• Rules governance;
• Policy governance;
• Procedure governance;
• schema and profile governance;
• controlled-value governance;
• identifier governance;
• Record-Type governance;
• relationship governance;
• provenance governance;
• validation governance;
• publication governance;
• versioning governance;
• correction governance;
• status and lifecycle governance;
• exception governance;
• conflict resolution;
• restricted-access governance;
• preservation and archival governance;
• transparency and accountability.

Governance Authority

Governance authority may be exercised through:

• the Registry institution;
• the Founder or designated institutional steward;
• approved Registry governance roles;
• approved review bodies or councils;
• documented automated controls operating under approved authority;
• delegated decision roles with defined scope;
• Suite-level authority where constitutional alignment is required.

Decision Rights

Governance should define who may:

• approve Registry Rules;
• approve or amend Policies;
• approve or revise Procedures;
• create or retire Registry Record Types;
• approve schemas and Record-Type Profiles;
• approve controlled values;
• approve identifier namespaces and patterns;
• approve validation outcomes or exceptions;
• authorize publication, correction, restriction, revocation, or archival action;
• resolve conflicts;
• approve migrations and compatibility changes;
• delegate operational authority;
• review or reverse prior Registry decisions.

Governance Roles

Registry may distinguish among:

• Authority — holds final decision responsibility.
• Approver — formally approves a proposal or action.
• Reviewer — evaluates consistency, evidence, risk, and readiness.
• Operator — executes approved Procedures.
• Maintainer — preserves records, schemas, documentation, and publication.
• Custodian — preserves artifacts or records without necessarily controlling meaning.
• Observer — monitors compliance or reports concerns without decision authority.

Separation of Duties

Material Registry actions may require separation among:

• proposal;
• review;
• approval;
• implementation;
• validation;
• publication;
• audit or historical review.

Separation should be proportional to the significance, risk, and reversibility of the action.

Governance Decision Record

Material governance decisions should preserve:

• decision identifier;
• title;
• decision authority;
• proposal or issue reference;
• decision date;
• effective date;
• scope;
• decision text;
• rationale;
• evidence reviewed;
• affected Registry materials;
• implementation requirements;
• exceptions or conditions;
• review date;
• superseded decision reference;
• publication and history references.

Illustrative Governance Record

Rules Governance

• Registry Rules require clear authority and approval.
• Rule changes must preserve version history and effective dates.
• Rules must remain aligned with Suite Standards and Methodology.
• Conflicting Rules must be resolved through documented Governance.
• Rules should not be changed through ordinary Procedure updates.
• Superseded Rules must remain historically discoverable.

Policy Governance

• Policies require identified authority, scope, version, approval, and effective date.
• Policies must remain consistent with Rules.
• Material policy changes require review of affected Procedures, schemas, profiles, and publications.
• Exceptions must not silently rewrite Policy.
• Prior Policy Versions must remain discoverable.

Procedure Governance

• Procedures require defined authority, version, prerequisites, steps, outputs, and records.
• Procedures must remain consistent with Rules and Policies.
• Operational convenience must not silently change institutional requirements.
• Procedure changes should trigger training, migration, or workflow updates when needed.
• Prior Procedure Versions must remain discoverable.

Schema and Profile Governance

• SREG Base Schema changes require documented approval.
• Record-Type Profiles require versioning and compatibility review.
• Breaking changes require migration or explicit continued support for prior versions.
• Deprecated fields and values must remain interpretable in historical records.
• Schema changes must be reconciled with Validation and Publication requirements.

Controlled-Value Governance

• Controlled values require approved definitions.
• Addition, amendment, deprecation, and retirement must be documented.
• Renamed values must preserve historical interpretation.
• Inverse and symmetry rules for relationships require approval.
• Validation outcomes, statuses, lifecycle states, and notice types must remain governed.

Identifier Governance

• Identifier namespaces and patterns require approval.
• Registry Identifiers must remain unique and non-reusable.
• Identifier corrections require preserved history.
• Reserved, assigned, published, superseded, and archived identifier conditions must be governed.
• Changes to identifier architecture require migration and resolution planning.

Record-Type Governance

• New Registry Record Types require defined scope and purpose.
• Each Record Type should have an approved Profile.
• Overlapping types require documented boundaries.
• Reclassification rules must preserve history.
• Deprecated Record Types must remain interpretable for historical SREGs.

Validation Governance

• Validation requirements and outcomes require approved definitions.
• Blocking errors, warnings, exceptions, and informational findings must remain distinct.
• Conditional validation requires defined authority and visible conditions.
• Revalidation triggers must be governed.
• Validation must not be represented as Certifier Certification.

Publication Governance

• Publication authority and readiness requirements must be defined.
• Canonical URL and resolution patterns require approval.
• Restricted publication and withdrawal require documented authority.
• Corrections, supersession, revocation, and archival presentation must preserve history.
• Official human-readable and machine-readable forms must remain aligned.

Correction Governance

• Material errors must be correctable through an approved process.
• Correction authority and evidence must be preserved.
• Silent material correction is prohibited.
• Disputed corrections require escalation and visible status.
• Corrections must preserve prior values and affected versions.

Status and Lifecycle Governance

• Status and Lifecycle controlled values require approval.
• Permitted transitions must be defined.
• Transition authority, reason, date, and evidence must be preserved.
• Supersession, revocation, retirement, and archival actions require accountable decision records.
• Registry Status and Registry Lifecycle State must remain separate.

Exception Governance

Exceptions should be approved only when:

• the governing requirement is identified;
• the requesting need is documented;
• the approving authority is competent within scope;
• risk and impact are considered;
• scope and duration are limited;
• compensating controls are documented;
• material effects are visible in Validation and Publication;
• review or expiration is defined.

Conflict Resolution

When Registry materials or decisions conflict, Governance should:

1. identify the conflicting provisions or decisions;
2. determine the governing authority hierarchy;
3. identify current and historical versions;
4. apply the more specific requirement when appropriate;
5. apply clear supersession when documented;
6. pause material action when ambiguity creates risk;
7. issue an interim decision when necessary;
8. approve correction, amendment, or supersession;
9. publish the resolution;
10. preserve the prior conflict and decision history.

Appeal and Reconsideration

Registry Governance may permit reconsideration when:

• new evidence becomes available;
• authority was misidentified;
• a Rule or Policy was applied incorrectly;
• a material conflict was overlooked;
• a decision exceeded delegated authority;
• an exception or restriction is no longer necessary;
• the governing framework materially changed.

Reconsideration should preserve the original decision, new review, outcome, authority, and effective date.

Emergency Governance

Temporary emergency action may be appropriate when delay would create material:

• security risk;
• safety risk;
• privacy harm;
• rights violation;
• publication deception;
• integrity failure;
• systemic Registry damage.

Emergency action should preserve:

• emergency authority;
• action taken;
• reason;
• date and time;
• affected records and systems;
• temporary duration;
• required post-action review;
• final ratification, modification, or reversal.

Delegation

Delegation should identify:

• delegating authority;
• delegated role or process;
• scope;
• permitted decisions or actions;
• limitations;
• effective date;
• expiration or review date;
• oversight requirements;
• revocation conditions.

Governance Review

Governance materials should be reviewed when:

• Suite Standards or Methodology change;
• Registry architecture changes;
• new Record Types are introduced;
• exceptions recur;
• conflicts expose ambiguity;
• Validation identifies systemic defects;
• publication or source architecture changes;
• roles or authority boundaries change;
• legal, privacy, rights, safety, or security conditions change;
• scheduled review dates arrive.

Governance Validation

Before a governance action becomes effective, Registry should confirm:

• decision authority is valid;
• scope is within Registry authority;
• Suite alignment is preserved;
• conflicts have been reviewed;
• affected materials are identified;
• implementation requirements are clear;
• version and effective date are assigned;
• exceptions and conditions are documented;
• publication and historical preservation are planned;
• human-readable and machine-readable governance records agree when both exist.

Governance Transparency

Registry should publish or preserve appropriate visibility into:

• current Rules, Policies, and Procedures;
• current schema and profile versions;
• current controlled values;
• material governance decisions;
• effective dates;
• change summaries;
• exceptions that materially affect public interpretation;
• conflict resolutions;
• superseded governance materials;
• review and amendment history.

Relationship to Suite Governance

Registry Governance must remain aligned with Suite-level constitutional, standards, methodology, and interoperability decisions.

Registry may govern its implementation without redefining Suite-wide authority.

Relationship to Source Institutions

Registry Governance may determine how Registry represents a Source Record.

It may not determine the Source Institution's own substantive meaning, outcome, rights, source status, or source-domain versioning.

Relationship to Chronicle

Material governance decisions may become Chronicle events when they have institutional or historical significance.

Registry remains authoritative for the Governance Decision Record. Chronicle remains authoritative for its historical event record.

Relationship to Navigator

Navigator may coordinate governance review, approval, implementation, and recurring review as formal workflows.

Registry remains authoritative for governance decisions. Navigator remains authoritative for Navigator-created workflow definitions and execution records.

What Governance Does Not Establish

• It does not create Source Authority.
• It does not certify Source Records.
• It does not create attestations.
• It does not override Suite Standards or Methodology.
• It does not override lawful authority or rights holders.
• It does not permit undocumented exceptions.
• It does not eliminate institutional accountability through delegation.
• It does not permit silent change or historical erasure.
• It does not transfer authority from another Suite institution.
• It does not expand Registry beyond its constitutional scope.

Governance Principle

Registry Governance should ensure that every material Registry decision is authorized, documented, reviewable, versioned, implementable, transparent, and preserved as part of institutional history.