01

The problem

When an AI agent acts on the web or spends money, the other side has no way to know who sent it, what it may do, or to prove afterwards what happened.

02

What we engineered

Borrow from border control: identity documents, scoped permissions and a receipt for every crossing.

  • A mission state machine with agent passports and child agents that inherit bounded authority.
  • Budget hard stops and signed receipts with an offline verifier.
  • An interactive Mission Lab that walks through admission, blocking and escalation scenarios.
KYA Mission Lab: a list of agent scenarios such as a verified agent admitted, an agent with no passport blocked, and a budget overrun sent to a human checkpoint.
03

How it connected

Standard HTTP message signatures (RFC 9421) in Python and TypeScript.

04

What technology was appropriate

Python and TypeScript monorepo.

05

Where it stands

Pre-alpha research. The Mission Lab demo is public; the code is not yet released.

Current state, stated as it is today.

Bring us the bottleneck.

If your problem looks like one of these, tell us. We will say whether a build is the right answer.

Bring us a bottleneck