KYE Protocol™ · architecture
KYE Protocol™ manifests — the installable / verifiable / sellable layer
Manifests bind purpose to permission. Each call cites one. Revoke the manifest, revoke the call.
13 canonical manifest types
What it is. Why it matters. What to do next.
- KYE™ Core Manifest™ — universal object model header
- KYE™ Profile Manifest™ — declares a profile + its required schemas + its conformance tests
- KYE™ Connector Manifest™ — declares a connector + its supported modes + auth + evidence emit classes (CKAN connector ships first)
- KYE™ Widget Manifest™ — declares an embeddable widget + its four-file contract
- KYE™ MCP Tool Manifest™ — declares an MCP tool + its input/output schemas + governance flags
- KYE™ Sector Pack Manifest™ — declares a sector pack + its rule pack refs + control frameworks
- KYE™ Proof Bundle Manifest™ — Phase 6 — declares a portable Authority Proof Bundle™
- KYE™ Edge Authority Bundle Manifest™ — declares a Compiled Authority Bundle for edge deployment
- KYE™ SKU Manifest™ — declares a commercial SKU + its entitlements + Stripe binding
- KYE™ Consultant Manifest™ — declares a consultant listing + specialism + attribution
- KYE™ Conformance Manifest™ — declares conformance test fixtures + certification outputs
- KYE™ Deployment Manifest™ — declares a deployment topology
- KYE™ OSS Package Manifest™ — declares an open-source package + its Apache 2.0 / CC-BY-4.0 split
Every manifest is signed at minting time using a vendor-published signature recipe. The Manifest Registry Engine indexes them. CI gate scripts/gates/rule-pack-canonical.mjs already enforces canonical-first integrity for rule pack manifests.
Companion surfaces
What it is. Why it matters. What to do next.
Inside KYE Protocol™ the layers are these: profiles define is; rule packs define does; dictionaries define means; manifests define installable / verifiable / sellable; engines execute; the Rules Gateway™ enforces.
Canonical KYE™ surfaces referenced on this page: KYE™ MCP Server · KYE Protocol™.