KYE™ Directory™
Search the authority graph.
KYE™ Directory™ is the public search surface. You ask who holds what authority, what evidence proves it, what risk is open, and what breaks if it is revoked — and the directory answers from the live graph. KYE™ Assurance™ lives here too: every certified entity, conformance pack, and audit replay is one query away.
Entities Agents Evidence packs Connectors Frameworks
1 · Authority Search
Who can act, on whose behalf?
Search any entity (`kye:org:gb:hmrc:000123`, `kye:agent:vendor:foo:1`) and the directory shows the full delegation chain, current grants, scope intersections, and active revocations.
2 · Evidence Search
Which decisions have proof?
Fetch an Evidence Pack™ by decision id, replay it byte-for-byte, verify the signature with public keys, and export the bundle to an auditor.
3 · Risk Search
What signals are open?
List every open risk signal across the authority graph — credential lapses, attestation expiries, drift events, blocked decisions — and follow each one to the entity it constrains.
4 · Blast Radius
What breaks if I revoke this?
Pick any authority grant; the directory shows every downstream delegation, every active decision, and every running workflow that depends on it. Revoke once, see the cascade.
5 · Connector Registry
connector
Which integrations are certified?
Every conformant connector ships with a manifest, schema declarations, and a signed conformance pack. The registry shows version, scope, and assurance level at a glance.
6 · Assurance Records
Who is KYE™ Certified™?
KYE™ Assurance™ is bundled into this directory: each certified entity, conformance pack, and regulatory mapping is a queryable record. Auditors search; everyone else verifies.
7 · Watch Surfaces
Which watches are served here?
The pull endpoint of the KYE™ Regulator Watch™ standing-witness surfaces. What is declared on a surface is what this page serves; nothing about the watched entity's other systems is claimed.
2 watch surfaces name this page as the pull endpoint. Each lists the state classes a follower is entitled to see and every sealed transition recorded so far: a decision id, an Evidence Pack™ reference and the public verify link, nothing from the watched entity's data plane. Generated from the followability and engagement registries; it changes only when they do.
Institute of Digital Economy (IoDE) Armenia: sme-payment-authority
kye:follow-surface:engagement:iode-armenia-agentic-finance · watches kye:engagement:iode-armenia-agentic-finance · status active · operating boundary: Phase One synthetic-data-only · visibility overt · follow-grant decided under kye:rule:follow-grant:pilot-engagement-default
Push delivery deferred: Pull-only today. A supervisory or counterparty follower reads engagement status transitions and completed obligation reviews at /directory.html; nothing is delivered to them, so noticing a change is their poll, not our push. Stated in the send-ready supervisor guide in exactly these terms before anything attractive is claimed, because a supervisor should not discover a delivery limit after signing. Closing it needs the §37 emission wiring, which is a runtime build and not a configuration of this row.
engagement:status-transition2026-08-29: registered → active, authorised by CEO onboarding directive 2026-08-29 (Armenia + OBP wave). Phase One synthetic-data-only remains the operating boundary; production data admission is a separate governed transition.kye:decision:bfb5a3e02dce8ce4ca8ce772·kye:evidence-pack:e371bc7687c1e691db7e010d· verify from public keysobligation:review-completed: no recorded item yet. First review due 2026-11-27 (activation date + review cadence).
TESOBE GmbH / Open Bank Project: open-banking-connector
kye:follow-surface:engagement:obp-open-banking-connector · watches kye:engagement:obp-open-banking-connector · status active · operating boundary: design-partner: connector co-design, sandbox-only · visibility overt · follow-grant decided under kye:rule:follow-grant:partner-engagement-default
Push delivery deferred: Pull-only today. The partner reads status transitions, obligation reviews and connector contract-version publications at /directory.html; a new contract version is not delivered, so an integrator polls for it. Same §37 emission wiring blocks it as the Armenia surface; declared separately because the state classes differ and a shared sentence would hide that a contract-version publication is the one a partner most needs pushed.
engagement:status-transition2026-08-29: registered → active, authorised by CEO onboarding directive 2026-08-29 (Armenia + OBP wave). Sandbox-only connector co-design remains the operating boundary per the obligation manifest.kye:decision:8849de1f532cc3e1bafeaff9·kye:evidence-pack:9a12c2402e2eaf719aebef46· verify from public keysobligation:review-completed: no recorded item yet. First review due 2026-11-27 (activation date + review cadence).connector:contract-version-published: declared on the surface. No canonical record carries a sealed item of this class yet, so nothing is shown rather than something invented.
Ready to see your AI agents flagged?
Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.
Canonical KYE™ surfaces referenced on this page: Authority Graph™ · KYE Protocol™.