---
title: "Architecture Graph — the protocol as a map · KYE Protocol™"
description: "An Obsidian-style interactive map of KYE Protocol™ — every engine, agent, rail, schema, gate and chapter as a node, every dependency as a typed edge. The same canonical graph the table view audits, rendered so you can see the architecture in one screen."
url: https://kyeprotocol.com/graph/
lang: en
source: "KYE Protocol"
---

> An Obsidian-style interactive map of KYE Protocol™ — every engine, agent, rail, schema, gate and chapter as a node, every dependency as a typed edge. The same canonical graph the table view audits, rendered so you can see the architecture in one screen.

# The whole architecture, as one map

[KYE Protocol™](https://kyeprotocol.com/) is a living system of engines, agents, rails, schemas, gates and chapters that must stay coherent on every commit. The Architecture Graph renders that system the way an engineer actually reads it — a node-link map you can pan, zoom and search — so you grasp in one screen what a list takes an afternoon to trace. Click any node to light up its dependencies.

[Start a governed pilot](https://kyeprotocol.com/poc/) [Open the table view](https://kyeprotocol.com/cascade-inventory/)

## Explore the graph

This is the same canonical graph the protocol uses to keep itself coherent — projected as a visual map instead of a sortable table. Filter by macro group or component category, search for any node, and click a node to focus its typed neighbours. Drag a node to reposition it; scroll to zoom.

Loading the architecture graph…

Honest rendering: every node and edge here is read from the protocol's own canonical dependency graph — engines, agents, rails, schemas, gates and constitution chapters, joined by the nine typed relationship verbs (produces, consumes, feeds, fetches-from, interacts-with, affected-by, impacted-by, connected-to, peer-of). It is the architecture, not a sketch of it.

## Why a map and not a list

Because architecture is a graph, and a list flattens it. When you can see KYE Protocol™ as a graph, the things that matter to you as a builder or a reviewer become visible at a glance.

- **Blast radius.** Click a schema and watch every gate, generator and page that consumes it light up — so you know what one change touches before you make it.
- **Coherence.** The same graph backs the [Cohesion Cascade™](https://kyeprotocol.com/glossary/) that fails CI when a source-of-truth edit doesn't ripple to its derived artefacts. The map shows you why.
- **Onboarding.** A new engineer reads the whole protocol — hundreds of nodes across platform, developer, compliance and commercial macro groups — in minutes, not days.

[See the same data as a table](https://kyeprotocol.com/cascade-inventory/)

## The same source of truth, two views

The Architecture Graph is a projection, not a parallel system — it reads the one canonical dependency graph and never invents its own. That single-root discipline is what lets KYE Protocol™ stay coherent at scale, and it's the reason regulated buyers can trust what they see.

- **One root, many views.** The visual map here and the sortable [cascade inventory table](https://kyeprotocol.com/cascade-inventory/) render the identical canonical graph — change the source once and both views update on the next build.
- **Typed, not decorative.** Every edge carries one of nine relationship verbs, so the map is a queryable dependency graph an auditor can reason about — not an org chart.
- **Public-safe by construction.** The map exposes node labels and component categories only; no internal mechanism content reaches this page, by the same patent-safety pass that guards every public surface.

Want the live data contract behind the map? Browse the [schema catalogue](https://kyeprotocol.com/schemas/) or the [chain-of-authority globe](https://kyeprotocol.com/authority-globe/) — two more views over the same canon.