The first key
Noor opens a vault with a passkey, makes a key pair in her browser, and finds it on her laptop too. 9 panels.
7 storyboards · 64 panels · 7 characters · all drawn from data
The keys, one panel at a time
Every workflow on this site as a storyboard: a passkey and a vault, the two-way rule, an invitation, a secret by QR code, an access key sealed to a key, an agent getting a key, and the next one, in person. Flick through them as a deck, see every panel at once, or read them as a script; then try each one for real.
The AnchorNoorLeoKofiMalloryScoutThe Fleet
Keys for people
Two ways, or not at all
Mallory floods a key, as in 2019, and then tries again here, where a vouch can only be written in the voucher's own record. 9 panels.
An invitation
The Anchor invites Leo with a QR code; Leo has no access key, keeps his key in the browser, and is verified, until a date. 9 panels.
A secret, as a QR code
Noor seals a token to Leo's key; Mallory gets the link and nothing else; Kofi writes to Noor's inbox without an account. 9 panels.
An access key, sealed
Leo needs an access key to make a vault; the Anchor seals one to the key Leo already has, and keeps a ledger of hashes. 9 panels.
Keys for agents
An agent gets a key
Scout, a session agent, makes its own key; the Anchor compares the fingerprint and signs for it, for a week; the Fleet runs the rest. 10 panels.
Next: proposed
In person, by QR code
Noor and Leo scan each other's phones; the camera is the channel; two scans make one link. Proposed, not built. 9 panels.
The cast
Fictional people and agents, each standing for a part someone plays in the register. Proposed by pki.agent for Dinis to accept, change or replace; the Anchor stands for the part Dinis plays for now, and whether it is drawn as him is his decision.
The Anchor
The anchor: verification starts here. The part Dinis Cruz plays in the register for now: verifies people in person, on a call or on a channel already known to be theirs, operates agents, hands out access keys. Whether the Anchor is drawn as Dinis, and how, is Dinis's decision; until then a generic figure.
“Two ways, or not at all.”
Noor
The colleague: a security engineer who already had an access key, and now has a key pair in a vault. The first people the Anchor brings in: technical, sceptical, quick to try the thing.
“Show me where the private half lives.”
Leo
The newcomer: invited by the Anchor, no access key, a designer. Everyone the register is for who has never thought about keys.
“I don't have an access key. Is that a problem?”
Kofi
The stranger: a journalist who has to reach Noor and has no account anywhere. Anyone writing to someone in the register through their inbox.
“Do I need to sign up for anything?”
Mallory
The attacker: flooded the keyserver network in 2019, and tries the same here. The abuse every web of trust has to survive.
“Anyone can add, and nothing can be deleted.”
Scout
A session agent: a Claude Code session with a key that lives as long as the session. Every agent that makes its own key, names its operator, and is confirmed for a week.
“My key. It stays here.”
The Fleet
A fleet key: a second key in the Anchor's vault, operated by the Anchor, that operates the Anchor's agents. How one person runs hundreds of agents without filling their own record.
“Operated by the Anchor. Operating the rest.”
The technique, the drawing code and the viewer are gen-z-developers.sgit.ai's, vendored with one local patch so this site can add props (keys, vaults, QR codes, sealed envelopes). The data: cast.json and one JSON file per storyboard, checked by admin/build/gen_storyboards.py.