--- title: "KYE Protocol™ — Event-driven by constitution" description: "KYE™ is the only AI-governance protocol that proves it isn't post-facto. Every privileged action emits a signed evidence envelope at the moment of the…" url: https://kyeprotocol.com/event-driven/ lang: en source: "KYE Protocol" --- > KYE™ is the only AI-governance protocol that proves it isn't post-facto. Every privileged action emits a signed evidence envelope at the moment of the… Constitutional property # Event-driven by constitution. You can claim to be event-driven. We _prove_ it. Every privileged action in KYE Protocol™ emits a signed evidence envelope **at the moment of the event**. The Event Registry™ is the single source of truth — 48 declared event families today. A compile-time CI gate verifies every `post_facto_forbidden` consumer has no cron. The same property is what auditors look for under **EU AI Act** Art. 12, **ISO 42001** A.6.2, and **SR 11-7** ongoing-monitoring. Hidden cron jobs fail the build. [Apply for a pilot](https://kyeprotocol.com/pilot-apply/) [Read the whitepaper](https://kyeprotocol.com/whitepaper/#governance) 38 event families · 16 post-facto-forbidden · p99 ≤ 5s SLO · CI-gated ## Why this is the moat. Every compliance / governance / audit vendor in the market today is **cron-based**. Vanta polls. Drata polls. AWS Config polls. The customer's audit trail is, by definition, stale by however long the cron window is — minutes for the fastest, hours for the typical, days for the worst. KYE Protocol™ inverts the model. The protocol does not collect evidence on a schedule; the protocol _is_ the moment evidence is created. Every action that touches a customer system emits a signed envelope synchronously, on the critical path of the action itself. The audit chain is not a log of what happened — it is the **same operation** as what happened. This is enforced architecturally, not aspirationally. The Event Registry™ at `internal` declares every event family. Each entry carries a `post_facto_forbidden` flag and a closed-set `delivery` mode. A compile-time CI gate (`event-registry-canonical`) blocks any code merge that introduces a hidden cron trigger on a post-facto-forbidden event. Customers see this because regulators see it: the gate's output is part of the deployment evidence chain. ## How we compare. | Property | AWS Config / Vanta / Drata / Wiz | Kafka / EventBridge / Cloudflare Queues | KYE Protocol™ | | --- | --- | --- | --- | | Event substrate | Cron polling | Event-driven by default | Event-driven; cron is structurally rejected when post-facto-forbidden | | Property enforcement | Runtime metric, post-hoc dashboard | Substrate choice; no enforcement of "this consumer must NOT be cron" | Compile-time CI gate; build fails on hidden cron | | SSOT for event taxonomy | None (vendor-internal) | None (per-app) | `kye.event_registry.v1` manifest, public schema, public listing | | Regulator-readable | Vendor's word | N/A | Signed evidence envelope per gate run; offline-verifiable | | Audit-trail staleness | Cron-window-bound (typical: hours) | Substrate-bound (typical: ms) | Declared per event: `max_latency_seconds`, verified by SLO | ## What's declared. 38 event families currently live in the canonical registry. Sample: - **Cloudflare Logpush** (workers\_trace\_events, http\_requests, firewall\_events) — streamed via R2 + bridge Worker to the public `logs` branch. SLO: ≤ 5s. - **GitHub Actions** (workflow\_run, deployment\_status) — webhook → bridge → audit chain. SLO: ≤ 10s. - **Clerk** (user.created, user.updated, session.created) — webhook → audit chain. SLO: ≤ 3s. - **Stripe** (invoice.paid, invoice.payment\_failed) — webhook → billing-state + audit chain. SLO: ≤ 5s. - **Internal runtime** (audit-chain append, reconciliation verdict, GovernedUI™ action proposal, directory index delta, etc.) — at-write or queue-driven. SLO: ≤ 5s. - **Cron-tolerated exceptions** — explicitly acknowledged (daily audit archive, hourly D1 backup, periodic DR test). Each is named in the registry; hidden crons fail CI. The full registry is public-machine-readable at `internal` (mirror queued for `/event-registry.html` on this site). ## How to verify it for your audit. If you are a regulator, an external auditor, or a Chief Risk Officer asking "how do I know KYE™ is not post-facto?", you have three independent verification paths: 1. **Read the registry.** `internal` — every event family, every consumer, every delivery mode. 2. **Run the gate yourself.** Clone the repo, run `node scripts/gates/event-registry-canonical.mjs`. Inspect the output — counts, drift, exceptions. 3. **Re-derive the signed evidence envelope.** Every CI run that passes the gate emits a signed gate-result envelope. Verify offline with our public key. This is not a vendor promise. It is a constitutional property of the protocol, verifiable by inspection. ## Ready to ship banking-grade audit trails that aren't stale? Pilot in 8–12 weeks. Signed evidence the day you deploy. [Apply for a pilot](https://kyeprotocol.com/pilot-apply/) [Or start with a PoC](https://kyeprotocol.com/poc/) Canonical KYE™ surfaces referenced on this page: [KYE Protocol™](https://kyeprotocol.com/).