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.

Coverage by jurisdiction

Demo data

You learn: Where KYE™ coverage is active, staged or planned. You can: Pick a stage.

Global / jurisdiction-neutral · 5 frameworks✓——
International (ISO / IEC) · 5 frameworks✓——
United Kingdom · 19 frameworks✓——
United States · 17 frameworks✓——
European Union · 9 frameworks✓——
Gulf region (GCC) · 4 frameworks✓——
Public sector (cross-jurisdiction) · 4 frameworks✓——
Canada · 16 frameworks✓——
Australia · 4 frameworks✓——
New Zealand · 3 frameworks✓——
Singapore · 3 frameworks✓——
Japan · 3 frameworks✓——
India · 6 frameworks—✓—
Brazil——✓
China (PRC) · 1 frameworks——✓
Switzerland · 1 frameworks✓——
Hong Kong——✓
Germany · 5 frameworks✓——
France · 5 frameworks✓——
Italy · 5 frameworks✓——
Spain · 5 frameworks✓——
Netherlands · 5 frameworks✓——
Belgium · 5 frameworks✓——
Luxembourg · 5 frameworks✓——
Poland · 5 frameworks✓——
Sweden · 5 frameworks✓——
Norway · 5 frameworks✓——
Denmark · 5 frameworks✓——
Finland · 5 frameworks✓——
Austria · 5 frameworks✓——
Ireland · 5 frameworks✓——
Portugal · 5 frameworks✓——
Greece · 5 frameworks✓——
Czech Republic · 5 frameworks✓——
Hungary · 5 frameworks✓——
Romania · 5 frameworks✓——
Slovakia · 5 frameworks✓——
Bulgaria · 5 frameworks✓——
Cyprus · 5 frameworks✓——
Malaysia · 1 frameworks—✓—
United Arab Emirates · 1 frameworks—✓—
Bahrain · 1 frameworks—✓—
Saudi Arabia · 1 frameworks—✓—
Indonesia · 1 frameworks—✓—
Pakistan · 1 frameworks—✓—
Qatar · 1 frameworks—✓—
Kuwait · 1 frameworks—✓—
Oman · 1 frameworks—✓—
Türkiye · 1 frameworks—✓—
Nigeria · 1 frameworks—✓—
Brunei Darussalam · 1 frameworks—✓—
Jordan · 1 frameworks—✓—
Egypt · 1 frameworks—✓—
Sudan · 1 frameworks—✓—
Thailand——✓
How this widget is built
Demonstrates
Coverage Atlas
Components
  • Jurisdiction dictionary (stages)
  • Framework registry
Flow
Jurisdiction → stage → frameworks. Architecture diagram
Used on

Chain of Authority: the chain, hop by hop

Demo data

You learn: Where the authority comes from at each hop. You can: Walk the chain.

How this widget is built
Demonstrates
Chain of authority
Components
  • Principal
  • Delegations
  • Agent
  • Decision
  • Evidence
Flow
Each hop of the chain, as the page sets it out. Architecture diagram
Used on

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.

Chain of Authority™global view · live projection

principal / delegation
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, for tracing one incident or sampling a whole quarter.

  1. Principal. kye:org:acme_ltd — the organisation on whose authority everything below stands.
  2. Delegation. kye:delegation:finance_team_to_agent — your finance team delegates, purpose-bound and time-boxed per ISO/IEC 42001 clause 6.
  3. 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.
  4. Capability. kye:capability:payment.prepare — the one action class this chain authorises; nothing ambient.
  5. 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.

Find your authority sprawl

Canonical KYE™ surfaces referenced on this page: Authority Graph™.