Adopt
Adopt the rail audit-ready from day one.
Move to production with a signed audit trail — apply for a pilot, audit a KYE™-governed system in days against signed Evidence Packs™, and operate with WORM retention, dual-channel sign-off, and offline-verifiable proofs. These are the adoption + audit surfaces.
Decision centre: chain of authority, admissibility, finality
ComputedYou learn: Who decided what, along which chain, why a request was held or denied, and that the record is final and verifiable. You can: Watch decisions arrive; approve as the delegate (the initiator cannot), verify a seal, revoke a delegation.
-
Procurement agent orders above its approval threshold
approval_threshold_breach
Chain of authority
- Orrin Logistics (demo) Principal
- Dara Quinn, head of procurement kye:authority:orrin.example:procurement-head-2026
- Procurement agent kye:authority:orrin.example:proc-04-2026q4
-
Drafting agent prepares a disclosure letter, with redaction
permission_granted
Decision record sealed
- Decision allow_with_constraints
- Obligations kye:obligation:redaction
ff8305bc6290ca7ef2d60b6290c4c2712c62b1280faf28be46d896685fdea90e -
Credit agent acts outside its jurisdiction
jurisdiction_unsupported
Decision
- not_revoked grant in force
- within_time_window 2026-10-14T09:09:20Z before 2027-01-12T00:00:00Z
- action_in_scope credit.line.approve in [credit.line.approve]
- purpose_matches lending.adjudicate = lending.adjudicate
- within_jurisdiction US in [GB, IE]
- within_constraints GBP 4,200.00 ≤ GBP 25,000.00
-
Accounts-payable agent pays a supplier invoice
permission_granted
Chain of authority
- Brightmoor Retail (demo) Principal
- Ana Ruiz, finance lead kye:authority:brightmoor.example:finance-lead-2026
- Accounts-payable agent kye:authority:brightmoor.example:ap-11-2026q4
-
Clinical summarisation agent asks to read records for marketing
permission_missing
Decision
- not_revoked grant in force
- within_time_window 2026-10-14T09:05:31Z before 2027-01-01T00:00:00Z
- action_in_scope record.read in [record.read, record.summarise]
- purpose_matches marketing.outreach ≠ clinical.summarise
- data_class_in_scope [health.record] in [health.record]
- within_jurisdiction GB in [GB]
-
HR operations agent acts on a revoked delegation
delegation_revoked
Signal
- Regional treasurer, EU Revoked
- Treasury agent (fx-router) Revoked by cascade
How this widget is built
- Demonstrates
- Decision feed and approvals
- Components
- Policy decision point (evaluate, kye_decide)
- Chain of authority
- Admissibility checks
- Decision records and evidence packs
- Revocation cascade
- Flow
- Each decision lands on the device of whoever must know or act: approvals on the approver's phone, denials on the CISO dashboard, allows in the team channel. Tapping one opens its chain, checks, seal or cascade. Architecture diagram
- Used on
- /examples/: On the examples page; it plays when scrolled into view (Play/Pause).
- /: The home page, right after its opening.
- /terminal/: The terminal: the decision centre on its devices.
Full reference index — every page in the adopt stage (7) ↓
Derived from the graph
7 pages in the adopt stage.
This page is a derived view over internal — a secondary projection over the canonical kye-stage enum (the buyer-journey spine). Adding or retagging a page rebuilds this landing on the next CI run — no hand-curated list to maintain.
Audit
Audit — 7 pages
Audit a KYE™-governed system in days, not months — signed evidence, public-key verifiable.
- Example reports by role — KYE Protocol™ Where are the per-role sample reports? On the Example reports shelf — one signed report envelope per persona (auditor, board, CISO, DPO, regulator and more), each verifiable offline.
- KYE™ Delegated Auditability™ — Runtime accountability for AI agents, without replacing IAM Runtime accountability for AI agents without replacing IAM — KYE™ adds a delegated-authority and evidence layer on top of your existing IAM, OAuth, API gateway, workflow, SIEM, GRC and AI-agent stack.
- KYE Protocol™ — AI System Compliance Card | Public-key-verifiable nutrition label for AI systems The nutrition label for AI systems — The KYE Protocol™ AI System Compliance Card is a public-key-verifiable, machine-readable, human-readable summary of an AI system
- KYE Protocol™ — Assurance Card Profile · system cards become executable KYE™ Assurance™ Card™ Profile™ — turn KYE™ runtime evidence into a living lifecycle assurance record per delegated entity. Owner, intended use, authority model, human involvement, provenance
- KYE Protocol™ — Coverage heatmap | 249 frameworks × control families Coverage heatmap — every registered regulatory framework × control families, green/amber/red by coverage %%. Machine-readable: regenerated from coverage-registry.json on every push to main.
- KYE Protocol™ — For auditors & GRC how do you audit AI agents in days instead of months by fetching signed evidence packs you can verify offline?
- KYE Protocol™ — Self-audit fixture · publicly verifiable proof of mechanism Signed JSON artefacts proving the KYE™ Reference Gateway™ governs and audits itself with its own primitives. Anyone can fetch + verify with the JWKS at /trust/self-audit-jwks.json
Ready to evaluate KYE Protocol™?
Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.
Canonical KYE™ surfaces referenced on this page: Authority Graph™ · Delegated Auditability · Evidence Pack™ · KYE Protocol™.