Harnesses
Not Rest Inc. · Capabilities · The model is not the system
Give a brilliant person an empty room and you get whatever mood they woke up in. Give them a studio — instruments laid out, tape rolling, a producer at the desk — and you get work. The model is the brilliant person. The harness is the studio: the scaffolding a working session runs inside, so that discipline is structural instead of optional.
Four kinds of structure
- Anchored discipline — the working contract loads at session start: probe before believing, prove before claiming, bank before stopping. The session's habits don't depend on remembering to have them.
- Lifecycle hooks — code that fires at the session's boundaries: start, every prompt, every delegation's end — keeping records current at zero attention cost.
- Gates — checks with exit codes that block what isn't right, the way this site's own deploy refuses to ship when code and declarations disagree.
- Receipts — an append-only trail of what ran, what it concluded, and what it cost, so “trust me” is never the answer to “what happened?”
Not a concept — an install
The not.rest session harness is open-source at github.com/notrestai/notrest: its README calls itself exactly what it is — the scaffolding a working session runs inside — and everything above is inspectable in it: the discipline contract, the session hooks, the eval suite that checks the harness's own rules (its doctrine: a well-encoded law leaves a static fingerprint — check the fingerprint), and the ledgers.
The bet underneath: models will keep getting smarter, and it won't be enough. Capability without structure produces impressive accidents. The harness is how capability becomes reliability — and reliability, not brilliance, is what you can hand real work to.