Cross-map your vocabulary against the canonical spine
Bring your own vocabulary, taxonomy, glossary or control framework. KYE Protocol™ maps every one of your terms onto the canonical framework, jurisdiction and taxonomy spine — 249 frameworks — and returns a per-term verdict, an alignment score and a gap list in seconds. You see exactly where you line up and where you do not, cutting a manual crosswalk from days to minutes — and the free report runs entirely in your browser, so nothing you paste ever leaves it.
Run the free cross-map
Paste your terms below — as JSON ([{"term":"…","definition":"…"}]), as CSV (term, definition),
or as a plain glossary (term: definition, one per line). Pick the format, press run, and read
the report. This is the free tier: the BYO Cross-Map™ runs
client-side, so your terms are never uploaded.
Report
Paste your terms and press Run cross-map to see the alignment table, gap list and score.
Honesty bar. KYE Protocol™ maps and flags only. Every verdict reports how your term relates to the canonical KYE™ spine — aligned, divergent, gap or conflict. KYE™ never asserts whether your definition is correct, and it never resolves a conflict for you. The mapping is deterministic and replay-proof: the same terms always yield the same report.
What each verdict means
Four verdicts, drawn from the canonical cross-map dictionary. They tell you where to look, not what to think — a regulator reads a flag the same way you do.
- Aligned. A canonical spine term matches yours at or above the similarity threshold. Example: your Human oversight maps to EU AI Act™ Article 14 human oversight.
- Divergent. A related-but-not-identical spine term matched (related-not-identical). KYE™ flags it for your review; it does not merge the two.
- Gap. No spine term matched. A concept the canonical spine does not cover — surfaced for the paid full mapping, never called a deficiency.
- Conflict. Your term collides with a spine term under a meaning you marked as not-equivalent. KYE™ flags the collision and leaves the resolution to you.
The spine itself is no black box: it is compiled from the 249 frameworks in the coverage registry — EU AI Act™, ISO/IEC 42001, NIST AI RMF, DORA, MAS and the rest — plus the KYE™ component taxonomy. See how it is assembled on the taxonomy page and which regimes are covered on the regulatory coverage page.
From free report to sealed mapping
The free report is the whole report — real verdicts, a real score, a real gap list, computed in your browser. When you are ready to depend on it, a governed pilot turns the snapshot into a maintained asset.
- Full mapping. Your complete vocabulary cross-mapped against the deep per-requirement registry, with every match reviewed.
- Sealed report. Each cross-map sealed into an Evidence Pack™ your auditors can replay-verify from public keys alone.
- Ongoing sync. When a framework moves, your mapping is re-run and the delta flagged — so your crosswalk never silently goes stale.
Talk to us about a governed pilot
Boundary: KYE Protocol™ governs how your terms relate to the canonical spine and seals the evidence — it does not rewrite your vocabulary or decide what your terms ought to mean. That authority stays with you.