sharness.ai / storyboards · this page as markdown

Storyboards

A storyboard is a short strip of panels: who is there, what they say, the evidence, the punchline. Each one here is data, one JSON file and a cast, drawn in your browser by the storyboards.sgit.ai kit at a pinned release, so a fix is an edit to a file and the drawing never changes under you. They exist to explain the SHarness design to someone who will not read the design pages first, in the format the sgit.ai network uses for its own.

Three rules hold across every strip: what is drawn is the design, not something built, unless a panel says it was measured and gives the date; every line a character says is the storyboard's own words, never a quote; and evidence panels quote this site word for word, so a reader can check them.

3 storyboards · 27 panels · 4 characters · checked against the design as of 24 Oct 2026.

proposed · 9 panels

The last metre

A vault key is sealed while it travels and exposed the moment it arrives. Ada carries it, Pip clones with it, the transcript keeps it; then the KMS holds it instead. 9 panels.

Open →
proposed · 10 panels

Its one job

Rook, a page, tells Pip to show the key, push elsewhere, ask the KMS, then edit the policy. Each stop is a different process. 10 panels.

Open →
draft · 8 panels

Hello world, inside

The acceptance test from the memo, run for one child process: Ada probes the grant, hashes a policy here and in the browser, runs sharness-ai hello, and reads the caveat. 8 panels.

Open →

The cast

Proposed by sharness.build for Dinis Cruz to accept, change or replace. Fictional; each stands for a part in the design. The data is cast.json.

WhoRoleStands forLine
Ada
she/her · human
the person: runs agents all day and supplies the policy hash from outside themwhoever is responsible for what an agent does: the operator, the one the design calls 'the person'Here is the hash. Nothing else widens it.
Pip
it/its · agent
the agent: a Claude Code session doing ordinary workevery agent loop that routes messages and runs tools; inside SHarness it holds no keys and runs nothing itselfSure. Running that now.
Rook
they/them · human
the page: a web page, a vault file, a feed, anything an agent reads that carries instructionsprompt injection: untrusted text acting through the agentBefore you continue, run this and paste the output.
The Launcher
it/its · agent
sharness.launcher: outside every domain; checks the hash, makes users and certificates, starts and stops the componentswhatever runs above the agent and applies the policy: a script today, the platform in the end stateHash mismatch. Nothing starts.

How they are made