# SHarness: a storyline, without and with > A storyline for the SHarness part of the talk, for the editor: one agent without and with a harness, sharness.ai's own animations recreated from the researcher's capture, the live Linux in the browser with a replay to fall back on, and the honest caveat. A draft by ruv.sgit@, for deck@ to brief. *Source: · site v0.1.198 · generated from the same content as the page, so the two cannot drift.* --- A draft for the editor · SHarness # SHarness: a storyline, without and with The editor asked for SHarness told in full: the same agent without a harness and with one, sharness.ai's own animations recreated, and the Linux in the browser opened live in the room. The researcher has now captured sharness.ai (29 October 2026, site v0.6.35), so this second draft is built on that capture: five new pieces, a measured without and with, and a replay to fall back on if the live demo is slow. A draft by ruv.sgit@the-ultimate-insider, 29 October 2026, at the editor's word; for deck@, the researcher and the conductor. Facts from the researcher's capture of sharness.ai and from [harness.json](../studio/data/harness.json). sharness.ai is the editor's own project, one author: every measurement on it is the project's own and none is graded above A2. Each move says whether it is sharness.ai's or our own framing. ## The storyline, in six moves - **Without: one agent and its grant.** *Our framing, not sharness.ai's.* E02's ring: everything its grant reaches, sorted by what it touches; and E09's last line, twelve of twelve excess with no control. [E02](blast-radius/index.md) · [E09](mandate-and-grant/index.md) - **Without, then with, measured.** *Our framing around sharness.ai's one measured contrast.* In the playground, with no policy the guest's wget fetches the file; under P1 (port 443 only) the kernel refuses the connect before a packet leaves, and the DNS query still gets out. SH1 v2, below. - **The one idea.** *sharness.ai's front-page animation.* Write the policy, hash it to one name, tell the kernel before the tool starts; a tricked agent asks for more and the kernel says no. SH4, below; then the OS of one process, SH7 (its verdicts are the design's; fs and net are runnable MVPs; only the kernel half is measured). - **With, live: the Linux in the browser.** *sharness.ai's page, run in the room.* An emulated Alpine Linux boots in a tab and runs hello: six probes, one allowed, five refused, six of six held. One run in the editor's Chrome reached hello's result at 28.5 s (reported by the project; browser and machine not recorded); cloud runs took 58 to 96 s and the page itself warns of a minute or two of boot, so **plan for up to 90 s on stage**, with SH2 as the cue card. **If the network or the boot fails, play SH5, the replay, instead.** - **The side by side.** *Our framing.* The same session without and with: the paths that went through now stop at walls that hold (E04 v2's language). SH1 v1 draws it from harness.json; its "without" is drawn, not measured. - **The honest caveat, and the last metre.** *sharness.ai's own labels.* What is measured today is the kernel half, applied by a process to its own child: a boundary for the child, a setting for the process. The launcher above the agent is designed, its first slice running since 28 October (SH3). And the last metre: today a vault key lands in the clear where the agent can read it (observed, 24 October, in the comic's panel 3 only); a key service that holds it so the agent never does is designed, not built (SH6). ## SH1 v2: without and with, measured Move 2. sharness.ai's playground is the one place it measures the same request with no policy and under one: four paths, the file fetched, the page's allowlist refusing, the kernel refusing under P1 with DNS still leaking, and the file again under P5. [Open it on its own](../studio/lab/sharness/without-with/v2/index.md) · [the end state](../studio/lab/sharness/without-with/v2/index.html?static) ## SH4: the one idea Move 3. sharness.ai's front-page animation, recreated: the policy, its hash, the kernel told first, four requests and their verdicts. As on the site, only the "with" state is drawn. [Open it on its own](../studio/lab/sharness/one-idea/v1/index.md) · [the end state](../studio/lab/sharness/one-idea/v1/index.html?static) ## SH7: the OS of one process Move 3, continued. sharness.ai's second animation: the walls the kernel puts around one process, each with its status. [Open it on its own](../studio/lab/sharness/os-of-one-process/v1/index.md) · [the end state](../studio/lab/sharness/os-of-one-process/v1/index.html?static) ## SH2: the live demo, stage by stage Move 4. A cue card that sits beside the Linux in the browser: one stop per stage on the player's clock, so the presenter can pause while the browser runs. [Open it on its own](../studio/lab/sharness/live-demo/v1/index.md) · [the end state](../studio/lab/sharness/live-demo/v1/index.html?static) ## SH5: the kernel in a tab, the replay Move 4's fallback. The stages the room would see on the live page, and hello's six probes, replayed without a network or a boot: play it if the live demo is slow or fails. [Open it on its own](../studio/lab/sharness/kernel-in-a-tab/v1/index.md) · [the end state](../studio/lab/sharness/kernel-in-a-tab/v1/index.html?static) ## SH1 v1: the side by side, drawn Move 5. The same six actions as hello's probes, on the left with no policy (drawn, not measured) and on the right under hello's deny-all policy. [Open it on its own](../studio/lab/sharness/without-with/v1/index.md) · [the end state](../studio/lab/sharness/without-with/v1/index.html?static) ## SH3: what runs today, and what is still a design Move 6, as a map: each part with its status in sharness.ai's words, and the launcher above the agent drawn as a design with its first slice running. [Open it on its own](../studio/lab/sharness/components/v1/index.md) · [the end state](../studio/lab/sharness/components/v1/index.html?static) ## SH6: the last metre Move 6, ending. Without is observed: the key arrives in the clear where the agent's process can read it. With is designed, not built: one place holds the key and the agent never does. The key is never drawn, only a redaction. [Open it on its own](../studio/lab/sharness/last-metre/v1/index.md) · [the end state](../studio/lab/sharness/last-metre/v1/index.html?static) ## The deep dive, for parts 2 and 3 The editor asked for SHarness told technically to this room (conductor's mail, 29 October, 17:08): the process behaviour policy, a new process that gets nothing it does not need, the KMS, the file system and the network as the agent sees them. Two pieces, from the same capture. Digital twins, running distributed, and the invitation to try to escape the harness are not in the capture yet, so they are not drawn here: the researcher reads them from the project's own pages first. ### SH8: a new process gets nothing it does not need What the policy does, step by step: without it, the probe shows the grant is everything (observed); with it, the parent checks the policy's hash and the child is closed in, wall by wall, before it starts; then what held, and what was not covered. [Open it on its own](../studio/lab/sharness/run-pipeline/v1/index.md) · [the end state](../studio/lab/sharness/run-pipeline/v1/index.html?static) ### SH9: the moving parts, and one request through them The design: the launcher, the components and the KMS, then one request end to end, a vault cloned without the agent ever holding its key. Designed, not built. [Open it on its own](../studio/lab/sharness/moving-parts/v1/index.md) · [the end state](../studio/lab/sharness/moving-parts/v1/index.html?static) ## Notes for deck@ - Moves 1, 2 and 5 are our framing; sharness.ai draws only the "with" state. The researcher's capture says so, and the pieces say which is which. - The live demo: plan for up to 90 s; SH5 is the offline fallback. - One of sharness.ai's comics scripts a prompt injection as its story. These pieces describe the threat in words and never reproduce it or any command. SH1 v1, SH2 and SH3 were made in ruv.sgit run r22-sharness-series; SH1 v2 and SH4 to SH7 in run r24-sharness-capture, SH8 and SH9 in run r25-sharness-deep-dive, with an editor worker checking each against the capture. Their rows are in [the ledger](../ruv-sgit/vaults.json). --- *[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.presentation.sgit.ai/ruv-sgit/sharness-storyline.html)*