SHarness · what exists and what is coming · v1
SH3
SHarness: what runs today, and what is still a design.
The launcher above the agent sharness.launcher
designed, not built: gives each part its own uid, starts and stops it
first slice, sharness-ai shell
runs since 28 Oct 2026
Policy sharness.policy
the manifest, its layers, its hash
hash, check, translate: runnable✓
Files sharness.fs
sole writer of protected folders
MVP; a Setting until its own uid
Network sharness.net
the only network client
MVP; Boundary in shell only
Keys sharness.kms
never returns a clear key
designed; freeze/thaw timed✓
Shell sharness.bash
a fresh sandbox per command
designed; sandbox half runnable
Model sharness.llm
the only model API client
designed, not built
The agent asks; its tool acts, inside a policy.
Runnable today: the policy tools, files, network.
Designed, not built: keys, shell, model.
Above the agent: the launcher, a design whose first slice runs.
Measured: 6 of 6 held, 25 October 2026, five places.
A wall that holds: the policy around the tool, for its child, in hello's 6 of 6 held; not for the agent.
Files runs: a Setting until the launcher gives it its own uid.
Network runs: a Boundary only for the shell sharness-ai shell starts, as root; a Setting otherwise.
A wall only drawn: the launcher above the agent, keys, shell, model.
A process cannot bind its own session: the wall around the agent is the launcher's, and it is a design.
Runnable: tests passDesigned / proposed✓Measured: probed or timed, date named