---
title: "KYE Protocol™ — Profiles — 10 canonical conformance modes"
description: "KYE™ has 10 canonical profiles, locked by constitution. Profiles define the conformance contract an implementation MUST support"
url: https://kyeprotocol.com/profiles/
lang: en
source: "KYE Protocol"
---

> KYE™ has 10 canonical profiles, locked by constitution. Profiles define the conformance contract an implementation MUST support

KYE Protocol™ · architecture

# KYE Protocol™ profiles — the 10 canonical conformance modes

Ten canonical profiles. Locked at v1. Sector packs and rule packs do the specialisation.

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

Plain take

## Plain take

Ten profiles. Locked at v1. Sector packs do the rest.

- One profile per kind of entity.
- Each profile has a schema. Each schema has tests.
- Sector packs add fields. Rule packs add checks.
- Maps to SOC 2, ISO 27001, OSCAL.

## The 10 canonical profiles

What it is. Why it matters. What to do next.

Per — the public profile list is locked. Adding an 11th profile requires a constitution amendment.

| # | Profile | Conformance contract |
| --- | --- | --- |
| 1 | **KYE™ Core Profile™** | Universal contracts: Entity, Principal, Actor, Purpose, Authority, Scope, State, Rule, Decision, Evidence, Replay, Manifest. |
| 2 | **KYE™ Runtime Authority Profile™** | How actions are evaluated at the Runtime Gateway. The seven-question contract (verified / allowed / dataset / jurisdiction / policy / risk-class / auditable). |
| 3 | **KYE™ Evidence & Replay Profile** | How actions are proven. Evidence Pack™, Decision Map™, Replay Proof™, signature + hash-chain conventions. |
| 4 | **KYE™ High-Assurance Profile™** | Banking-grade + critical-infrastructure-grade hardening — stricter floors, dual-channel sign-off, hardware-rooted signing. |
| 5 | **KYE™ Edge Governance Profile™** | Disconnected / degraded / restricted operation. Compiled Authority Bundle + Edge Arbiter + Safety Floor + Offline Evidence Log. |
| 6 | **KYE™ MCP / Agent Runtime Profile™** | How MCP tool calls + agent-to-agent delegation are evaluated. |
| 7 | **KYE™ Connector Profile™** | How external systems (CKAN / Stripe / Clerk / Salesforce / Splunk / Slack / GitHub) integrate. |
| 8 | **KYE™ Sector Profile™** | Meta-profile for sector packs. Declares the 7-component sector-pack contract. |
| 9 | **KYE™ Conformance Profile™** | How an implementation proves it conforms — test fixtures, conformance report, certification badge. |
| 10 | **KYE™ Manifest Profile™** | How installable / verifiable / billable units (connectors, widgets, SKUs, rule packs, sector packs, MCP tools) declare themselves. |

[View profile specifications →](https://github.com/KYE-Protocol/app/tree/main/profiles)

## 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: [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) · [KYE™ Edge Governance™](https://kyeprotocol.com/glossary/) · [KYE™ MCP Server](https://kyeprotocol.com/mcp/) · [KYE Protocol™](https://kyeprotocol.com/).