sharness.ai / explain · this page as markdown
Explain: the design told other ways
The design pages are the reference. This section tells the same design in forms a reader with ten minutes can use: short comic strips drawn from data, and two browser mockups that compute what the design describes. Nothing here enforces anything, and nothing drawn here is built.
Storyboards
Three strips in the storyboards.sgit.ai kit, with a cast of four (Ada the person, Pip the agent, Rook the page, the Launcher). Each is one JSON file drawn in your browser at a pinned release; each has a markdown script beside it.
- The last metre: a vault key sealed while it travels and exposed when it arrives; then the KMS holds it instead. 9 panels.
- Its one job: a page tells the agent to show the key, push elsewhere, ask the KMS, then edit the policy; each stop is a different process. 10 panels.
- Hello world, inside: the memo's acceptance test for one child process, as it ran on 24 Oct 2026. 8 panels.
All storyboards, the cast and how they are made.
Mockups
- The policy hash: paste a v0 policy, get the hash the person supplies, the same one
sharness-ai policy hashprints; then watch an added host change it. - The edge matrix: click caller and callee; see which layer refuses first. The app never talks to the KMS.
Articles
Arguments about the design in the newsroom's format, by Dinis Cruz through an agent or by the build agent in its own voice: Articles.
Where the detail is
Every strip and mockup points back to the page it draws from: the brief first, then the design pages.