The Map of KYE™ — the protocol as a cypress
Picture the protocol as a cypress. The trunk is the KYE™ core that decides; the branches carry authority up to each stage; and the canopy is the chain of legitimacy, base to crown. Every consequential action your agents take climbs this tree, and you should be able to see exactly where it stands. The map below is that view: select a stage and its foliage lights while the rest dims, so a CISO, an auditor, or your build team reads one honest picture of how authority becomes final.
What the map shows
This is a projection of real KYE Protocol™ doctrine, not a decorative tree — every part stands for a component you can name. The trunk is the KYE™ core, the Decision Engine that admits or refuses each action. The branches are authority reaching each stage without widening on the way. The roots are the evidence evidence layer: write-once WORM storage and Replay-Proof™ records that survive the agent, the model, and the vendor.
- The canopy is split into six foliage bands, one per stage of the chain of legitimacy — the same chain the doctrine front-door walks top to bottom.
- Each band carries a callout naming the real mechanism behind it, so you are never reading a metaphor without its component.
- The whole picture is governed by the same canon that maps KYE Protocol™ to 243 frameworks, including the EU AI Act™, NIST AI RMF, and ISO/IEC 42001.
Here is the map. Pick a stage from the chips below and watch its foliage light while the rest of the tree dims — a wayfinder you and your team can point at in a review. Leave it on Whole tree to see the full cypress at once.
Select a stage — its foliage lights, the rest dims. Pure CSS, no script, so it works the moment the page loads.
Every part maps to a real component: trunk = the KYE™ core, branches = authority reaching each stage, roots = the evidence evidence layer (WORM · Replay-Proof™), canopy = the chain of legitimacy.
The chain of legitimacy
A consequential action does not become legitimate in one step — it climbs the tree, and KYE Protocol™ governs every link so authority never leaks between them. Read the canopy base to crown, exactly as the trust layer doctrine reads it, and each stage is the input to the next.
- Purpose. The declared reason the action is allowed to exist, scoped and time-bound. KYE Protocol™ calls this Purpose Permission™ — the lowest band, the soil the rest grows from.
- Authority. The delegated permission that licenses the act, traced across every principal in the chain so you can resolve who held it.
- Delegation. How that authority passes to an agent, a tool, or a teammate — passed, never widened on the way.
- Execution. The action itself, admitted or refused at the moment it is attempted, not reviewed weeks later. This is Action Admissibility™.
- Evidence. The signed record of what was decided and why, captured as an Evidence Pack™ the affected person can contest.
- Finality. A sealed answer that replays from public keys alone. KYE Protocol™ calls this Authority Finality™ — the crown of the tree.
Where you are — the wayfinder
The lit band is not random: in production, the Map of KYE™ follows each page's stage. Every KYE Protocol™ surface declares a kye-stage in its metadata, and the map lights the foliage for that stage — so wherever you land, you can see at a glance which link of the chain you are standing on.
- If you are a builder wiring an agent, the map lights Execution and points you at where admissibility is checked.
- If you are a CISO or counsel reviewing an incident, it lights Evidence and Finality, the bands a regulator will ask about.
- If your team is scoping a new use case, it lights Purpose and Authority — the questions you answer before a single action runs.
One doctrine, many implementations
You are looking at one tree because there is one doctrine. The cypress is a single canonical view of the chain of legitimacy; the products, agents, and dashboards KYE Protocol™ ships are all projections of these same six stages, never competing pictures of them.
- The same chain governs a payment agent, an onboarding flow, and a regulator-facing report — the bands do not change, only the action does.
- Because the map is honest, you can hand it to your board or your auditor and walk the same six stages every KYE™ deployment produces.
- It is the front-door view of the trust layer for consequential action: decide, record, make final — drawn as a tree you can read in one glance.