The firewall for machine action.

Antivirus scanned files. Firewalls filtered packets. EMILIA Gate verifies actions before machines change the world. It sits at the actuator boundary and refuses any consequential action unless it carries a valid, non-replayed authorization receipt — proof a named human approved that exact action.

Not authentication, not permissions, not anomaly detection. A policy-enforcement point that requires portable proof of human authorization before the world is mutated. Deny by default. Fail closed.

If an agent cannot produce a valid receipt, it cannot change money, code, permissions, data, infrastructure, energy, or physical state.

The gate is deployed by the resource owner — the bank, the cloud API, the database, the robot controller, the grid. An agent that wants to act must bring a receipt the gate verifies. There is no central authority to trust; verification is offline.

Consequences, not prompts.

Request → challenge → sign → verify → execute → proof.

Assurance tiers set the floor per action: software — A valid receipt — a software-held key. class_a — A device-bound human signoff (WebAuthn / passkey). quorum — m-of-n distinct humans — the cryptographic two-person rule.

One gate, every actuator boundary.

It does not stop every bad actor. It makes unreceipted systems untrusted.

A bad actor can build an unguarded machine. EMILIA Gate makes legitimate infrastructure refuse unreceipted consequential actions by default — so the parties with leverage (clouds, payment rails, regulators, insurers) can require a receipt. That is how TLS, code signing, and SOC 2 won: not by stopping every bad actor, but by making serious buyers reject systems that lack the control. Necessary, not sufficient.