Not slides — live vaults

See the approach actually running.

Each demo below is a real application inside an encrypted vault, opened with a deliberately published read-only key and running directly in this page. The key is the whole credential: no account, no signup, no write access, and it is handed to the embedded vault over a same-page handshake rather than a URL. The larger vaults load on request rather than on arrival, so this page stays light on a phone.

What leaves your device. For every demo here except one, the answer is nothing: the vault is decrypted in your browser and what you do inside it stays there. The exception is Agent permission games, which sends your score so it can keep a leaderboard — it is labelled on its own card and on its page, and it is the only one that sends anything anywhere.

Why publish the keys at all? Because the model should be inspectable. Each key is a one-way derivation of the vault's own key — it grants read, and only read — and publishing it means anyone can open the demo, clone the vault, and check what we say against what is actually there. The same property is how a finished register gets handed to an auditor or a board.

Then do it with your own estate

The demos use invented estates. Yours is more interesting.

Pick one agent already in production. We will state its mandate, map the grant behind it, and show you the gap — with a number on it.

How it works