The chain of authority, as a living globe
Every consequential AI action stands on a chain: a principal delegates, an agent acts, a capability is granted, evidence is sealed. KYE Protocol™ renders that chain as what it really is — arcs of authority moving across jurisdictions, every hop checked at the moment it happens.
Global view
Arcs travel between the jurisdictions KYE Protocol™ maps — the EU AI Act, UK SM&CR, MAS, APRA and Canadian PIPEDA regimes among the 249 frameworks in the coverage registry; each waypoint is an authority check, not decoration.
agent acting
grant evidenced
Honest rendering: the arcs animate the canonical example corpus —
public/examples/authority-path-discovery.json and public/examples/delegation.json —
projected onto the covered jurisdictions. It is a faithful view of how the protocol moves authority, not a
simulation of customer traffic.
This globe shows how authority moves. To see where KYE Protocol™ is covered — and which jurisdictions sit dark and requestable — open the Coverage Atlas night-map, the complementary coverage view.
One chain, walked end to end
This is the actual five-hop authority path from the canonical example — the same shape every KYE™ deployment produces, whether you are a CISO tracing an incident or an auditor sampling a quarter.
- Principal.
kye:org:acme_ltd— the organisation on whose authority everything below stands. - Delegation.
kye:delegation:finance_team_to_agent— your finance team delegates, purpose-bound and time-boxed per ISO/IEC 42001 clause 6. - Actor.
kye:agent:finance_agent_001— the AI agent that will act. It is a first-class principal with a verifiable identity your auditors can resolve. - Capability.
kye:capability:payment.prepare— the one action class this chain authorises; nothing ambient. - Authority grant.
kye:authority:grant:payment_prepare_001— the runtime grant, sealed into an Evidence Pack™ any reader can replay-verify.
Boundary: KYE Protocol™ governs whether each hop may carry authority — it does not route payments or run the agent. Break a hop (revoke the delegation, expire the grant) and the chain fails closed at the next check.
Why a globe and not an org chart
Because your authority no longer lives in one building, one tenant, or one legal system — and a regulator reads it that way too.
- Your agents act across borders by default. A delegation granted under UK SM&CR can touch an EU AI Act high-risk system minutes later.
- Each hop changes which duties bind — EU AI Act Article 12 logging here, MAS TRM controls there. The handoff is itself an authority decision, checked and evidenced.
- Sprawl hides in the arcs. Orphaned delegations and over-scoped grants light up when you see your authority as a graph, not a list.