The accountability rail for AI-driven action.

how do you move the KYE Protocol™ rail to production? Apply for a pilot, audit in days against signed Evidence Packs™, and operate with WORM retention, audit-ready.

AI governance is the discipline of bounding what an AI system may do, recording what it did, and proving it stayed inside its bounds when audited.

What is AI governance as a service? KYE Protocol™ delivers AI and agent governance as a service — the authority decision plus Replay-Proof™ evidence over the agents you already run.

What is Approval Briefs? The KYE™ GovernedUI add-on that turns a pending AI-agent action into a one-page brief a human can approve, reject, or escalate — with the decision sealed as evidence.

Can I see the whole KYE Protocol™ architecture at once? Yes — the Architecture Graph maps every engine, agent, rail, schema, gate and chapter as a node and every dependency as a typed edge.

What is Authority Finality™? KYE Protocol™

Who authorised an autonomous science agent to act? KYE Protocol™ proves the institution legitimately granted the authority for that specific real-world effect — capability alone never does.

What is the KYE™ Authority Risk Profiler? A read-only, customer-curated profile of your AI-agent estate that maps your clutter, overlaps, concentrations, bottlenecks, and painpoints so you can decide.

What is Authority Sourcing™? Event sourcing for authority: an entity

How do I see KYE Protocol™ govern a real agent action? Book a 30-minute demo — bring one action and we walk it through the rail live, refusal to signed evidence.

What is Bring-Your-Own Cross-Map? Paste your vocabulary, glossary or taxonomy — KYE™ maps each term to the framework + taxonomy spine (aligned, divergent, gap or conflict), flagging, never asserting.

What is the Chain of Authority Global View? A living globe rendering principals, delegations, agents, capabilities and grants as arcs across jurisdictions — every hop checked and evidenced.

Where can I follow KYE Protocol™? The /channels page lists every official channel — GitHub, X, LinkedIn, Hugging Face, and the Luma event calendars — each with its live status.

When your customer-service chatbot says it is an AI, issues a refund, or escalates, KYE™ proves the disclosure happened and the chatbot action was authorised, evidenced, and final.

Where does KYE Protocol™ cover? The Coverage Atlas rotating globe lights up 32 active jurisdictions and shows 3 dark, requestable ones — brightness is coverage depth, darkness is a gap.

Do I have to migrate to adopt KYE Protocol™? No — KYE™ is additive: you keep your systems, control what you share, and it composes with your stack rather than replacing it. Read-only by default.

How do you deploy a governed agent on your own infrastructure? Run real agent code your side; KYE Protocol™ governs the action boundary, proving authority per action — SaaS, in-region or self-hosted.

after the Digital Omnibus, which EU AI Act obligations apply when — and what should already be running at the action boundary before each date arrives?

does the KYE Protocol™ rail fit your problem? Read the per-audience briefs, framework coverage, and signed Evidence Pack™ samples that map the rail to your controls.

Where do I see KYE Protocol™ events? The /events hub — conferences, workshops, webinars, office-hours, and report launches, generated from one canonical calendar. Subscribe to be notified.

A live, signed Evidence Pack™: supplier_payment_agent prepares a £950 payment. Observed Action → Shadow Evaluation → Authority Gap → Guard Recommendation. Replayable offline.

How does KYE™ help with Failure to Prevent Fraud? It proves the consequential action was authorised, scoped and final — the reasonable-procedures evidence ECCTA asks for, replayable from public keys.

Which free tools can I use right now? The sandbox, the Authority Finality™ diagnostic, the Risk Profiler, the Evidence Pack™ demo, demos, the Cross-Map and KYE Lens™. No install, no signup.

Where is KYE Protocol™ strong, and where is it a gap? The Gap Finder shows 32 covered jurisdictions, 3 dark requestable ones, plus the frameworks out of scope — each gap has a request button.

How do I see what KYE Protocol™ looks like on my own stack? Send your website and email — you receive a tailored authority diagram of your systems, agents and evidence chain, prepared by a person.

What is governance by design for AI projects? KYE Protocol™ turns your project scope into a Governance Design Brief™ — controls, evidence and frameworks — before you build, crediting into a pilot.

What do reputable sources say about the problem KYE™ solves? /independent-signals collects verbatim, attributed quotes from McKinsey, WEF, NIST, BCG and Deloitte — observations, not endorsements.

What is the Agentic Authority Index™? KYE Protocol™

Lending with AI: how do you let agents underwrite, price, and decline credit while every decision stays authorised, model-in-scope, explainable via a Decision Map™, contestable, and replay-provable?

What is the KYE AI Adoption Navigator™? A free pre-adoption self-assessment that finds where AI delivers most value at least unmanaged risk, plus your first governed pilot and the controls you need.

Who and what can take consequential actions across your organisation — and where is that authority sprawling? KYE Authority Discovery™ is the free assessment that scores the sprawl.

Canadian health custodian: how do you let AI act on personal health information while every action stays lawful under PHIPA, inside the circle of care, with a signed replayable access record?

What is the KYE Compliance Observability Adapter™? It pulls GRC, observability, and eval telemetry into KYE™ as admissibility inputs, turning sensed signals into authority decisions.

Screening with AI: how do you let agents pull and act on consumer reports for hiring or tenancy while every use is purpose-permitted, consent-gated, explainable, and contestable?

KYE Directory™ is the public search surface across the authority graph. Find an entity, an authority grant, an evidence pack, a risk signal, or the blast radius of a single revocation.

estate-planning principal: how do you run wills, LPAs, trusts through one workspace where every clause is deterministic and every AI assist is bounded by a replayable authority chain?

KYE™ Federated Directory Query is the fan-out query that hits all eleven Directory indices in one round-trip and merges results under a deterministic ranking rule with per-tenant masking.

asset manager: how do you let AI recommend, rebalance and execute while every action stays inside its mandate, under a live grant from a named principal, replayable at supervisory review?

What is the KYE GitHub App™? An installable check that, on a pull request touching a privileged change, asks KYE™ whether it carries the required authority and posts a governed verdict.

Does KYE™ replace my GRC tool? No. KYE™ plugs into Drata, Vanta, or ServiceNow GRC, imports your existing controls, and exports a replay-provable Evidence Pack™ into them. Your GRC stays the record.

hardware team: how do you let AI help across the lifecycle while every action — release to fab, tapeout, firmware OTA, BOM change — stays admitted under a named engineer, replayable in a recall?

Hiring with AI: how do you let agents screen, rank, and reject candidates while every decision stays lawful, bias-audited, contestable, and replay-provable?

How do System Integrators ship KYE™ governance? The Authority Adapter Pack™ routes a host platform

What is KYE Lens™? A free, privacy-by-design browser extension that overlays a site

The KYE Marketplace™ hub. Find KYE™-certified consultants, connectors, and sector packs. All listings carry signed provenance — pay-to-rank is constitutionally forbidden.

MAS MindForge: how do you make the AI Risk Management Operationalisation Handbook enforceable at runtime, so every consequential AI action is oversight-mode-bound and replay-provable for MAS?

OCC AI supervision: how do you make the OCC

May an agent access, rely upon, invoke, cite, or transact with a resource — under its rights and jurisdiction? KYE Open Access Authority™ decides at the action boundary and evidences every decision.

conveyancing firm: how do you let AI help on a property matter while every step stays admitted under a named conveyancer, with source-of-funds evidence you can replay?

How do you refuse out-of-scope AI-agent action while it is forming, not reconstruct it after? KYE™ enforces authority at the moment of the action; refusals are signed, replayable.

Three pathways — KYE Protocol™ engagement model — how prospective adopters engage as enterprise Customers, ecosystem partners, or sector working-group participants. Engagement shape

The KYE Protocol™ ecosystem: Connector Hub™ integrates, Connector Profiles™ make authority portable across sectors, App Store productises, Plugin Marketplace™ extends. One orientation, four surfaces.

Universities: co-publish governed, replay-verifiable research with KYE™ via the Publishing Authority Track, run an authority pilot, and teach the authority layer most courses omit.

See yourself in KYE™ — Interactive demos for KYE Protocol™: decision flow, cascade visualizer, URN parser, trust graph, dashboard counters, and vocabulary browser.

The KYE™ App Store. 21 productised authority surfaces on KYE Protocol™ — payments, open finance, sandbox, sector apps, MCP, evidence, certification, legal. Open contracts; manifest schema

In 4–10 weeks a KYE™ pilot delivers a signed Evidence Pack™, regulator-mapped control crosswalk, and replay-proof bundle per privileged AI action — handable to auditor or regulator.

what is the KYE Protocol™ — the open standard, schemas, rails, and engines that produce signed evidence of every AI-agent action?

Buyer — what is the KYE Protocol™ quiz? A 60-second interactive scorecard rotating across Authority Risk Index™, AI Governance Knowledge, and Regulator Readiness. Shareable result with social card.

From KYX to KYE™ — The KYE™ Thesis. Why KYC, KYB, KYA and other category-based verification tools cannot govern delegated AI action. Why post-facto stitching from IAM, OAuth, SIEM and GRC fails at machi

The KYE Protocol™ platform in 8 modules: Entity Registry, Authority Gateway, Purpose & Scope, Decision Maps, Evidence Packs, Replay Proofs, Data Purpose Binding, Edge Governance.

Nine flows, one six-step trace — Nine real-world KYE Protocol™ use cases — high-value payments, custody break-glass, EU AI Act docs, HIPAA chart review, NIS2 incident response, FedRAMP RAG, claims tri

who benefits when AI agents come under one open authority and evidence standard, and what does that look like for each role in society?

Why KYE™: per-feature table contrasting the without-KYE™ gap with the with-KYE™ outcome and the framework requirement satisfied (EU AI Act, DORA, SEC 17a-4, HAARF, etc.).

KYE™ Widgets: 19 embeddable governed widgets — authority gate, evidence replay, decision map, consent receipt and more — that drop KYE™ authority into any partner site. Browse the catalogue here.

The KYE Protocol™ sales deck has moved to sales.kyeprotocol.com.

KYE Protocol™ vs Microsoft’s Agent Governance™ Toolkit: KYE™ is the vendor-neutral authority layer that proves who was allowed to act, Replay-Proof™ from public keys alone, across any agent stack.

What is the KYE Runtime Proxy Adapter™? It turns your runtime proxy or LLM gateway into a Policy Enforcement Point that calls the KYE™ decision inline and enforces the authority verdict at the wire.

What is KYE Site Authority™? A free, non-fakeable scan scoring how a site discloses its authority and evidence to AI agents across six dimensions, with a public registry and a badge. Not a truth score.

Which turn-key KYE™ bundle fits my sector, role, jurisdiction? KYE Starter Packs™ — 10 canonical packs pre-binding the right rule packs, sector packs, dictionaries, comms, widgets, purposes.

procurement team: how do you let AI help run a tender while every action — score, shortlist, award, dispute — stays admitted under a named officer, with evidence you can replay in a challenge?

What is the KYE™-Powered Directory™? The public registry of organisations that adopt KYE Protocol™ and Agentic Governance™ — listed only after explicit public consent.

Click any sector — banking, payments, healthcare, pharma, maritime, energy, defense, RegTech

Open or proprietary AI governance? Proprietary asks you to trust a closed scoring box; KYE Protocol™ is verifiable — open schemas, Apache-2.0, every decision Replay-Proof™ from a public key.

Who authorised the benefits decision that hit this family? KYE Protocol™ binds every benefits action to layered rights-bounded authority, pauses enforcement while citizens challenge, and proves it.

Who allowed the AI agent to list, reprice, offer or release a deposit? KYE Protocol™ admits each real-estate action under a live mandate, holds irreversibles for named sign-off, and seals the proof.

What is selective AI sovereignty? Strategic control over AI dependencies across data, models and infrastructure in proportion to risk. KYE™ proves those controls actually hold when AI acts.

How does KYE Protocol™ govern self-improving AI? Not by solving recursive self-improvement, but by revalidating an agent

AI agent skills are a new attack surface — 969 malicious ones in a year. A scanner says a skill is clean; KYE™ proves the clean skill stayed in its authority — evidenced and final.

Where do I start with KYE Protocol™? Pick the outcome you need — agent auditability, runtime approval, or evidence replay — and each solution routes you to the right authority capability.

What is Sovereign Execution™? Data sovereignty answers where AI runs; Sovereign Execution™ governs who is allowed to act on that decision — proven from public keys, above confidential compute.

What is the KYE™ Tech & AI Due-Diligence Profiler? It turns a tech-stack and AI inventory into a deterministic, cited gap report against the framework registry — every gap traced, never guessed.

Where does KYE™ sit in the agent-protocol stack? Above the protocols — MCP and A2A carry the calls; KYE Protocol™ decides whether each call is admissible and proves it. It does not replace them.

What is the Authority Simulator™? Set a scenario and watch KYE Protocol™ admit or refuse an AI action at the moment — the action climbs the chain, Purpose to Finality, or stops at a refusal.

What is the business case for Authority Finality™? Approvals and policies don

What is the KYE™ Agent Authority Stack? The authority + evidence + finality layer above any agent runtime — purpose-bound, replay-verifiable, suspendable — so every agent action is regulator-provable.

What is the KYE Policy Resolver™? The adapter that delegates raw allow/deny to any policy engine while KYE™ keeps purpose-bound authority, evidence and finality above it — provable from public keys.

Who owns the authority-to-finality centre of the AI stack? KYE Protocol™ owns, defines and leads it as Authority Finality™. Every other layer — observability, identity, evidence — is an input.

What free tools does KYE Protocol™ offer? A self-serve toolbox — Authority Risk Profiler, Authority Diagram, readiness test, sandbox, and KYE Lens™ — showing KYE™ working in minutes, no sign-up.

how do you start with the KYE Protocol™ rail without lock-in? Wrap your agent, run shadow mode, and try the sandbox before committing.

what is the KYE Protocol™ rail and why does it exist? Start with the concepts, glossary, and reference — the learn surfaces that explain the accountability rail.

Where do I see what

Can I see KYE Protocol™ actually running? This video library holds recorded runs of a governed agent deployed, refused out of scope, and its Evidence Pack™ trail opened and verified.

What does KYE Protocol™ offer, free vs paid? This catalogue lists every offering — tiers, products, add-ons, developer, programs, services and connectors — each marked free, paid or contact.

What does KYE™ do for Kaggle datasets and models? It binds the artifact to its AI Bill of Materials and the obligations its use carries, so you can prove it is governed for regulated deployment.

What does KYE™ do for Hugging Face models? It binds a model to its AI Bill of Materials and the obligations its use carries, so you can prove the model is governed for regulated deployment.

Honest status spec, implementation, and the service that doesn t exist — Operational targets KYE Protocol™ services run under. SLA tiers (99.9% / 99.95% / 99.99%), RTO/RPO per component, incident seve

Where are the per-stakeholder sample reports? On the Example reports shelf — one signed report envelope per persona (auditor, board, CISO, DPO, regulator and more), each verifiable offline.

In-browser KYE Protocol™ sandbox. Build an /v1/runtime/authorize request, see the assembled JSON, copy the curl, see a deterministic stub Decision Map™ response. No installation, no signup.

How does KYE™ work with Weights & Biases? Connect your W&B registry; when an agent

How does KYE™ govern AI at the inference boundary? A KYE™ PEP an OpenAI-compatible inference gateway (NVIDIA NIM, Triton, vLLM) consults before running the model — admit, block, escalate or quarantine.

A trace records what an AI agent did; it holds no grant proving the action was authorised. Authority is decided at the boundary — that is Authority Finality™.

AI governance is converging on a single structural conclusion: written policy and pre-deployment assessment are necessary but not sufficient.

Why must governance become executable as AI moves exponentially? Policy cycles take years; capability compounds in months — the execution boundary is the only layer fast enough.

Twelve do

A German court has held that an AI provider is responsible for the answers its AI presents, and that the responsibility cannot be shifted to the reader — reporting based on publicly available…

A financial-stability regulator has, in effect, told the market that a paragraph of instructions is not a control — reporting based on publicly available sources, not legal or compliance advice.

An API key grants reach to an endpoint; it never grants a per-action verdict on whether the actor was authorised. Authority is decided at the boundary — that is Authority Finality™.

In the Authority Court, the defendant is the agent

What is Authority Governance™? The category KYE Protocol™ defines: governing who is allowed to let an AI take a consequential action — the authority layer above describe-and-monitor AI governance.

How do I get certified to build governed AI agents? Earn a KYE™ certificate — the Builder credential or its Insurance specialisation — by building an agent whose Evidence Pack™ replays, not by quiz.

Canonical definitions for AI governance terms — AI governance, delegated authority, Purpose Permission, evidence pack, Replay-Proof, authority gap, shadow mode, four-eyes, and more.

What is ISO/IEC 42001 and how do you certify — clauses 4-10 explained, Annex A

KYE Authority Fellows™ is a free, self-serve authority certificate program for women, minorities, and developing-country AI practitioners — Bronze to Gold via credited contributions.

The KYE Authority Pulse™ is the weekly bulletin of what changed inside the KYE Protocol™ canon — new governance chapters, new frameworks under mapping, new commercial products, and new governed…

KYE Community™ is a zero-cost open community for AI practitioners learning to prove agent authority — free KYE Learn™ courses, the open-source Constitution Kit, and the Authority Fellows™ program.

KYE Governed Proposal Authority™ turns a SERPRO governed data-query partnership context into a deterministic, fully-cited, replay-sealed proposal.

KYE Learn™ — the canonical education centre for AI governance, agentic AI risk, model risk frameworks, and players landscape.

The six clickable KYE Protocol™ primitives — Identity, Authority, Scope, State, Audit, On-Behalf-Of — each with its canonical schema, endpoint, JSON example, decision role, audit event

Frequently asked questions about KYE Protocol™ — Authority Finality™, conformance, deployment, integration, regulation, governance, profiles, roadmap.

Plain-English definitions of every KYE Protocol™ term: Authority Graph™, Decision Map™, Authority Finality™, on-behalf-of, attenuation, cascade, evidence pack, ePDP, PEP / PDP, decision codes

Governance for the AI Web reduces Systemic Authority Risk™ — who authorised what across the web of humans and AI agents — via four products over the existing KYE™ rails.

Canonical KYE Protocol™ vocabulary: entity types, action types, decision codes, reason codes, capability kinds, side-effect levels, data classes, signal types, redaction fields, taxonomies

Dictionaries are versioned lists of canonical terms — definitions, categories, severities, control mappings. Rules reference dictionaries by reason_code; the Rules Gateway™&trade

Observability watches what an AI agent does; it never decides whether the agent was authorised to act. Authority is settled at the boundary — that is Authority Finality™.

Where can I read KYE Protocol™

As agentic tools get better at execution, the durable value moves to judgment — and judgment, made enforceable at the moment of action, is what governance is.

Healthcare organisations are adopting AI into clinical and operational decisions — triage, diagnosis support, documentation, scheduling, prior authorisation — while sitting on the most sensitive…

Financial institutions are deploying AI into decisions that regulators already supervise — creditworthiness, fraud, market and model risk — faster than their governance programmes can keep up.

The industry now agrees on how to secure an enterprise AI agent — and that agreement stops one layer short of authority.

How does SR 11-7 model risk guidance apply to AI agents — the four classic categories extended to action risk, the three-line model, documentation expectations, KYE Protocol™ mapping.

A successful AI-agent action is not a legitimate one. The Authority Court puts the action on trial and asks whether it was authorised, in scope, at t=0 — and the verdict is Authority Finality™.

The loudest AI-governance fear is the rogue agent.

What does the EU AI Act actually demand of AI agents — risk tiers, prohibited practices, high-risk obligations, GPAI rules, the four obligations that bite hardest, timeline 2025-2027.

The KYE Protocol™ Blog argues doctrine: the layers mistaken for authority — observability, traces, permits, identity, keys — and the boundary that separates each from Authority Finality™.

What is the Map of KYE™? The protocol drawn as a cypress — its canopy is the chain of legitimacy (Purpose to Finality), and selecting a stage lights that foliage.

Digital-rights enforcement has moved from "do you have a privacy policy?" to "prove what happened" — and most organisations cannot answer at execution time.

What is the Research Program? Governed publishing — no claim without a cited source, every report evidence-sealed and replay-verifiable; institutes co-author via the Publishing Authority Track™.

The return on AI is no longer in doubt — and that is precisely why governance is now the constraint that matters.

There is a measurable gap between what organisations say about their AI governance and what they can actually prove — and that gap is invisible until the first incident, when it becomes the whole…

What is the trust layer for consequential action? The layer that decides whether an action may proceed, records why, and makes that authority final and provable — KYE Protocol™.

The headline insider threat of 2026 is not a disgruntled employee — it is an AI agent that was manipulated into turning against the organisation that runs it.

Who plays in AI governance — GRC suites, AI-risk newcomers, model-eval platforms, agent-governance specialists — where each falls short and how to choose.

Who is accountable for an AI answer? The party that presents it as authoritative — KYE Protocol™ records the authority and cited basis so it is provable. Reporting, not legal advice.

KYE Protocol™ Acceptable Use Policy. Prohibited uses, prohibited content, automated-behaviour limits, security obligations, abuse reporting, suspension.

KYE Protocol™ brand kit: master logo, indigo brand colour (#6366f1), charcoal ink, type, spacing, clear-space and the misuse list. Source of truth for every surface.

Upgrade your build here s what s new — KYE Protocol™ chronological release notes. v1.0.0 frozen April 2026; rolling v1.0.x patch series; v1.1 preview profiles in flight. Per-release scope, breaking-ch

KYE Protocol™ Cookie Policy. No first-party cookies, no analytics or advertising trackers; a few localStorage keys for theme and update read-state; strictly-necessary host security cookies only.

Everything is open — Plain-English legal page: Apache 2.0 across schemas, SDKs, OpenAPI, conformance, reference Gateway. Patent-track mechanism algorithms and KYE™ trademarks are protected. FAQ on lic

KYE Protocol™ Mutual Evaluation Agreement: compulsory clickwrap confidentiality and no-competing-use terms accepted in every pilot, PoC, partner, trainer and auditor intake, pinned by version hash.

Public-sector portals, regulator data portals, smart-city hubs, research catalogues, health data catalogues, NGO portals, infrastructure transparency portals

KYE Protocol™ press kit: boilerplate, logo, screenshots, contact for journalists / analysts / partners.

KYE Protocol™ Privacy Policy. Data controller: KYE Protocol™ Ltd. Data we collect, lawful basis, retention, sub-processors, data subject rights under GDPR Articles 15-22, international transfers

v1 — KYE Protocol™ roadmap with dated milestones — v1.0 frozen April 2026, v1.0.x patch series, v1.1 preview profiles (Conformance Certification, Authority Graph™, Payload Trust, Self-Audit Attestation

Every page on the KYE Protocol™ public site, with a one-line description of each.

KYE Protocol™ Terms of Service — minimum-viable B2B SaaS terms for the Audit Pilot program. Governing law: England & Wales. Notices: [email protected].

Interactive 3D platform map: every canonical KYE™ component as a dot on a rotatable dotted globe (longitude=stage · shell=rail), coloured by connectivity health — islands & broken chains.

What does each colour mean across KYE Protocol™? Every top-level component family has one WCAG-AA hue, light and dark: sector blue, framework violet, program teal, agent amber, sku green, and more.