Home / Keys for people and agents / An access key, sealed
Keys for people and agents · Keys for people · board 05
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.
built 9 panels · pki.agent, 20 October 2026. Every line a character says is the storyboard's, not a quote, and is marked not_a_quote; evidence panels quote this site's pages or the research note word for word, which the build checks.
Take it with you
The same storyboard in every shape it comes in. The data and its derived files are on this site; the pictures are drawn in your browser, now, by the same code as the deck (export.js, v0.1.0), from the current panel.
Put it on your page
Two lines, from any site. The script is pinned to an immutable release of the kit, so the embed draws exactly this, for as long as the page exists. How embedding works.
The panels
- 1. An access key, sealed: The key first, then the access key, then the vault. (cover; Handing out access keys)
- 2. The chicken and the egg. Leo says: “Which comes first?” (scene; Handing out access keys)
- 3. The key comes first. Leo says: “My key, in the browser.” (scene; join/index.html)
- 4. Sealed to it. (scene; send.js, grant)
- 5. His vault, created with it. Leo says: “Create my vault with it.” (scene; open.js, grantButton)
- 6. Every device. Leo says: “On my phone as well.” (scene; account.js, unlock)
- 7. The Anchor's ledger. The Anchor says: “Who, when, and a hash. Never the key.” (scene; vault/index.html#vaults)
- 8. Next: minting, on signed requests (proposed). (scene; Handing out access keys, phase 2)
- 9. An access key never travels in the clear.. (punchline; Handing out access keys)
Imported unchanged from SGit-AI/SGit-AI__Website__PKI/admin/content/storyboards/05__an-access-key-sealed.json at commit ab6affc9 (2026-10-20). The cast is cast.json.