emiliaprotocol/emilia-protocol
Authority control plane for autonomous work. EMILIA Gate enforces finite customer-owned mandates at protected executor boundaries; the open protocol keeps evidence verifiable.
What it solves
EMILIA Protocol provides a security boundary for autonomous agents to prevent them from "quietly widening" their operating mandate. It solves the control problem where agents can perform consequential actions (like moving money, changing code, or altering infrastructure) without explicit, durable, and verifiable authority for each specific action.
How it works
EMILIA implements a "toll booth" (Gate) at the boundary where an agent's intent becomes a consequential action. It separates identity (who is calling) from authority (what exact work is allowed).
- Mandate: A human or institution defines a finite operating mandate (limits, budget, expiry).
- Exact Work: The system binds the method, target, and material fields of a request into a canonical executable object.
- Verify and Reserve: The Gate verifies the authority required for that exact action, reserves that authority before the provider is entered, and permits only one admitted provider attempt to prevent blind retries.
- Human Authority: When required by policy, the system can trigger a WebAuthn/passkey sign-off for a specific action.
- Truthful Result: It generates portable evidence (Trust Receipts) of what was admitted and observed, treating lost responses as
INDETERMINATEstates that require reconciliation rather than automatic retries.
Who it’s for
- AI Agent Developers: Those building autonomous workers that need to be wrapped in a security layer to ensure they stay within bounded capabilities.
- Enterprises: Organizations requiring durable authority state and audit trails for agent-driven financial operations or infrastructure changes.
- Security Auditors: Users who need portable, verifiable evidence of agent actions.
Highlights
- Preventive Control: Blocks unauthorized actions before they reach the provider credential.
- Emergency Authority Freeze: Allows owners to stop new consequences without needing to terminate the agent's computation.
- Causal Evidence: Uses a system of Trust Receipts and Trust Profiles to provide offline-verifiable evidence of work.
- Causal-Action Identifier (CAID): Binds authority to the exact material fields of an action.
- MCP Server Support: Includes a Model Context Protocol (MCP) server for easy integration with LLM tools like Claude or Cursor.
Related
- Project
- Project
- Project
- Project
- Project