The Gap Finder — where KYE Protocol™ is strong, and where it is an honest gap

This page shows you the truth in one view. 32 jurisdictions are covered. 3 sit dark, and you can request them. The numbers come straight from the canonical coverage registries. We never inflate coverage to 100%.

A gap is a feature here, not a flaw. You see exactly what KYE Protocol™ governs today. You see what it does not. Then you ask for the gap that matters to you in one click. Your procurement starts with fewer blind spots and a faster yes or no.

3jurisdictions to request
12frameworks out of scope
32jurisdictions covered
456requirement groups enforced

Request the gap you need See the Coverage Atlas

Jurisdiction gaps

These jurisdictions are not yet covered. Each one is requestable. The full coverage map lives on the Coverage Atlas.

ItemStatusAction
BrazilUncovered — request itRequest this →
Hong KongUncovered — request itRequest this →
IndiaPending mappingRequest this →

Framework and regime gaps

These frameworks sit out of scope today. KYE Protocol™ is an evidence layer, not a replacement for every control. The full tri-state map lives on the Regulatory Coverage page.

ItemStatusAction
CCPA/CPRAOut of scopeRequest this →
China PIPLOut of scopeRequest this →
ECB AI Supervisory ExpectationsOut of scopeRequest this →
Frontier Bio-Safeguard EvalOut of scopeRequest this →
FSB Sound PracticesOut of scopeRequest this →
IMDA MGF (Agentic AI)Out of scopeRequest this →
MAS AIRG (consultation)Out of scopeRequest this →
OECD AI PrinciplesOut of scopeRequest this →
Singapore PDPAOut of scopeRequest this →
Singapore PS ActOut of scopeRequest this →
Singapore SFAOut of scopeRequest this →
UK IDTA / Data BridgeOut of scopeRequest this →

One honest number

KYE Protocol™ enforces 456 requirement groups at runtime. It has 244 more designed and in build. It marks 153 as out of scope. That last number is the honest part. We show it on purpose. Read the Regulatory Coverage page for the full breakdown.

Coverage Atlas → Offering inventory