An AI assistant asks to do something in the company's ERP. Before anything happens, the request has to get past seven gates — who is asking, whether they may, what they are carrying, and whether a person signed for it. This page shows those gates live, and names the one that stops a call.
Three separate keys. Stealing the gateway is not enough.
trust domainsShow the authorization lanes and the token chain
This bench is a local rehearsal of the rules: nothing here calls the gateway, and no order is ever created by it. Real traffic appears on “The gate”.
How it works — and what it won't do
The explainer is part of the same instrument, not a separate site — so you can switch to it mid-demo without losing the room. The full architecture write-up →
Passkey enrolment happens once, on the approver's own device, and appears here as a completed fact rather than a menu item. Approve on your phone →
A compromised approver device could approve one action. The blast radius is one single-use approval bound to one statement — not a standing permission.
This is a demo, not production, and it is not affiliated with or endorsed by any vendor named on it.