Regulatory
EU AI Act, DORA, PSD3, NIS2, FedRAMP and 9 more frameworks ask for evidence the protocol already produces. Certification is the bridge.
Certification program
Five tiers, 133 black-box fixtures, 289 control mappings across 249 frameworks. Every claim at every tier is a signed artefact a regulator or auditor can verify offline. The protocol is Apache 2.0; certification is the only commercial layer.
You learn: What happens at each step. You can: Step through it.
Step 1 of 4
KYE Protocol™
M1 L1 / L2 self-tiers
Re-run fixtures whenever your integration changes; resubmit signed report. No fixed cadence.
Step 2 of 4
KYE Protocol™
M2 L3 KYE™ Conformant™
Notify the program on any breaking change. Program spot-checks 10% of L3 partners per quarter. Listing flagged if checks fail.
Step 3 of 4
KYE Protocol™
M3 L4 KYE™ Certified™
Annual revalidation by your audit firm. Listing carries the last-revalidation date. Lapsed certifications drop to L3 status until refreshed.
Step 4 of 4
KYE Protocol™
M4 Spec version bumps
Major-version bumps (v1 → v2) require re-certification within 12 months. Minor bumps are additive; no re-cert.
Why certify
EU AI Act, DORA, PSD3, NIS2, FedRAMP and 9 more frameworks ask for evidence the protocol already produces. Certification is the bridge.
Regulated buyers' procurement teams ask: "show us a signed conformance report you didn't write yourself." L3 / L4 are exactly that.
Public-key-verifiable claims defeat the "trust us" failure mode. Anyone can replay a certification artefact end-to-end.
KYE™ Academy™ authority tracks
The KYE™ Academy™ certifies the people who make AI agents governable. Each track targets one role on the path from a deployed agent to a replay-verifiable authority claim, and each ends at a credential the capstone exam recognises. Pick the track that matches what you ship.
Ship skills and agents bound to a Skill Authority Manifest — purpose, tool scope, finality, evidence, revocation — so the agent's authority is declared, not assumed.
Map agent authority to controls and verify a signed Evidence Pack™ offline with public keys alone. The audit becomes a replay, not a meeting.
Productise your governance expertise into a KYE-Powered Pack™ through the Sector Pack Foundry™ — your framework, the protocol's authority spine.
Deliver multi-week authority implementations with the partner playbook and earn a registry-listed implementer badge clients can verify.
The capstone credential — proof you can take an agent from deployment to a defensible, replay-verifiable authority claim end-to-end.
The ladder
Within each tier, an implementation can carry capability-scoped marks. Each badge attests to a defined slice of the conformance pack — not the whole thing — so an implementation can grow its claims one capability at a time.
KYE™ Core Conformant™ Core authority, delegation, scope, state, audit, decision-code conformance against the Core fixture set. Program in development
KYE™ Authority Conformant™ Authority Finality™ binding — actor · on-behalf-of · capability · scope · state · audit — tested end-to-end. Program in development
KYE™ Capability Conformant™ Capability registry, grant, invocation, quarantine and cascade fixtures all pass. Program in development
KYE™ Evidence Conformant™ Evidence Pack™ generation, signing, replay and OSCAL projection conformance. Program in development
Capability-scoped badges are still in development. They become live once the public conformance program opens registration and the per-capability fixture pack is frozen. Until then, only the five tiers above are issued. Capability badges, when issued, will be versioned, time-limited, and link to a public verification record at /badges/{badge_id}/verify showing implementation, profile version, test-suite version, issued / expires dates, and revocation status.
These are the canonical badge templates. A per-customer badge is stamped from one of these shields plus a signed Evidence Pack™ record, then served from registry.kye.dev/badges/{badge_id}.svg with a public verification link. The shields below are the templates those instances render from — one per level in the ladder.
Self-asserted — free, run the open pack, no program review.
Program-verified conformance (L3) — the umbrella mark plus capability- and profile-scoped variants.
Certified (L4) — third-party-audited, listed in the public registry.
Embed your earned badge once issued (replace the level + your verification URL):
<a href="https://registry.kye.dev/badges/{badge_id}/verify">
<img src="https://registry.kye.dev/badges/{badge_id}.svg" alt="KYE™ Conformant" height="24" />
</a>
135 conformance fixtures
The conformance pack is 133 black-box fixtures grouped into seven families. Each fixture takes a signed input, expects a deterministic output, and is replayable offline using the published key set. No fixture depends on hosted infrastructure; conformance is reproducible on a laptop.
/v1/runtime/authorize contract, decision codes, constraint emission, latency envelope.289 control mappings
Conformance projects through the KYE™ Compliance Mapping Rail™ into 266 named controls across 249 frameworks. The same evidence pack satisfies multiple frameworks; you do not run separate audits for the same artefact.
Approved audit firms
L4 audits are run by independent firms approved by the KYE Protocol™ program. Approval criteria: SOC 2 / ISO 27001 / EU AI Act-notified-body credentials, prior regulated-sector audit experience, and a signed audit-firm agreement that aligns scope, evidence handling, and report format. Audit firms do not pay to be listed; partners and end customers select from the published list.
The approved-audit-firm roster opens with the v1.1 release. Firms interested in joining should contact the program via the link below.
Maintaining certification
Start
For most teams, the path is L1 first (run fixtures, find gaps), then L2 (sign + submit), then L3 (program review). L4 is the destination, not the starting point.
Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.
Canonical KYE™ surfaces referenced on this page: KYE Protocol™.