Standards
Defines the Suite expectations, evidence criteria, requirements, and determination principles that Certifier applies during operational certification.
Open Standards → Suite Standards →Certifier · Operational Implementation
Satoshium Certifier
Satoshium Certifier is the operational certification implementation of the Satoshium Suite. It applies Suite Standards and Suite Methodology to review digital artifacts, workflows, services, reports, datasets, tools, and records through evidence-supported certification.
Certifier evaluates certification subjects by organizing evidence, applying Suite Standards and Suite Methodology, reaching certification decisions, and preserving the resulting Certification Package. Reports, receipts, certified records, machine-readable records, and Suite-ready references are generated from that Package.
Institutional Position
Certifier operates beneath Suite Standards and Suite Methodology and serves as the Suite's operational certification implementation. It applies those shared foundations through its own Evidence architecture, Workflow, Certification Classes, schema, Certification Package, generated outputs, trust framework, and interoperability rules.
Suite Standards
↓
Suite Methodology
↓
Satoshium Certifier
↓
Certification Package
↓
SCPR · SCR · SCRD
↓
Suite Methodology
↓
Satoshium Certifier
↓
Certification Package
↓
SCPR · SCR · SCRD
Certifier owns the certification action, Certification Package, determination,
Certification Class, lifecycle, and generated certification artifacts.
Referenced subject systems retain authority over their own objects.
Institutional Foundation
These pages define the Suite-governed standards, methodology, vocabulary, governance, and trust principles beneath every Certifier action.
Methodology
Defines the repeatable Suite process through which Certifier organizes evidence, evaluates a subject, reaches a decision, and produces certification artifacts.
Open Methodology → Suite Methodology →Governance
Defines the institutional rules, authority boundaries, operating expectations, and long-term controls that guide Certifier activity.
Open Governance →Definitions
Establishes Certifier's canonical vocabulary, including Certification Package, SCPR, SCR, SCRD, Certification Class, Evidence, SREG, and related Suite references.
Open Definitions →FAQ
Answers common questions about Certifier's purpose, Certification Package architecture, Evidence, Classes, generated artifacts, authority boundaries, and Suite interoperability.
Open FAQ →Trust
Explains how Certifier creates reviewable confidence through evidence, transparent reasoning, preserved records, generated artifacts, and clear authority boundaries.
Open Trust →Trust Model
Defines Certifier's structured trust framework and the relationship among evidence, assessment, confidence posture, limitations, reviewability, and certification outcomes.
Open Trust Model →Certification Architecture
These pages define how Certifier receives a subject, organizes evidence, classifies review depth, executes its workflow, and structures machine-readable output.
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 →Evidence
Defines the factual materials used to support certification scope, evaluation, findings, limitations, reports, receipts, certified records, and later verification.
Open Evidence →Workflow
Defines the operational path from Certification Subject through Evidence, Certification Package, evaluation, decision, generated artifacts, and Suite references.
Open Workflow →Classes
Defines Certification Classes and the intent, review depth, and confidence posture communicated by each class under the governing Suite framework.
Open Classes →Schema
Defines the structured formats used by Certifier outputs, including Certification Packages, SCRD JSON, Evidence Inventories, and Suite reference structures.
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.
Reports
Preserves the detailed certification review record, including scope, Evidence, findings, limitations, governing Standards, Methodology references, and decision.
Open Reports →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 →Registry
Explains how Certifier produces Registry-ready references after certification while Satoshium Registry independently owns and governs the resulting SREG.
Open Registry →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 →
↓ references_source
ANCH-2026-0001
Attestations
Explains how certification records, receipts, evidence references, hashes, Registry entries, and later trust statements can support independent attestation.
Open Attestations →Suite Integration and Operations
These pages define how Certifier connects with the wider Satoshium Suite and communicate the current operational state of the institution.
Interoperability
Defines how Certifier exchanges references with Atlas, Registry, Chronicle, Anchor, Beacon, Attestor, and Navigator while preserving each system's independent authority.
Open Interoperability →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 reference 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.
Certifier Workflow
Certifier follows a repeatable workflow in which a certification subject is reviewed against Suite Standards and Suite Methodology, evidence is organized, a canonical Certification Package is created, and generated certification artifacts are produced for review, public verification, cataloging, preservation, integrity protection, discovery, and future attestation across the Satoshium Suite.
Certification Subject
↓
Evidence
↓
Certification Package
↓
Evaluation & Decision
↓
SCPR · SCR · SCRD HTML / JSON
↓
Registry · Chronicle · Anchor · Beacon · Attestor · Navigator
↓
Evidence
↓
Certification Package
↓
Evaluation & Decision
↓
SCPR · SCR · SCRD HTML / JSON
↓
Registry · Chronicle · Anchor · Beacon · Attestor · Navigator
Standards define expectations. Methodology defines the process. Certifier executes the certification workflow. Registry catalogs it. Chronicle preserves qualifying historical memory. Anchor preserves integrity through its own Integrity References. Beacon publishes discovery. Attestor supports verification. Navigator orchestrates use. Reference does not transfer authority.