Frequently Asked Questions

Satoshium Certifier is the operational certification implementation of the Satoshium Suite. It reviews defined Certification Subjects against applicable Suite Standards and Suite Methodology, evaluates supporting Evidence, reaches certification determinations, and preserves the result through a canonical Certification Package.

Certifier is authoritative for its own certification actions, Certification Packages, Certification Classes, lifecycle, and generated certification artifacts.

Its purpose is not merely to record information, but to preserve how a subject was reviewed, what evidence was considered, what determination was reached, and how that result can be independently reviewed later.

Certifier supports certification of defined digital subjects such as:

• Pages
• Reports
• Services
• Workflows
• Datasets
• Tools

Additional subject categories may be introduced through documented Certifier and Suite governance.

A Certification Subject is the defined item, system, record, workflow, service, dataset, tool, or other governed subject being reviewed.

Examples include:

• A webpage
• A published report
• A software tool
• A workflow
• A dataset
• A service

The Certification Subject defines what is inside the certification boundary. The term should not be confused with a downstream conformance target or other institutional object.

Certification is the process of reviewing a target against a documented standard, evaluating supporting evidence, and recording a determination.

Certification is intended to create a transparent and reviewable record of that process.

The Certification Package is Certifier's canonical operational record for a certification.

It preserves the Certification Subject, certification boundary, governing Standards, applied Methodology, Evidence Inventory, evaluation, determination, Certification Class, lifecycle information, and generated artifact relationships.

Reports, receipts, certified records, and downstream Suite references derive from the Certification Package.

Reference does not transfer authority: the subject system retains authority over the subject it owns.

No.

Certification documents a review performed according to a defined standard and available evidence at a specific point in time.

Certification does not guarantee:

• Accuracy
• Completeness
• Future performance
• Regulatory compliance
• Legal validity

Certification records document review outcomes rather than absolute truth.

Certifier uses documented Certification Standards.

Standards define:

• Scope
• Requirements
• Evaluation criteria
• Evidence requirements
• Determination guidance

All certification activities should be traceable to an applicable standard.

Certifier may use evidence appropriate to the applicable Standard and Certification Subject, including:

• Canonical records
• Reports
• Structured data
• URLs and durable references
• Screenshots or captures
• Hashes and integrity metadata
• Notes and review observations
• Supporting institutional artifacts

Evidence requirements are governed by the applicable Suite Standards and Certifier methodology rather than by a single universal evidence list.

Certification Classes communicate the level of certification granted.

Version 1.0 defines:

The target exists and has been documented.

The target exists, is documented, and demonstrates operation.

The target has been reviewed against an established standard and is supported by documented evidence.

These concepts describe different parts of a certification record.

Certification Outcome records the determination reached by Certifier for the defined review.

Example:

Certified

Certification Status communicates the current certification-domain condition of that issued certification.

Example:

Issued · Active

Lifecycle State describes where the certification record exists in its broader institutional lifecycle.

These concepts should not be collapsed into one generic status field.

A Certification Report is the detailed review record supporting a certification event.

Reports document:

• Evidence reviewed
• Findings
• Methodology
• Determinations
• Conditions
• Recommendations

Reports provide the reasoning behind certification outcomes.

Certifier uses several generated artifact forms derived from the canonical Certification Package:

SCPR
Certification Process Report

SCR
Certification Receipt

SCRD
Satoshium Certified Record

The SCPR preserves the detailed review process and reasoning.

The SCR provides a concise public-facing certification receipt.

The SCRD provides the certified-record representation in human-readable and, where published, machine-readable form.

These artifacts must remain traceable to and materially consistent with the canonical Certification Package.

A Certification Receipt is a concise public-facing summary of a certification event.

Receipts provide proof that certification occurred while referencing supporting reports and records.

A simple way to think about it:

Evidence
     ↓
Report
     ↓
Receipt

Evidence supports the review.

The Report explains the review.

The Receipt summarizes the review.

Hashes support integrity verification.

They help answer a simple question:

Is this the same artifact that was originally reviewed?

Hashes do not prove correctness.

They help verify consistency.

Notes preserve observations, assumptions, limitations, clarifications, and reviewer reasoning.

They help explain how findings and determinations were reached.

Notes preserve context that might otherwise be lost.

Not necessarily.

Version 1.0 supports:

• Human review
• AI-assisted review
• Human-AI-assisted review
• Automated review

The applicable standard determines the review requirements.

AI may assist certification activities.

Examples include:

• Evidence collection
• Analysis
• Documentation
• Review support

However, AI-generated observations should not automatically be treated as authoritative conclusions.

Certification should remain transparent and reviewable.

Satoshium Registry is the Suite institution responsible for canonical registration, durable SREG identity, classification, provenance, validation, publication, and public discovery of registered institutional records.

Certifier creates and owns the certification record.

Registry may create a SREG that catalogs that Certification Package while Certifier retains certification authority.

Satoshium Chronicle is the Suite institution responsible for preserving qualifying historical Occurrences through canonical Chronicle Entries.

A qualifying certification Occurrence may be preserved by Chronicle, but Chronicle does not own or re-adjudicate the certification action. Certifier remains authoritative for the Certification Package and determination.

Satoshium Anchor is the Operational Suite institution responsible for governed Integrity References and verification of defined representations.

In the first production relationship, ANCH-2026-0001 preserves integrity context for the complete canonical SCRD JSON representation SCRD-SC-CERT-2026-0001. That boundary does not extend to the entire Certification Package or linked artifacts unless separately anchored.

Anchor owns its Integrity Reference. Certifier retains authority over the certification record and decision.

Satoshium Beacon is the Operational Suite institution responsible for governed Discovery Signals and discovery metadata.

BEAC-2026-0001 is Beacon's first published production Discovery Signal. It directly observed SC-CERT-2026-0001 as its primary authoritative source.

Beacon discovery makes a governed object easier to discover without becoming certification authority. The September 13, 2026 observation does not by itself establish that the source remained unchanged through later dates.

Beacon owns the Discovery Signal. Certifier retains authority for the certification decision, class, lifecycle, and status.

Satoshium Attestor is the Operational Suite institution that creates governed Attestations and produces governed, attributable, bounded Trust Statements through Rule-Constrained Evaluation of eligible governed inputs.

Its first production operation created ATT-2026-0001 and TRST-2026-0001. Both are Active · Published · V1.0, and the production Evaluation Outcome was supported.

TRST-2026-0001 is derived-from ATT-2026-0001. The Attestor objects also preserve governed references to the relevant Certifier, Registry, Chronicle, Anchor, and Beacon objects.

Attestor does not independently re-certify Certifier's decision, establish the substantive truth of the underlying Atlas intelligence, extend Anchor integrity beyond its defined representation, or make a generalized determination of trustworthiness.

Attestation and evaluation do not replace Certifier's certification authority.

At a high level:

Atlas
   ↓
Certifier
   ↓
Registry
   ↓
Chronicle
   ↓
Anchor
   ↓
Beacon
   ↓
Attestor
   ↓
Navigator

Atlas creates information.

Certifier reviews information.

Registry catalogs authoritative records through SREGs.

Chronicle preserves qualifying historical memory.

Anchor preserves integrity references.

Beacon publishes governed Discovery Signals and discovery metadata.

Attestor creates governed Attestations and produces bounded Trust Statements through Rule-Constrained Evaluation.

Navigator provides workflow definition and orchestration across Suite activity.

Together they form a connected Suite while preserving independent institutional authority.

A production example now exists:

Atlas Jurisdiction Record — El Salvador
        ↓
SC-CERT-2026-0001
        ├── SREG-2026-0001
        ├── CHR-2026-0001
        ├── ANCH-2026-0001
        ├── BEAC-2026-0001
        ├── ATT-2026-0001
        └── TRST-2026-0001

These are institution-owned objects connected by governed relationships. They are not Versions of one another and do not share authority. TRST-2026-0001 is derived-from ATT-2026-0001.

Connection ≠ Identity. Reference ≠ Derivation. Reference ≠ Support. Reference does not transfer authority.

Yes.

Certifier is released under the MIT License unless otherwise specified.

See:

LICENSE

for the governing license terms.

The long-term vision of Certifier is to create a transparent and durable framework for documenting review, evidence, certification, and trust across digital systems.

The objective is not simply to issue certifications.

The objective is to create certification records that remain understandable, reviewable, and useful years into the future.

New contributors are encouraged to begin with:

README.md
docs/certifier-overview.md
docs/certification-philosophy.md
docs/workflow-diagram.md

These documents provide the best introduction to the Certifier framework.

Trust should not depend upon memory.

Trust should not depend upon reputation.

Trust should be supported by standards, evidence, and reviewable records.

Satoshium Certifier exists to help preserve those records.