KYE Protocol™ — the Entity Trust Control Plane for AI-native systems.

Every AI inference becomes a governed, evidenced, replayable event — without replacing IAM, OAuth, your API gateway, GRC, or SIEM.

KYE™ adds a delegated-authority, evidence, and runtime-decision layer on top of the stack you already run.

Categories verify. Protocols govern.

KYC verifies the customer. KYB verifies the business. KYA verifies the agent. The natural next step was KYX — know your X. But KYX is still verification at onboarding. Once every component of a digital system — human, agent, model, dataset, tool, downstream API — can act under delegated authority, governance has to be a protocol, not a stitched-together report.

• verified_userKYC / KYB / KYA — verify a category of actor once, at onboarding.
• trending_upKYX — the generalisation. Works for new categories, still a verification step.
• policyKYE™ — runtime governance. Every action governed, every inference evidenced, every delegation replayable.

IAM controls access. KYE™ governs every inference.

Seven questions every AI-native call must answer.

The KYE Runtime Gateway™ resolves each one before the inference reaches downstream systems.

Start with evidence. Move to enforcement when ready.

Per-inference accountability for enterprise AI.

Every inference resolves to a canonical entity chain.

Entity hierarchy v3.1 (constitution §1a, locked 2026-05-15). The Runtime Gateway answers the seven questions against the leaf kye:endpoint:….

KYE Runtime Gateway™ — the canonical answerer.

The protocol governs itself.

Constitution §0.3 (adopted 2026-05-15). Every CI run, deploy, schema migration, secret rotation, and domain binding is governed by the same engines that govern customer inferences.

Ten engines × eight rails — one protocol.

Engines are the computation primitives. Rails are the user-facing surfaces that orchestrate them. Locked by constitution §14.

Every inference produces replayable evidence.

{
  "evidence_pack_id": "kye:evp:acme.example:01JYEVP0...",
  "issued_at":        "2026-05-15T13:31:00Z",
  "endpoint_id":      "kye:endpoint:acme.example:claude-sonnet-eu-2",
  "actor_principal":  "kye:prin:acme.example:agent:ops-copilot",
  "runtime_gateway": {
    "mode":        "strict",
    "q1_verified":  "true",
    "q2_allowed":   "true",
    "q3_dataset":   "approved",
    "q4_jurisdiction": "eu-west",
    "q5_policy":    "compliant",
    "q6_risk_class": "high-suitable",
    "q7_auditable": "sealed"
  },
  "control_refs": [
    "EU_AI_ACT.AIA_HIGH_RISK_LOGGING",
    "EU_AI_ACT.AIA_HUMAN_OVERSIGHT",
    "DORA.ICT_RISK_REGISTER",
    "ISO_42001.AIMS_8_2"
  ],
  "risk_score": {
    "value":        12,
    "out_of":       100,
    "signature_suite": "ed25519-2025"
  },
  "replay_context_seal": "sha256:9c8a..."
}

Beyond local validity.

What each audience gets.

Six productised pilots. Fixed scope. Closed registration.

Every pilot has its own onboarding agent, demo seed pack, dashboard preset, Evidence Pack™ sample, and signed final report. The commercial menu is sent to qualified applicants by email — not published.

Start with one workflow.

1. Pick a pilot. Define one AI workflow and the model endpoint that backs it.
2. Bind the Runtime Gateway™ in Shadow mode — no production block.
3. Generate Evidence Packs™ on every inference. Receive the signed final report.
4. Surface authority gaps, jurisdiction drift, risk-class violations.
5. Convert pilot → annual at the right tier. Pilot fee credited at signature.

After you apply, the qualification team responds within 2 business days with the full commercial menu, conversion terms, and pilot scope draft.