---
title: "KYE Protocol™ — Decision Engine · step 6 of the KYE™ stack"
description: "KYE™ Decision Engine — the PDP that walks the Authority Graph™ at decision time, evaluates vocabulary-bound predicates, runs continuity + discoverability…"
url: https://kyeprotocol.com/decision-engine/
lang: en
source: "KYE Protocol"
---

> KYE™ Decision Engine — the PDP that walks the Authority Graph™ at decision time, evaluates vocabulary-bound predicates, runs continuity + discoverability…

Step 6 · Decision Engine

# The KYE™ Decision Engine — decisions over meaning + state.

Step 5 holds the live instance graph. Step 6 is the engine that walks it. The Decision Engine (KYE™ Decision Engine™) consumes a candidate request, traverses the Authority Graph™, evaluates ontology-bound predicates, runs continuity + discoverability checks, and returns a signed verdict with reason code.

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

1 · What it does at decision time

## Walks the chain. Signs the verdict.

For every candidate decision the Decision Engine resolves the actor / principal / capability / scope context, evaluates it against the bound authority graph, ontology, continuity and discoverability inputs, and returns a verdict with a reason code. The verdict is bound into a signed Decision Map™ and chain-linked into the audit ledger.

The specific check ordering, the inter-check short-circuit rules, the verdict alphabet, and the per-verdict obligation set are proprietary and are not disclosed in this repository. Conformant runtimes consume the canonical contract via the private decision-engine binding.

2 · The decision endpoint

## One authorize call.

```
POST /v1/runtime/authorize
Content-Type: application/json

{
  "actor_entity_id": "kye:agent:finance_agent_001",
  "principal_entity_id": "kye:user:finance_owner_001",
  "capability_id": "kye:capability:payment.prepare",
  "scope": { "amount": { "value": 240, "currency": "GBP" } },
  "delegation_id": "kye:delegation:0xabc"
}
```

Custom per-vendor gates are replaced by one signed verdict + one signed Decision Map™, replayable offline by any third party with the published JWKS.

Where to go next

## Continue the stack →

Every claim here is backed by the open KYE Protocol™ contracts and verifiable end-to-end from the publisher's JWKS — you check it yourself, you don't take our word for it.

[← Step 5 · Knowledge graph](https://kyeprotocol.com/knowledge-graph/) [Step 7 · Runtime gateway →](https://kyeprotocol.com/gateway/)

## Ready to see your AI agents flagged?

Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.

[Apply for pilot →](https://kyeprotocol.com/pilot-apply/) [Try the sandbox →](https://kyeprotocol.com/sandbox/demos/)

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