sharness.ai / the source documents · this page as markdown

The source documents

Published verbatim for review. These are the documents this site was built from, as received on 24 October 2026. The raw markdown is the source of truth; the site's pages port them with the naming rules applied.

The brief for this site

Document	What it is
BRIEF-for-website-agent.md	identity, seed text, page structure, claim rules, naming rules and open decisions for sharness.ai

The design pack (read in order)

#	Document	What it settles	Ported to
00	00-README.md	problem, goals, threat model, glossary, decisions, end state	Why, Roadmap
01	01-architecture.md	the original four components, edges, mutual TLS with a session CA, command flows, deployment topologies, refactor path in sgit	Architecture, Components, Roadmap
02	02-sealed-key-flow-and-kms.md	the sealed handover, the KMS protocol, where keys live and for how long	Keys and the KMS
03	03-process-behaviour-policy.md	Process Behaviour Policies: schema, layers, hashing, enforcement map, learning from traces, prompt-injection walkthrough	Process Behaviour Policies
04	04-environment-evidence.md	every probe and measurement, with method and caveats	Evidence
05	05-sharness.md	the generalisation: naming, components, transparent vs harness-aware apps, minimal code	Architecture, Components, About
06	06-llm-and-the-agent-loop.md	how an agent message flows (observed), `sharness.llm`, `sharness.bash`, the dual-LLM split	Agents and LLMs
07	07-enforcing-the-process-tree.md	every process through `sharness.bash`; side doors; safe testing; proof of concept not yet run	Enforcing the process tree

How this pack relates to sgit's

The design began as cli.sgit.ai's sealed vault keys design pack. Compared against the sgit pack's documents 00–04 as Dinis Cruz shared them, as of 24 Oct 2026: 01, 02 and 03 here are identical; 00 here adds documents 05–07 to the reading list and the note on names; 04 here adds §7, the observation of the agent loop. Nothing in the sgit pack's 00–04 is missing from this one. The sgit pack also has a 05, compatibility and rollout (with nothing switched on, sgit behaves exactly as 0.24.0 does; sealed and plain clones side by side; staged rollout), which is sgit-specific and is linked, not republished.

Memos

Date	Memo	Written up as
24 Oct 2026	Voice memo 01: guidance notes for SHarness, as transcribed	A secure harness for agents

The evolution, on cli.sgit.ai

SHarness began as a fix for sgit, and that history is published where it happened:

A vault key that never lands: the analysis that started it, the morning of 24 October 2026.
Sealed vault keys in sgit: requirements, from an agent that moves vault keys for a living, the same day.
The requirements and the design, side by side: the two read against each other and against the code.
Sealed vault keys for sgit: a design pack: the sgit-specific design, with its compatibility and rollout document.
The SHarness design pack, above: the same design, generalised.

Known issues in the pack

Published as received, so these remain in the raw files:

00-README.md links 05-the-sharness.md; the file is 05-sharness.md.
Documents 01–04 use the sgit-specific component names (sgit-cli, sgit-fs, sgit-net, sgit-kms); document 05's diagram uses harness.<role> where the rest of the pack uses sharness.<role>. The site's pages use sharness.<role> throughout.
The pack lists the command name as open; it was settled as sharness-ai the same day (see Roadmap).

All content CC BY 4.0.