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.
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 should contain a Red Team tab documenting all issues found and resolved.
3. The footer should 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 →
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 entry 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, not the badge itself.
Full certification methodology ↗
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.
File a certification issue on GitHub. Automated intake — no call required for Tier 1 and Tier 2.
File a Certification Issue ↗ Read Full Methodology