pki.sgit.ai / storyboards / An access key, sealed

An access key, sealed

built 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.

Try it, for real: Hand over an access key →The proposal →

The panels

  1. 1. An access key, sealed (cover; Handing out access keys)
  2. 2. The chicken and the egg (scene; Handing out access keys)
  3. 3. The key comes first (scene; join/index.html)
  4. 4. Sealed to it (scene; send.js, grant)
  5. 5. His vault, created with it (scene; open.js, grantButton)
  6. 6. Every device (scene; account.js, unlock)
  7. 7. The Anchor's ledger (scene; vault/index.html#vaults)
  8. 8. Next: minting, on signed requests (proposed) (scene; Handing out access keys, phase 2)
  9. 9. An access key never travels in the clear. (punchline; Handing out access keys)

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. The data is an-access-key-sealed.json and cast.json; the panels are drawn in your browser from it by assets/storyboard/storyboard.js, gen-z-developers.sgit.ai's storyboard kit, with Rough.js. Nothing is an image file.