// Sovereign Trace Protocol · Certification Registry

Verify a
Certification

A badge is only as meaningful as what's behind it. Here's exactly what each AION badge means, who issued it, and how to verify it hasn't been misrepresented.

Ledger Entries · STP
11
Simulators Verified
3
Certified Orgs
0
Certified Auditors
0
Standard
FROZEN-2.0
Choose your path
Path 01
🔒
Seal Your Work
You are an individual — researcher, analyst, journalist, developer, or creator. You want to permanently seal a piece of work, a prediction, or an observation with a cryptographic triple-time stamp.
Get Started →
Path 02
🏛
Certify Your AI
You represent an organization deploying AI systems. You want formal certification that your infrastructure meets the FROZEN-2.0 standard — immutable failure capture, transparent remediation, honest epistemic record.
Start Certification →
Path 03
🔍
Verify a Badge
You have seen an AION badge in the wild — on a simulator, a service page, or a certification document. You want to know if it's legitimate and what it actually means.
Check a Badge →
Path 01 — Seal Your Work
1
Open the Seal Tool
Go to aionsystem.github.io/certify/seal/ — no account required, no server, zero dependencies. The SHA-256 seal is computed locally in your browser using SubtleCrypto.
2
Write Your Entry
Type exactly what you are sealing — a hypothesis before an experiment, a prediction before it resolves, a document you received, a creative work before submission. Write in present tense. Be precise. The content you write is the content that gets sealed.
3
Select Your Template
Choose from 14 template types: General Trace, Research Priority, Evidence Chain, Foresight Seal, AI Failure, Creative Priority, Clinical Record, Scope Anchor, and more. The template shapes how the ledger entry is categorized.
4
Generate Your Seal
The tool generates a SHA-256 hash of your content bound to the current Gregorian, Hebrew (full dehiyot), and 13 Moon Dreamspell timestamps simultaneously. Download the sealed JSON file. This is your permanent record.
5
Submit to the Public Ledger (Optional)
Open a GitHub Issue on the SOVEREIGN-TRACE-PROTOCOL repository ↗ using the correct template. Paste your sealed JSON as a comment. Sheldon K. Salmon manually confirms entries until the auto-seal workflow is funded. Your entry becomes permanently public and citable.
6
Done — Your Seal is Permanent
Whether or not you submit to the ledger, your local JSON is cryptographically sealed. The hash cannot be retroactively altered. Store your JSON file. The seal is the resolution. Open Seal Tool →
Path 02 — Certify Your AI Deployment
1
Review the Certification Methodology
Read CERTIFICATION.md ↗ in full. It defines exactly what the FROZEN-2.0 standard requires, what each tier covers, and what the Epistemic Debt Score measures. Certification is not installation — it is formal verification.
2
Choose Your Tier
Tier 1 ($2,500) — single event verification, 5–7 days, automated intake.
Tier 2 ($25,000/yr) — full implementation audit, annual badge license, AION Registry listing.
Tier 3 ($100k+/yr) — quarterly reviews, Epistemic Debt Statement, C-Suite engagement.
Tier 4 (negotiated) — NIST AI RMF, CMMC 2.0, EU AI Act, FAR/DFARS alignment.
3
File a Certification Issue
Open a GitHub Issue using the Audit Request template (Template 10) on the SOVEREIGN-TRACE-PROTOCOL repository ↗. Tier 1 and Tier 2 intake is automated — no call required. Tier 3 and 4 intakes are Monday/Tuesday only.
4
Audit Process
The audit covers: failure capture architecture, remediation documentation, epistemic record integrity, and Epistemic Debt Score calculation. The EDS formula is public. You will receive a Certification Report with ledger entry ID and SHA-256 seal before your badge is issued.
5
Badge Issuance
On certification completion, your organization is listed in the AION Registry with a verifiable ledger entry. You receive a licensed badge SVG and usage guidelines. The badge is non-transferable and linked to your specific ledger entry. Questions → aionsystem@outlook.com
Path 03 — Verify a Badge
1
Identify the Badge Type
Is it an STP Certified badge (amber hexagonal shield)? An AION Verified Simulator badge (gold octagonal seal)? Or an STP Certified Auditor badge (cyan hexagonal shield)? Each has different verification steps. See the badge reference section below.
2
Check for a Ledger Entry ID
Every legitimately issued badge is linked to a ledger entry in the SOVEREIGN-TRACE-PROTOCOL public ledger ↗. Request the entry ID from the badge holder. A badge with no corresponding ledger entry is not valid.
3
Use the Verifier Tool Below
Paste the ledger entry ID in the interactive verifier on this page. It will validate the format, generate the correct GitHub URL, and confirm what a valid entry for that ID should contain. Jump to Verifier →
4
For Simulator Badges
The simulator itself must contain: a Red Team tab documenting all issues found and resolved, source reference citation, red team pass count, and issue count in the footer. If any of these are missing, the badge has not been legitimately issued.
Interactive badge verifier
🔍 Verify a Ledger Entry
Paste a ledger entry ID (format: STP-[TEMPLATE]-[DATE]-[ID]) to validate its format and generate the direct GitHub verification link.
The verifier checks format validity locally — click the generated link to confirm the entry exists on GitHub.
Example valid IDs:
STP-GENERAL-TRACE-2026-03-09-000005  ·  STP-CREATIVE-PRIORITY-2026-03-10-000008  ·  STP-RESEARCH-PRIORITY-2026-03-14-U3N9CK
The three badge types
STPCERTIFIED STP Certified
Sovereign Trace Protocol · FROZEN-2.0
Issued to organizations whose AI deployment infrastructure has been formally audited against the FROZEN-2.0 standard.
View full certification methodology ↗
Immutable failure capture, transparent remediation, honest epistemic record. Four tiers — Basic through Defense Grade.
Issued to: Organizations
Palette: Amber & Black
Shape: Hexagonal shield
Tiers: Basic · Enterprise · Strategic · Defense
AION · VERIFIED· SIMULATOR ·SHELDON K. SALMON AION Verified Simulator
Simulation Certification · v1.0 · March 2026
Issued to simulation tools: physics verified, red-teamed, peer-reviewed. Issued by Sheldon K. Salmon under AION methodology.
View full certification methodology ↗
Every issue found is documented in the simulator's Red Team tab. The badge is not issued until that documentation is complete.
Issued to: Simulation tools
Palette: Black & Gold (#D4AF37)
Shape: Octagonal precision seal · 24 ticks
Seal: NON-TRANSFERABLE · SHA-256
STPCERTIFIEDAUDITOR STP Certified Auditor
Independent Auditor Credential
Issued to individuals authorized to file audit completions to the AION ledger under their own badge number.
View full certification methodology ↗
SHA-256 sealed at issuance. Non-transferable. Annual cap: 50 sealed audits. Renewable by reapplication only.
Issued to: Individual auditors
Palette: Cyan & Dark
Shape: Hexagonal shield variant
Term: 1 year · renewable by reapplication
Generate your own sovereign trace seal
🔒SOVEREIGN · TRACEFROZEN-2.0
// STP Browser Seal Tool · FROZEN-2.0 · SHA-256
Seal What Is True.
Permanently.
Every individual, researcher, organization, or analyst can generate a permanent cryptographic seal binding their content to three simultaneous calendar systems. No account required. No server. Zero dependencies. The seal is computed locally in your browser using SubtleCrypto — the same SHA-256 standard as the Python package.
📅 GregorianCivic time
🌑 HebrewFull dehiyot · FROZEN-2.0
🌀 Dreamspell13 Moon galactic
🔒 SHA-256SubtleCrypto · browser-native
🔒 Open the Seal Tool → Submit to Public Ledger ↗
WHAT YOU RECEIVE
✓ Sealed JSON download
✓ SHA-256 content hash
✓ Triple-time stamp
✓ Ledger ID (browser-generated)
✓ Direct GitHub Issue link
✓ Local VERIFY tool
✓ Browser ledger history
COST
Free
Always. No account.
How to verify a badge manually

For Simulator Badges

Every AION Verified Simulator badge is linked to a specific tool. To verify:

1. The badge should link to this page or to the CERTIFICATION.md file.
2. The simulator must contain a Red Team tab documenting all issues found and resolved.
3. The footer must name the source reference, red team pass count, and issue count.

If any of these are missing, the badge has not been legitimately issued.

View live example: Roller Coaster Simulator →

For STP Certification Badges

STP Certified badges are issued through the Sovereign Trace Protocol ledger on GitHub. To verify:

1. Request the organization's Certification Report — it contains a ledger entry ID.
2. Look up that ID in the AionSystem/SOVEREIGN-TRACE-PROTOCOL public ledger ↗.
3. Confirm the entry is signed by Sheldon K. Salmon with a triple-time seal.

A badge with no corresponding ledger entry is not valid. The AION Registry is the source of truth.

Full certification methodology ↗

What Certification Is Not

Certification is not a guarantee that AI systems will not fail. They will.

Certification is verification that the organization has built infrastructure that captures failures immutably, remediates them transparently, and maintains an honest epistemic record.

An organization with a certified deployment and a high failure rate is more trustworthy than an organization with no failures on record and no ledger. The ledger with failures is honest. The ledger with no failures may simply have no ledger.

STP Certification tiers
Tier 1
Basic Verification
$2,500
Single failure event verification. 5–7 business days. Automated intake — 24/7.
Tier 2
Enterprise
$25,000/yr
Full implementation audit. 30-day window. Annual badge license. AION Registry listing.
Tier 3
Strategic Retainer
$100,000+/yr
Quarterly reviews. Private filing window. Epistemic Debt Statement. C-Suite engagement.
Tier 4
Defense Grade
Negotiated
NIST AI RMF · CMMC 2.0 · EU AI Act · FAR/DFARS · Monthly reviews. DoD/Federal.

Engage Certification

File a certification issue on GitHub. Automated intake — no call required for Tier 1 and Tier 2.

File a Certification Issue ↗ Read Full Methodology