Playbooks · concrete run-throughs

Run a KYE Protocol™ pilot from kick-off to signed evidence in three documented playbooks.

Each playbook is a concrete step-by-step run-through against the open KYE Protocol™ contract. No abstractions; every step names the schema, endpoint, evidence artefact, or rule pack involved. You can replay every step offline against the reference Gateway and the 708 example payloads in github.com/KYE-Protocol/examples.

Pick the playbook that matches your seat.

verified_user KYE™ Audit Pilot™ — 28-day run-through For the buyer evaluating KYE™: a 28-day, shadow-mode-only engagement that captures one named AI-agent workflow, signs an Evidence Pack™ for every decision, and outputs a signed pilot report. No production change. No regulatory exposure. Read the buyer playbook → science Vendor conformance run For a vendor advertising KYE™ conformance: how to run the 129-fixture pack against your gateway, generate a signed `conformance-report.json`, and post the verification record to the public registry. Self-attest at the L2 rung; pursue audit-firm attestation for L3 / L4. Read the vendor playbook → balance Regulator probe For a regulator or auditor verifying a KYE-anchored decision: how to take a `decision_id` produced in production and replay the full Authority Graph™ + Decision Map™ + Evidence Pack™ offline, using only the publisher's JWKS — no vendor cooperation required. Read the regulator playbook →

What every playbook shares.

  • Open contract. The 10 canonical profiles, 57 rule packs, 49 sector packs, 185 dictionaries, and 5 manifests are Apache 2.0. The 556 JSON Schemas have absolute `$id` URIs under https://kyeprotocol.com/schemas/ and ship with 282 validated example payloads.
  • Replayable evidence. Every governed action emits the §0.3 governance event family (kye.evidence.decision_map.v1, kye.replay.context_seal.v1, kye.evidence.pack.v1) to the per-tenant append-only WORM audit chain (D1 + object-store immutability (COMPLIANCE retention) per constitution §30).
  • Offline-verifiable. A third party holding only the publisher's JWKS can verify an Evidence Pack™ without any further vendor cooperation. This is the same posture used by SCITT receipts and by TUF for software supply chain.
  • IP-safe public surface. The mechanisms (decision-binding algorithm, stop-cascade, replay-proof construction, meaning-continuity scoring) remain proprietary. Every public artefact is IP-safe by construction; the ip-safety-scan gate blocks mechanism keywords from leaking into the public mirror.
  • KYE Native Search Engine™. Signed search result envelopes replayable offline from public keys alone. Mechanism is proprietary and is not disclosed in this repository.
  • KYE Reporting Engine™ at period close. Per-framework compliance report synthesis. Signed report envelope, replayable offline. Auto-delivery via reports@kyeprotocol.com on opt-in cadence. Mechanism is proprietary and is not disclosed in this repository.

How to engage.