Certifier · Operational Certification

Satoshium Certifier

Satoshium Certifier is the Operational Certification institution of the Satoshium Suite. It applies applicable Suite Standards and certification-specific Suite Methodology to evidence-supported certification while preserving the authority of every other Suite institution.

Certifier evaluates certification subjects by organizing governed evidence, applying applicable standards and certification methodology, reaching certification determinations, and preserving the resulting Certification Package. Generated reports, receipts, certified records, machine-readable records, and Suite-ready references remain Certifier artifacts derived from that Package.

Institutional Position

Certifier is the Suite's Operational Certification institution. Its canonical operational object is the Certification Package. Certifier applies applicable Suite Standards and certification-specific Suite Methodology through its own evidence architecture, workflow, Certification Classes, schema profiles, generated outputs, and interoperability practices.

Suite Standards
↓
Suite Methodology
↓
Satoshium Certifier
↓
Certification Package
↓
SCPR · SCR · SCRD
Certifier owns the certification action, Certification Package, certification determination, Certification Class, certification lifecycle, and generated certification artifacts.
Referenced subject systems and downstream Suite institutions retain authority over their own objects.

Authority follows the governed subject.
Reference does not transfer authority.

Institutional Foundation

These pages identify the standards, certification methodology, vocabulary, institutional governance, and related trust guidance that constrain or support Certifier activity.

Foundation

Standards

Defines the Suite expectations, evidence criteria, requirements, and determination principles that Certifier applies during operational certification.

Open Standards → Suite Standards →
Foundation

Methodology

Defines certification-specific implementation through which Certifier organizes evidence, evaluates a subject, reaches a certification determination, and produces certification artifacts.

Open Methodology → Suite Methodology →
Foundation

Governance

Defines Certifier's institutional rules, authority boundaries, operating expectations, and long-term controls. Constitutional Suite changes remain governed by Suite Governance.

Open Governance →
Foundation

Definitions

Establishes Certifier's canonical vocabulary, including Certification Package, SCPR, SCR, SCRD, Certification Class, Evidence, SREG, and related Suite references.

Open Definitions →
Public Guidance

FAQ

Answers common questions about Certifier's purpose, Certification Package architecture, Evidence, Classes, generated artifacts, authority boundaries, and Suite interoperability.

Open FAQ →
Trust

Trust

Explains how Certifier creates reviewable confidence through evidence, transparent reasoning, preserved records, generated artifacts, and clear authority boundaries.

Open Trust →
Trust Architecture

Trust Model

Explains Certifier's evidence-based confidence framework and the relationship among evidence, assessment, limitations, reviewability, and certification outcomes without creating Attestor Trust Statements or generalized Suite trust authority.

Open Trust Model →

Governance Boundary

Certifier governs certification operations within its settled institutional authority. Routine and institution-owned material certification changes remain with Certifier, subject to Suite coherence review where applicable. Changes to institutional role, canonical ownership, Suite membership, authority allocation, or constitutional position require Suite Governance / Architecture Reconciliation.

CHANGE WITHIN AUTHORITY → may remain institutional.
CHANGE TO AUTHORITY → requires Suite Governance.
CERTIFICATION DETERMINATION ≠ GOVERNANCE DECISION.
CERTIFIER REVIEW ≠ SUITE GOVERNANCE REVIEW.

Certification Methodology Boundary

The Suite Methodology pages used by Certifier are certification-specific. They do not become universal Suite lifecycle, workflow, evidence, evaluation, decision, or schema rules.

Certification Lifecycle ≠ universal Suite lifecycle.
Certification Workflow ≠ universal Suite workflow.
Certification Evaluation Criteria ≠ universal Suite evaluation criteria.
Certification Evidence Requirements ≠ universal Suite evidence rules.
Certification Logic ≠ Suite Governance decision logic.
Certification Schema ≠ Certification Package.

Certification Architecture

These pages define how Certifier receives a subject, organizes evidence, classifies review depth, executes its workflow, and structures machine-readable output.

Operational Directory

Certified Items

Provides the public directory of subjects that have completed or are undergoing certification review and resolves completed certifications to their canonical packages.

View Certified Items →
Review Foundation

Evidence

Defines the factual materials used to support certification scope, evaluation, findings, limitations, reports, receipts, certified records, and later verification.

Open Evidence →
Repeatable Process

Workflow

Defines the certification-domain operational path from Certification Subject through Evidence, evaluation, certification determination, Certification Package, and generated artifacts. Downstream Suite interactions are independently governed.

Open Workflow →
Classification

Classes

Defines Certification Classes and the intent, review depth, and confidence posture communicated by each class under the governing Suite framework.

Open Classes →
Machine-Readable Structure

Schema

Defines structured representation requirements used by Certifier outputs, including Certification Packages, SCRD JSON, Evidence Inventories, and Suite reference structures. Schema ≠ canonical object.

Open Schema →

Certification Records and Public Outputs

These pages expose the records generated from Certifier's canonical Certification Package for detailed review, public verification, cataloging, and downstream use.

Generated Output

Reports

Preserves the detailed certification review record, including scope, Evidence, findings, limitations, governing Standards, Methodology references, and decision.

Open Reports →
Public Verification

Receipts

Provides concise public records documenting that certification occurred, what was certified, where supporting artifacts can be found, and how verification can proceed.

Open Receipts →
Catalog Reference

Registry

Explains how Certifier outputs may be referenced by Registry after certification while Satoshium Registry independently creates, owns, and governs the resulting SREG.

Open Registry →
Integrity Preservation

Anchor

Connects Certifier-produced artifacts to Satoshium Anchor Integrity References without transferring certification authority. Anchor preserves integrity context for a defined representation while Certifier remains authoritative for the Certification Package and generated certification records.

SCRD-SC-CERT-2026-0001
↓ references_source
ANCH-2026-0001
Open Anchor → Open ANCH-2026-0001 →
Discovery Signal

Beacon

Connects the canonical Certification Package to Satoshium Beacon discovery without transferring certification authority. Beacon has published BEAC-2026-0001 as a Discovery Signal identifying the active Operational certification represented by SC-CERT-2026-0001.

SC-CERT-2026-0001
↓ authoritative source for discovery
BEAC-2026-0001
Open Beacon →
The same certification context later participated in Satoshium Attestor's first controlled production operation. ATT-2026-0001 and TRST-2026-0001 are Active · Published · V1.0. Attestor owns the Attestation, Rule-Constrained Evaluation, Evaluation Outcome, and bounded Trust Statement; Certifier retains authority for the certification decision.
Open BEAC-2026-0001 → Open ATT-2026-0001 → Open TRST-2026-0001 →
Attestor Integration

Attestations

Explains how Certifier records can serve as eligible governed inputs to Satoshium Attestor without transferring certification authority. The first production operation produced ATT-2026-0001 and the bounded Trust Statement TRST-2026-0001.

SC-CERT-2026-0001 + eligible governed Suite-source inputs
↓
ATT-2026-0001
↓ Rule-Constrained Evaluation · supported
TRST-2026-0001
Open Certifier Attestations Guidance → Open ATT-2026-0001 → Open TRST-2026-0001 →

Suite Integration and Operations

These pages define how Certifier connects with the wider Satoshium Suite and communicate the current operational state of the institution.

Suite Connection

Interoperability

Defines how Certifier exchanges governed references with Atlas, Registry, Chronicle, Anchor, Beacon, Attestor, and Navigator while preserving each institution's independent authority. Interoperability may constrain exchange; it does not reallocate authority.

Open Interoperability →
Operations

Status

Summarizes Certifier's current operational posture, published certification activity, artifact readiness, lifecycle condition, and Suite integration state.

Open Status →

Operational Certifier Structure

Certifier is established as the Suite’s operational implementation for evidence-based certification. Its operational structure centers on the Certification Package as Certifier's canonical operational object, from which reports, receipts, certified records, machine-readable records, and Suite references are generated. Certifier exists to transform evidence into reviewable, repeatable, and independently verifiable certification records for the Satoshium Suite.

The inaugural operational certification, SC-CERT-2026-0001, established the Atlas Jurisdiction Record — El Salvador as Certifier's first production subject and proved the end-to-end certification workflow from evidence review through canonical Certification Package and downstream Suite references.
The SCRD JSON record SCRD-SC-CERT-2026-0001 also became the Source Artifact for ANCH-2026-0001, the first published Satoshium Anchor Integrity Reference. This demonstrates the Suite boundary in production: Certifier owns the certification record; Anchor owns the Integrity Reference that preserves integrity context for its defined representation.
The canonical Certification Package SC-CERT-2026-0001 subsequently became the primary authoritative source for BEAC-2026-0001, Satoshium Beacon's first published production Discovery Signal. Beacon owns the discovery representation; Certifier continues to own the certification decision, class, lifecycle, and status. Reference does not transfer authority.
Open BEAC-2026-0001 →

Certifier Workflow

Certifier follows a repeatable certification-domain workflow in which a certification subject is reviewed under applicable Standards and certification Methodology, governed evidence is organized, a certification determination is reached, and the canonical Certification Package and generated certification artifacts are produced.

Certification Subject
↓
Evidence
↓
Certification Evaluation & Determination
↓
Certification Package
↓
SCPR · SCR · SCRD HTML / JSON
Downstream Suite interactions are independently governed and conditional. Registry may catalog. Chronicle may preserve qualifying historical memory. Anchor may preserve integrity context through its own Integrity References. Beacon may publish Discovery Signals. Attestor may consume eligible governed inputs and produce bounded Trust Statements. Navigator may define or orchestrate workflows.

Conceptual Sequence ≠ Mandatory Pipeline.
Exercised Lineage ≠ Mandatory Architecture.
Reference does not transfer authority.

Certification begins with evidence; authority remains with the institution that governs the result.