KYE™ developer playbooks
Provider-agnostic, patent-safe patterns. Each playbook is pure pattern plus links to public schemas and examples — zero mechanism content. Read one, then scaffold it from a starter template.
Developer playbooks, step by step
Demo dataYou learn: What happens at each step. You can: Step through it.
-
Step 1 of 4
KYE Protocol™
Govern your agent
Emit the §0.3 evidence family and bind the agent under §52 — the minimum a governed agent owes.
-
Step 2 of 4
KYE Protocol™
Authority finality
The discover → authority → purpose → evidence → finality chain that makes an action defensible.
-
Step 3 of 4
KYE Protocol™
Policy-resolver integration
Map Cedar / OPA / Cerbos verdicts onto the locked KYE™ DecisionOutcome set — provider-agnostic.
-
Step 4 of 4
KYE Protocol™
Agent-gateway + KYE™
Wrap a cloud agent-gateway verdict with a KYE™ Evidence Pack so the decision is replay-provable.
How this widget is built
- Demonstrates
- KYE Protocol™
- Components
- The steps this page describes
- Flow
- Each step in order, as the page sets it out. Architecture diagram
- Used on
- /oss/playbooks/: On this page, after its opening.
Govern your agent
Emit the §0.3 evidence family and bind the agent under §52 — the minimum a governed agent owes.
Authority finality
The discover → authority → purpose → evidence → finality chain that makes an action defensible.
Policy-resolver integration
Map Cedar / OPA / Cerbos verdicts onto the locked KYE™ DecisionOutcome set — provider-agnostic.
Agent-gateway + KYE™
Wrap a cloud agent-gateway verdict with a KYE™ Evidence Pack so the decision is replay-provable.
Canonical KYE™ surfaces referenced on this page: Evidence Pack™.