---
title: "KYE Protocol™ — Sales deck (v3.1, 15 slides)"
description: "Interactive 15-slide sales deck for the KYE Protocol™: the Entity Trust Control Plane for AI-native systems. Runtime Gateway™ answers the seven canonical questions every inference must answer. Start with evidence. Move to enforcement when ready."
url: https://kyeprotocol.com/sales/deck/
lang: en
source: "KYE Protocol"
---

> Interactive 15-slide sales deck for the KYE Protocol™: the Entity Trust Control Plane for AI-native systems. Runtime Gateway™ answers the seven canonical questions every inference must answer. Start with evidence. Move to enforcement when ready.

# KYE Protocol™ — the Entity Trust Control Plane for AI-native systems.

Every AI inference becomes a governed, evidenced, replayable event — without replacing IAM, OAuth, your API gateway, GRC, or SIEM.

[Apply for a pilot](https://kyeprotocol.com/pilot-apply/) [See an Evidence Pack™](https://kyeprotocol.com/evidence-pack-demo/) [Apply for a pilot](https://kyeprotocol.com/pilot-apply/)

KYE™ adds a delegated-authority, evidence, and runtime-decision layer on top of the stack you already run.

2026-05-15 · v3.1 · KYE Protocol™ Ltd

From KYX to KYE™

## Categories verify. Protocols govern.

KYC verifies the customer. KYB verifies the business. KYA verifies the agent. The natural next step was **KYX — know your X**. But KYX is still verification at onboarding. Once every component of a digital system — human, agent, model, dataset, tool, downstream API — can act under delegated authority, governance has to be a **protocol**, not a stitched-together report.

- **KYC / KYB / KYA** — verify a category of actor _once_, at onboarding.
- **KYX** — the generalisation. Works for new categories, still a verification step.
- **KYE™** — runtime governance. Every action governed, every inference evidenced, every delegation replayable.

AI agents don’t just _identify_. They **act**. Existing systems verify who logged in. They cannot prove **what was invoked**, **on whose behalf**, **against what dataset**, **under what policy**, **at what risk class**, and **whether the call is auditable**. [Read the full thesis →](https://kyeprotocol.com/thesis/)

Why existing tools are not enough

## IAM controls access. KYE™ governs every inference.

| Layer | Question it answers |
| --- | --- |
| **IAM / OAuth** | Can this identity access the system? |
| **API Gateway** | Can this request reach the service? |
| **GRC** | Are controls documented? |
| **SIEM** | What events happened? |
| **MLOps platform** | Did the deployment succeed? |
| **KYE™** | Was this inference **verified**, **allowed**, against an **approved dataset**, in a **permitted jurisdiction**, under a **compliant policy**, at the right **risk class**, and is the call **auditable**? |

KYE™ does not replace existing infrastructure. It adds the missing **per-inference accountability layer**.

The KYE™ answer

## Seven questions every AI-native call must answer.

The KYE™ Runtime Gateway™ resolves each one before the inference reaches downstream systems.

Q1

### Verified

Q1 Is the model endpoint registered and within its declared parameters?

Q2

### Allowed

Q2 Is the caller authorised — under the delegated-authority chain — to invoke it?

Q3

### Dataset

Q3 Is the dataset being read or referenced approved for this purpose?

Q4

### Jurisdiction

Q4 Is the tool, data, or downstream effect allowed in the caller’s jurisdiction?

Q5

### Policy

Q5 Is the request compliant with the active Operating Model™ and policy bundle?

Q6

### Risk class

Q6 Is the model suitable for the declared risk class on its evaluation profile?

Q7

### Auditable

Q7 Is the entire call — inputs, outputs, decision, evidence — replayable from a signed Evidence Pack™? If any answer is “no”, the Runtime Gateway can deny, escalate, or shadow per the active mode.

The wedge

## Start with evidence. Move to enforcement when ready.

### Observe.

The Runtime Gateway™ runs in shadow mode — no production block. Every model-endpoint invocation is captured with full context.

### Evidence.

Each observed inference becomes a signed Evidence Pack™: actor, principal, purpose, authority, scope, dataset, policy, decision — replayable.

### Alert.

Authority gaps, jurisdiction drift, and risk-class violations surface as events in your existing SIEM — without blocking.

### Guard.

Narrow guards deploy on the highest-risk model endpoints. Production stays fast; risk is bounded.

### Enforce.

Runtime decisions block unauthorised, out-of-scope, or out-of-jurisdiction inferences before they reach downstream systems.

### Expand.

Roll out to additional workflows, sectors, and partners using the same protocol primitives and Evidence Pack™ format.

KYE™ ships in **four Edge Governance modes** (Shadow · Advisory · Guarded · Strict). You pick which.

First use case

## Per-inference accountability for enterprise AI.

Enterprise AI copilots Agentic payments Procurement agents Customer-support agents Compliance investigation agents Third-party AI workflows Open-finance workflows Clinical decision support

First commercial wedge: **regulated AI workflows in financial services** under EU AI Act, DORA, and the FCA Operational Resilience regime.

How it works

## Every inference resolves to a canonical entity chain.

Entity hierarchy v3.1 (constitution §1a, locked 2026-05-15). The Runtime Gateway answers the seven questions against the leaf `kye:endpoint:…`.

Tenant kye:tenant:…

Workspace kye:wsp:…

Model Endpoint kye:endpoint:… · policy\_set + evaluation\_profile + audit\_stream

Runtime Gateway™ seven-question decision

Evidence Pack™ → Audit Stream kye:audstream:… → SIEM / GRC / Cold storage

A `kye:model:…` is the artefact. A `kye:endpoint:…` is the **bound URL with its own governance** — that is what gets verified.

The control plane

## KYE™ Runtime Gateway™ — the canonical answerer.

### What it is

A Cloudflare-edge worker on the inference path. Resolves the seven Runtime Gateway questions in < 25 ms p95, with offline fallback.

### What it consults

Compiled Authority Bundle (signed at the edge) + Operating Model™ + Evaluation Profile + Policy Set for the resolved endpoint.

### What it emits

One signed Decision Map™ per call + a Risk Score (Ed25519) + an Evidence Pack™ entry pushed to the bound Audit Stream.

### Four Edge Governance modes

Shadow · Advisory · Guarded · Strict — per-endpoint, per-jurisdiction. Edge Arbiter enforces the Safety Floor when offline.

If a single question is unresolved at the edge, the Runtime Gateway never silently allows — it falls back to the declared mode and writes an Offline Evidence Log entry that reconciles on next sync.

Constitutional locks

## The protocol governs itself.

Constitution §0.3 (adopted 2026-05-15). Every CI run, deploy, schema migration, secret rotation, and domain binding is governed by the same engines that govern customer inferences.

### KYE™ Governance Engine™

Governs every privileged action. Issues `kye.purpose.request.v1`, `kye.purpose.admissibility.v1`, `kye.evidence.decision_map.v1`, `kye.replay.context_seal.v1`. Same engine that authorises customer agents authorises our own deploys.

### KYE™ Compliance Engine™

Every regulatory-framework claim maps to a control row + ≤ 90-day attestation. Emits `kye.compliance.attestation.v1` and `kye.evidence.pack.v1` on a fixed cadence. Frameworks: EU AI Act, NIST AI RMF, ISO 42001, DORA, SOC 2.

Customers do not have to **trust** our claims. They can **replay** them — against the same Evidence Pack™ format the Runtime Gateway emits for their own inferences.

The platform

## Ten engines × eight rails — one protocol.

Engines are the computation primitives. Rails are the user-facing surfaces that orchestrate them. Locked by constitution §14.

### Ten engines

Entity · Authority · Purpose & Scope · State · Rules · Decision · Evidence · Replay · Directory · Ecosystem.

### Eight rails

Purpose Permission™ · Resilience Loop™ · Directory · Operating Model™ · Delegated Auditability · Onboarding · Billing & Metering · Edge Governance™.

### How you reach them

SDKs (TypeScript · Python · Go) · OpenAPI · MCP server · webhooks · Cloudflare-edge Runtime Gateway™.

### Where you see them

KYE™ Cloud (app.kyeprotocol.com) · KYE™ Widgets (embeddable) · KYE™ Directory (search) · KYE™ Audit Pilot™ (regulator-facing).

Evidence Pack™ example

## Every inference produces replayable evidence.

- **Actor** — `kye:prin:…` that initiated the call
- **Endpoint** — `kye:endpoint:…` resolved at decision time
- **Principal chain** — delegated-authority path
- **Policy set** — active Operating Model™ hash
- **Dataset reference** — approved-purpose binding
- **Jurisdiction** — caller + datapath
- **Risk score** — signed `kye.risk.score.v1`
- **Runtime decision** — allow / deny / approval / shadow
- **Payload hash** — tamper-evident
- **Replay seal** — `kye.replay.context_seal.v1`

```
{
  "evidence_pack_id": "kye:evp:acme.example:01JYEVP0...",
  "issued_at":        "2026-05-15T13:31:00Z",
  "endpoint_id":      "kye:endpoint:acme.example:claude-sonnet-eu-2",
  "actor_principal":  "kye:prin:acme.example:agent:ops-copilot",
  "runtime_gateway": {
    "mode":        "strict",
    "q1_verified":  "true",
    "q2_allowed":   "true",
    "q3_dataset":   "approved",
    "q4_jurisdiction": "eu-west",
    "q5_policy":    "compliant",
    "q6_risk_class": "high-suitable",
    "q7_auditable": "sealed"
  },
  "control_refs": [
    "EU_AI_ACT.AIA_HIGH_RISK_LOGGING",
    "EU_AI_ACT.AIA_HUMAN_OVERSIGHT",
    "DORA.ICT_RISK_REGISTER",
    "ISO_42001.AIMS_8_2"
  ],
  "risk_score": {
    "value":        12,
    "out_of":       100,
    "signature_suite": "ed25519-2025"
  },
  "replay_context_seal": "sha256:9c8a..."
}
```

Every Evidence Pack™ is replayable offline — auditors verify against the canonical format, not your screenshots.

Advanced assurance

## Beyond local validity.

### Scenario Testing™

Simulate what could happen under proposed authority changes before they ship to production.

### Approval Brief™

Brief approvers with full context, alternatives, and risks before the inference executes.

### Reality Coupling™

Detect when a locally valid system has decoupled from current ground truth.

### Stable Drift Detection

Surface slow, plausible drift that single-action audits miss — rolling-window detector.

KYE™ can **simulate what could happen**, **brief approvers before action**, and detect when a locally valid system has become **decoupled from current reality**.

Enterprise value

## What each audience gets.

### GRC

AI use-case inventory
Risk register
Control mapping
Audit evidence
Framework readiness (EU AI Act, DORA, ISO 42001)

### Security

Per-inference visibility
Runtime authority logs
Revocation cascade
SIEM events
Risk-score alerts

### Engineering

SDKs (TS / Py / Go)
OpenAPI
MCP server
Webhooks
Evidence Pack™ automation

### Leadership

Governance coverage %
Audit readiness
Risk-class exposure
Reduced AI adoption friction
Replayable claims

Pilot offerings

## Six productised pilots. Fixed scope. Closed registration.

Every pilot has its own onboarding agent, demo seed pack, dashboard preset, Evidence Pack™ sample, and signed final report. The commercial menu is sent to qualified applicants by email — not published.

| Offering | Duration | Best for |
| --- | --- | --- |
| **KYE™ Discovery Workshop™** | 1 week | Use-case shortlist, authority-risk map, pilot scope. |
| **KYE™ AI Agent Audit Pilot™** | 4 weeks | Enterprise AI / copilot / agent owners — one workflow, Shadow mode. |
| **KYE™ Regulated Workflow Pilot™** | 6 weeks | Banks / insurers / healthcare / public sector — 2–3 workflows. |
| **KYE™ Governance Ops Pilot™** | 8 weeks | GRC / security / legal / audit teams — inventory + register + dashboard. |
| **KYE™ Edge Governance Pilot™** | 8 weeks | Defence / energy / drones / critical infrastructure — offline / degraded. |
| **KYE™ Strategic Sandbox Pilot™** | 12 weeks | Banks / ecosystems / regulators / national platforms — multi-team. |

Pilot fees credit 100% against the first-year annual licence when signed within 60 days — the commercial menu and conversion terms are shared after qualification.

Call to action

## Start with one workflow.

1. Pick a pilot. Define **one AI workflow** and the model endpoint that backs it.
2. Bind the Runtime Gateway™ in **Shadow** mode — no production block.
3. Generate **Evidence Packs™** on every inference. Receive the signed final report.
4. Surface **authority gaps, jurisdiction drift, risk-class violations**.
5. Convert pilot → annual at the right tier. Pilot fee credited at signature.

After you apply, the qualification team responds within **2 business days** with the full commercial menu, conversion terms, and pilot scope draft.

Start with **evidence**. Move to **enforcement** when ready.

Canonical KYE™ surfaces referenced on this page: [Audit Pilot](https://kyeprotocol.com/auditors/) · [Delegated Auditability](https://kyeprotocol.com/glossary/) · [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) · [KYE™ Cloud™](https://kyeprotocol.com/apps/) · [KYE™ Directory™](https://kyeprotocol.com/directory/) · [KYE™ Edge Governance™](https://kyeprotocol.com/glossary/) · [KYE™ MCP Server](https://kyeprotocol.com/mcp/) · [KYE™ Onboarding Agent](https://kyeprotocol.com/glossary/) · [KYE Protocol™](https://kyeprotocol.com/) · [Purpose Permission](https://kyeprotocol.com/glossary/) · [Resilience Loop](https://kyeprotocol.com/glossary/).