# Execution Protocol

> Infrastructure for safe autonomous agents. Deterministic execution, policy
> enforcement, and cryptographic receipts — one structured message in, one
> verifiable outcome out.

The Execution Protocol turns structured agent intents into committed actions
with proof. Every action passes a deterministic pipeline (token validation →
schema → boundary → completeness → math → execute → commit auth split →
receipt) and emits a self-contained ES256-signed receipt that any third
party can verify offline.

## Get started

- [How it works](https://executionprotocol.dev/docs/concepts/how-it-works) — the deterministic pipeline
- [Sandbox](https://executionprotocol.dev/demos/sandbox) — try it in the browser, no signup
- [Verify a receipt](https://executionprotocol.dev/verify) — paste any sandbox receipt and check the signature

## Concepts

- [Authorization Boundary](https://executionprotocol.dev/docs/concepts/authorization-boundary) — pre-commit policy gates between LLM intent and deterministic action
- [Receipts](https://executionprotocol.dev/docs/concepts/receipts) — signed proof of every action
- [Delegation](https://executionprotocol.dev/docs/concepts/delegation) — scoped authority chains
- [Architecture](https://executionprotocol.dev/docs/concepts/architecture) — system architecture
- [Protocol landscape](https://executionprotocol.dev/docs/concepts/protocol-landscape) — Execution vs A2A/MCP/ACP/REST
- [Threat model](https://executionprotocol.dev/docs/concepts/threat-model) — what we defend against

## Reference

- [Errors](https://executionprotocol.dev/docs/reference/errors) — sandbox error codes with remediation
- [Types](https://executionprotocol.dev/docs/reference/types) — shared types
- [Specification](https://executionprotocol.dev/docs/spec) — open protocol specification

## Demos

- [Sandbox](https://executionprotocol.dev/demos/sandbox) — split-pane interactive demo
- [Booking](https://executionprotocol.dev/demos/booking) — booking-DSL flow
- [Authorization Boundary](https://executionprotocol.dev/demos/boundary) — pre-commit block demo
- [Delegation](https://executionprotocol.dev/demos/delegation) — multi-party approval flow
- [Receipt verifier](https://executionprotocol.dev/demos/receipt) — receipt inspection

## Whitepapers

- [Whitepapers index](https://executionprotocol.dev/whitepapers) — position papers + technical briefs
- [The Action Layer](https://executionprotocol.dev/whitepapers/the-action-layer) — why agent infrastructure needs a fourth layer

## Blog

- [Blog index](https://executionprotocol.dev/blog) — engineering, customers, concepts, post-mortems
- [Blog RSS](https://executionprotocol.dev/blog/feed.xml) — subscribe via RSS
- [Why we built Execution Protocol](https://executionprotocol.dev/blog/why-we-built-execution-protocol)

## Optional

- [Security](https://executionprotocol.dev/security)
- [About](https://executionprotocol.dev/about)
- [Partnerships](https://executionprotocol.dev/partnerships)
- [Contact](https://executionprotocol.dev/contact)

## About this material

Patents pending. Public materials describe the protocol at a property level
only — what the system does and the assurances it provides. Implementation
details and term definitions appearing in public materials are illustrative
and non-limiting. The filed patent applications are the controlling
specifications; where a public document and a filed application use a shared
term, the application's definition controls.