EMILIA Protocol

EMILIA Protocol is a pair of individual IETF drafts and an open-source gate for checking an agent’s authority before a protected tool runs, keeping signatures, credentials, evidence and observed effects as separate facts.

Where it stands

As of 2026-10-08, the Agentic Standards Map records:

Two individual Internet-Drafts by Iman Schrock (EMILIA Protocol, Inc.) were current on 2026-10-08: draft-schrock-ep-architecture-03 (2026-09-06, Informational) and draft-schrock-action-evidence-boundary-07 (2026-09-25, Informational). The Apache-2.0 repository emiliaprotocol/emilia-protocol was created on 2026-03-13.

Why it matters to agents

The architecture draft “composes the Canonical Action Identifier (CAID), Authorization Evidence Chain (AEC), and Action Evidence Boundary (AEB)” and says “A valid signature, a current credential, a satisfied evidence requirement, and an observed effect remain different facts.” The README says “EMILIA Gate checks authority before a protected tool runs”; its example MCP payment server “refuses a call without approval, binds approval to the amount, currency, vendor, and destination”, and the README calls the example “a local demonstration” with “a mock payment tool”. …

Sources

• https://datatracker.ietf.org/doc/draft-schrock-ep-architecture/
• https://datatracker.ietf.org/doc/draft-schrock-action-evidence-boundary/
• https://github.com/emiliaprotocol/emilia-protocol
• https://mailarchive.ietf.org/arch/msg/agentproto/_-7ahBTxuzTScC_1yCTarPXsbzU/
• https://github.com/aaif/wg-identity-and-trust/issues/13

Status and relevance quoted, shortened, from the Agentic Standards Map by Francesco Marinoni Moretto, CC BY 4.0, https://frmoretto.github.io/agentic-standards-map/. The full entry, with every dated source, is in map.json under emilia-protocol.

Industry: security