--- title: "KYE Protocol™ — Schemas · step 4 of the KYE™ stack" description: "KYE™ schemas — JSON Schema 2020-12 contracts that validate every payload at runtime. Step 4 of the canonical 8-step KYE™ stack" url: https://kyeprotocol.com/schemas/ lang: en source: "KYE Protocol" --- > KYE™ schemas — JSON Schema 2020-12 contracts that validate every payload at runtime. Step 4 of the canonical 8-step KYE™ stack Step 4 · Schemas # JSON Schema. Bytes on the wire. Steps 1–3 name, sort, and define meaning. Step 4 ships the wire contract. You get 1165 JSON Schemas 2020-12 files with stable `$id` URLs, walked by ajv on every CI run. 1 · What ships ## 103 published schemas. Each has an example. Every schema is versioned and namespaced under `https://kyeprotocol.com/schemas/`. Each one has at least one example payload in `public/examples/`. The validator runs in CI and fails the build on any drift. - **Core:** `entity`, `delegation`, `scope`, `policy-decision`, `runtime-event`, `trust-domain`, `identifier`, `relationship`, `access-right`, `credential`, `attestation`, `audit-event`, `evidence-pack`, `signal`, `transfer`, `compliance-card`. - **Continuity Module™:** `continuity-profile`, `continuity-context`, `intent-trace`, `continuity-decision`, `agency-drift-event`, `continuity-evidence-pack`. - **Discoverability Profile™:** `discoverability-profile`, `directory-entry`, `discovery-query`, `discovery-result`, `discovery-policy`, `authority-path-discovery`, `discovery-audit-event`. - **Semantic Registry:** `ontology-term`, `ontology-relationship`, `ontology-mapping`, `semantic-assertion`, `jsonld-context`. - **Operating Model™:** `operating-model-profile`, `use-case-intake`, `readiness-assessment`, `entity-authority-record`, `authority-gate`, `commit-boundary`, `review-path`, `training-record`, `adoption-evidence-pack`. - **Assurance Card:** `assurance-card-profile`, `assurance-card`, `human-involvement-plan`, `provenance-evidence`, `assurance-review-cycle`, `decommissioning-plan`. - **Classification + Risk:** `kye.data_classification_assignment.v1`, `kye.risk_assessment.v1` — signed envelopes; the runtime constructions are proprietary and are not disclosed in this repository. - **Search · Memory · Data Flow:** `kye.search_result.v1`, `kye.agent_memory.v1`, `kye.data_flow_graph.v1` — signed envelopes returned by named sub-engines (KYE™ Native Search Engine™, KYE™ Memory Engine™, KYE™ Data Mapping Agent™); the runtime constructions are proprietary and are not disclosed in this repository. - **Reporting:** `kye.report.v1` — signed envelope returned by the KYE™ Reporting Engine™. The synthesis construction is proprietary and is not disclosed in this repository. 2 · Why JSON Schema 2020-12 ## One contract. Three audiences. Developers want types. Auditors want a JWS (JSON Web Signature) over a known shape. Regulators want a stable cite. JSON Schema 2020-12 gives all three from one file. - **Developers** bind the schema to TypeScript and Python types via the KYE™ SDK™. - **Auditors** verify each Evidence Pack™ by hashing the payload against the schema digest. - **Regulators** cite a stable URN under EU AI Act Annex IV and ISO 42001 Annex B. - **Buyers** compare vendors against the same conformance fixtures, end of story. 3 · How you wire it in ## Three patterns. Five minutes each. Fetch the JSON. Reference it from OpenAPI 3.1. Verify the webhook signature, then validate the body against the schema. The same files feed your SDK clients and your audit reports under DORA Art. 6. (Signature algorithms are proprietary and not disclosed here; verification SDK helpers are published.) - **Bind a REST payload.** Add `$ref` to `entity.json` in your OpenAPI 3.1 spec. - **Verify a webhook.** Check the JWS, then validate the body against `audit-event.json`. - **Ship an Evidence Pack™.** Concatenate inputs, the Decision Map™, and the seal under `evidence-pack.json`. 4 · Reproduce ## Walk every example. In under a minute. Clone the public examples repo, install, run the test. The same harness lives in CI on every push. ``` git clone https://github.com/KYE-Protocol/examples cd examples npm ci && npm test # 103 ok, 0 failed ``` Where to go next ## Continue the stack → Step 3 holds the meaning. Step 5 turns these named objects into the queryable graph an auditor or regulator can replay. [← Step 3 · Ontology](https://kyeprotocol.com/ontology/) [Step 5 · Knowledge graph →](https://kyeprotocol.com/knowledge-graph/) [Step 2 · Taxonomies](https://kyeprotocol.com/taxonomies/) ## Ready to see your AI agents flagged? Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks. [Apply for pilot →](https://kyeprotocol.com/pilot-apply/) [Try the sandbox →](https://kyeprotocol.com/sandbox/demos/) Canonical KYE™ surfaces referenced on this page: [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) · [KYE Protocol™](https://kyeprotocol.com/).