Public-key verifiable
A KYE™ badge resolves to a Replay-Proof™ that anyone can re-check against KYE™'s published keys — no portal login, no “contact us to confirm”. The claim travels with its proof.
Governance · verifiable badges
Every badge in KYE Protocol™ is a replay-verifiable authority mark, backed by an Evidence Pack™. This hub names what a KYE™ badge is and routes you to the canonical surface for each of the 5 badges KYE™ issues. A vanity logo asks for trust. A KYE™ badge lets a CISO or auditor re-prove the claim from public keys alone — cutting badge-validation from a days-long procurement thread to one self-serve check.
You learn: The page's points, one at a time. You can: Step through them.
Step 1 of 3
KYE Protocol™
Public-key verifiable
A KYE™ badge resolves to a Replay-Proof™ that anyone can re-check against KYE™'s published keys — no portal login, no “contact us to confirm”. The claim travels with its proof.
Step 2 of 3
KYE Protocol™
Backed by evidence
Each badge points to an Evidence Pack™ — the sealed, WORM-retained JSON record of what was assessed and decided, signed with a JWS the badge resolves to. The badge is a pointer to that record.
Step 3 of 3
KYE Protocol™
Revocable, never stale
A KYE™ badge renders only while the holder stays conformant and within their disclosure boundary. If conformance lapses, the badge is revoked — the picture can never outlive the proof.
Every mark KYE™ issues
From the L0 self-declaration up to KYE™ Certified™ — every conformance and authority mark KYE™ issues, one shield each. Each badge resolves to a Replay-Proof™ backed by an Evidence Pack™, so a CISO or auditor re-proves it from public keys alone.
The canonical badge shields render here. See the badge ladder →
What a KYE™ badge is
A vanity logo is a picture: it says “trust us” and nothing more. A KYE™ badge is the opposite — it is a claim of authority or conformance that carries its own proof. Behind every badge sits an Evidence Pack™ and a Replay-Proof™ derivable from public keys, so the badge is not something you take on faith. You, your team, or an independent auditor can re-verify it without ever contacting KYE™.
A KYE™ badge resolves to a Replay-Proof™ that anyone can re-check against KYE™'s published keys — no portal login, no “contact us to confirm”. The claim travels with its proof.
Each badge points to an Evidence Pack™ — the sealed, WORM-retained JSON record of what was assessed and decided, signed with a JWS the badge resolves to. The badge is a pointer to that record.
A KYE™ badge renders only while the holder stays conformant and within their disclosure boundary. If conformance lapses, the badge is revoked — the picture can never outlive the proof.
The badges KYE™ issues
KYE™ issues a small, canonical set of badges — one for each kind of authority or conformance claim. Each badge has exactly one home page where it is defined and earned; this hub only routes you there, so the definition lives in one place and never drifts. Pick the claim you need to make or check.
The five-tier conformance ladder that lets a builder or partner display a KYE™ Badge™ once they pass certification. Earn or verify it on the certification page.
Per-program completion and competency badges for the KYE™ certificate programs — the training-and-assessment route to a displayable mark.
The badge that surfaces an executable Assurance Card — an auditor- and CISO-facing mark whose claims resolve to live evidence rather than a static system card.
The licensed, revocable badge a Sector Pack Foundry™ partner displays on a certified expert pack — governed by its own badge state machine.
Each of the nine KYE™ partner types carries a licensed, revocable badge that renders only while the partner stays conformant and within the disclosure boundary.
How verification works
Because every badge is anchored to a Replay-Proof™, verifying one is mechanical. The path is always the same: follow the badge to its Evidence Pack™, then re-derive the proof from KYE™'s public keys. A badge that fails to re-verify is, by definition, void.