---
title: "KYE Protocol™ — Rules Gateway™ — runtime enforcement"
description: "Every delegated AI action passes through the Rules Gateway™™. The gateway loads the applicable rule packs + dictionaries + manifests for the tenant…"
url: https://kyeprotocol.com/rules-gateway/
lang: en
source: "KYE Protocol"
---

> Every delegated AI action passes through the Rules Gateway™™. The gateway loads the applicable rule packs + dictionaries + manifests for the tenant…

KYE Protocol™ · architecture

# KYE™ Rules Gateway™ — runtime enforcement boundary

Every AI action goes through the gateway. The gateway checks rules. You get one of six verdicts — with proof.

[Apply for pilot →](https://kyeprotocol.com/pilot-apply/) [Read the docs](https://kyeprotocol.com/docs/)

Plain take

## Plain take

Every call. One check. One verdict. With proof.

- Allow. Deny. Approve. Warn. Quarantine. Limit.
- Each verdict cites a rule.
- Each rule cites a control.
- Each call gets an evidence pack.

## Architecture

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

The Rules Gateway™ is the canonical enforcement boundary for delegated AI. The pre-existing [KYE™ Runtime Gateway™](https://kyeprotocol.com/protocol/) (the seven-question contract from) is a specialisation of the Rules Gateway™ for AI-inference calls — same enforcement boundary, AI-specific rule pack loaded.

```
AI agent / app / workflow / MCP tool
                ↓
        KYE™ Rules Gateway™
                ↓
   loads applicable manifests
   loads applicable dictionaries
   loads applicable rule pack(s)
   calls Authority / Purpose / State / Decision engines
                ↓
   allow | deny | review | evidence_required | quarantine
                ↓
   emits Evidence Pack + Replay Proof
                ↓
   packages into Authority Proof Bundle (Phase 6)
```

## Canonical verdict precedence (locked)

Effects from matching rules reduce by canonical precedence. **deny wins absolutely** regardless of priority — the safety floor.

1. **deny** — safety floor
2. **require\_human\_approval**
3. **require\_revalidation**
4. **quarantine**
5. **rate\_limit**
6. **require\_evidence\_pack**
7. **advisory\_warn**
8. **audit\_route\_\*** (side effects, no verdict change)
9. **allow**

## 11 condition operators

Rules express condition trees using `all_of` / `any_of` / `not` combinators and these leaf comparators: `eq · ne · gt · gte · lt · lte · in · not_in · matches · exists · older_than`. Field paths use JSONPath-style accessors into the action context.

## Runtime

Library: `@kye/rules-gateway` — pure deterministic evaluator + loader; 12 passing unit tests against the real Financial Services rule pack. Worker wrapper ships at `internal`.

## 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™](https://kyeprotocol.com/rules-gateway/) enforces.

- [Profiles — the 10 canonical conformance modes](https://kyeprotocol.com/profiles/)
- [Rule packs — behavioural logic](https://kyeprotocol.com/rule-packs/)
- [Dictionaries — canonical vocabulary](https://kyeprotocol.com/dictionaries/)
- [Sector packs — sector bundles](https://kyeprotocol.com/sectors/)
- [Manifests — installable / verifiable units](https://kyeprotocol.com/manifests/)
- [Rules Gateway™ — runtime enforcement](https://kyeprotocol.com/rules-gateway/)

Canonical KYE™ surfaces referenced on this page: [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) · [KYE Protocol™](https://kyeprotocol.com/).