---
title: "KYE Protocol™ — Manifests — installable / verifiable / sellable units"
description: "Every installable / verifiable / billable unit in KYE™ is a signed manifest. Connectors, widgets, SKUs, rule packs, sector packs, MCP tools, proof bundles…"
url: https://kyeprotocol.com/manifests/
lang: en
source: "KYE Protocol"
---

> Every installable / verifiable / billable unit in KYE™ is a signed manifest. Connectors, widgets, SKUs, rule packs, sector packs, MCP tools, proof bundles…

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.

[Apply for pilot →](https://kyeprotocol.com/pilot-apply/) [Read the docs](https://kyeprotocol.com/docs/)

## 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™](https://kyeprotocol.com/rules-gateway/) enforces.

- [Profiles — the 10 canonical conformance modes](https://kyeprotocol.com/profiles/)
- [Rule packs — behavioural logic](https://kyeprotocol.com/rule-packs/)
- [Dictionaries — canonical vocabulary](https://kyeprotocol.com/dictionaries/)
- [Sector packs — sector bundles](https://kyeprotocol.com/sectors/)
- [Manifests — installable / verifiable units](https://kyeprotocol.com/manifests/)
- [Rules Gateway™ — runtime enforcement](https://kyeprotocol.com/rules-gateway/)

Canonical KYE™ surfaces referenced on this page: [KYE™ MCP Server](https://kyeprotocol.com/mcp/) · [KYE Protocol™](https://kyeprotocol.com/).