---
title: "KYE Protocol™ — Knowledge graph · step 5 of the KYE™ stack"
description: "KYE™ knowledge graph — the live, instance-level graph of entities, authorities, delegations, capabilities, scopes, decisions and evidence"
url: https://kyeprotocol.com/knowledge-graph/
lang: en
source: "KYE Protocol"
---

> KYE™ knowledge graph — the live, instance-level graph of entities, authorities, delegations, capabilities, scopes, decisions and evidence

Step 5 · Knowledge graph

# Live instances of entities, authorities, decisions.

Steps 1–4 define the _contracts_. Step 5 is the _state_: a live, instance-level graph of every entity, every signed delegation, every capability grant, every scope, every state vector, every decision and every evidence pack the runtime has produced — typed under the KYE™ ontology and bound by signatures.

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

1 · What lives here

## Authority Graph™ · Decision Map™ · Evidence Graph™ · Blast Radius Map™.

KYE-Graph™ ships four normative graph projections over the same instance store. Each is a typed view, not a separate database.

### Authority Graph™

Entities, delegations, authorities, capabilities, scopes — every edge typed by the ontology.

### Decision Map™

The signed, replayable artefact emitted with every authorize call. Inputs → rules → outcome.

### Evidence Graph™

Audit events, evidence packs, transparency receipts — bound to the decisions that produced them.

### Blast Radius Map™

The downstream-derived authorities a single revocation or quarantine signal would reach. Pre-emit; helps operators choose the right action.

2 · Why a graph and not a table

## Authority is a chain, not a row.

Tabular ACLs answer _"can actor A do X?"_. The agentic stack needs _"can actor A act on behalf of principal P, under delegation D, attenuated by scope S, in state vector V, against capability C, with evidence E?"_ — a path query, not a row query. A graph is the only honest data model. The Authority Graph™ is what the policy engine traverses in step 6.

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 4 · Schemas](https://kyeprotocol.com/schemas/) [Step 6 · Policy engine →](https://kyeprotocol.com/decision-engine/)

## 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/).