KYE Protocol™ · architecture

KYE Protocol™ rule packs — behavioural logic

Bundles of decision rules. Each rule maps to a control row. Each verdict cites the rule that fired.

Apply for pilot →Read the docs

Rule packs, point by point

Demo data

You learn: The page's points, one at a time. You can: Step through them.

  1. Step 1 of 8

    KYE Protocol™

    KYE™ EU AI Act Rule Pack™

    3 rules — EU AI Act Art. 6 / 9 / AIA Human Oversight / AIA High-Risk Logging

  2. Step 2 of 8

    KYE Protocol™

    KYE™ Compliance Evidence Rule Pack™

    evidence emission for actions carrying compliance control_refs

  3. Step 3 of 8

    KYE Protocol™

    KYE™ Action Admissibility Rules™

    deny on revoked authority / purpose-scope mismatch

  4. Step 4 of 8

    KYE Protocol™

    KYE™ Continuity Rule Pack™

    revalidate after role change

  5. Step 5 of 8

    KYE Protocol™

    KYE™ Meaning Continuity Rules™

    warn on deprecated vocabulary

  6. Step 6 of 8

    KYE Protocol™

    KYE™ Discoverability Rules™

    audit directory lookups to SIEM

  7. Step 7 of 8

    KYE Protocol™

    KYE™ Recovery Rule Pack™

    human approval after compromise

  8. Step 8 of 8

    KYE Protocol™

    KYE™ Federation Rule Pack™

    cross-trust-domain attestation

How this widget is built
Demonstrates
KYE Protocol™
Components
  • The points this page makes
Flow
Each point in order, as the page sets it out. Architecture diagram
Used on

70 rule packs (and counting)

What it is. Why it matters. What to do next.

Each rule pack carries: a manifest (what it applies to + which rules it includes) + N rule files (condition + effect + reason_code + control_refs). Adding a new compliance regime is a JSON PR, not a code change.

Compliance + behaviour

  • KYE™ EU AI Act Rule Pack™ — 3 rules — EU AI Act Art. 6 / 9 / AIA Human Oversight / AIA High-Risk Logging
  • KYE™ Compliance Evidence Rule Pack™ — evidence emission for actions carrying compliance control_refs
  • KYE™ Action Admissibility Rules™ — deny on revoked authority / purpose-scope mismatch
  • KYE™ Continuity Rule Pack™ — revalidate after role change
  • KYE™ Meaning Continuity Rules™ — warn on deprecated vocabulary
  • KYE™ Discoverability Rules™ — audit directory lookups to SIEM
  • KYE™ Recovery Rule Pack™ — human approval after compromise
  • KYE™ Federation Rule Pack™ — cross-trust-domain attestation
  • KYE™ Custody Rule Pack™ — evidence on custody changes
  • KYE™ Operating Model Rule Pack™ — deny without active OM
  • KYE™ Rate Limit Rule Pack™ — default 60 calls/min/capability/agent
  • KYE™ Transparency Rule Pack™ — cold-storage routing for high-risk decisions
  • KYE™ SIEM Routing Rule Pack™ — every deny → SIEM

Sector + payments

  • KYE™ Financial Services Rule Pack™ — 5 rules (payment threshold / authority gate / evidence / rate limit / credit decision)
  • KYE™ Payments Rule Pack™ — deny to blocklisted counterparty / evidence on every payment
  • KYE™ Card Payments Rule Pack™ — PCI DSS evidence for card data
  • KYE™ EU Payments Rule Pack™ — PSD2 SCA above €30
  • KYE™ Open Finance Rule Pack™ — TPP consent enforcement
  • KYE™ Treasury Rule Pack™ — dual control above £100k
  • KYE™ Pension Rule Pack™ — TPR record-keeping evidence

Browse rule packs →

Companion surfaces

What it is. Why it matters. What to do next.

Inside KYE Protocol™ the layers are these: profiles define is; rule packs define does; dictionaries define means; manifests define installable / verifiable / sellable; engines execute; the Rules Gateway™ enforces.

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.