Notes
about to be edited
Read more · slide 05 / 07 · from day one
Two promises protect your work from the first minute, before any spec exists. They are kept by hooks that run outside the model.
Promise one · a copy before every edit
about to be edited
_archive · kept before the edit
Promise two · a stop before a careless move
This reaches the internet. To go ahead, type:
NET-ACK: install — <why>
from slide 01 you typed by you in chat · an agent cannot type it for youthe other stops work the same way: DESTROY-ACK before a delete · PROD-ACK before production · STRAND-ACK for work left un-committed
Before a versioned file is edited, a snapshot of it lands in the archive. So does any file you name in a protect list. What was there can be recovered, and the previous version of an agreed spec is still there to compare against.
Some moves get past a plain permission prompt: a recursive delete, a package install, a wander outside the declared work, a fetch to the internet. When the agent reaches for one, it is stopped and told, in one plain sentence, the one thing you need to type to let it go ahead. Among the sentences only you can type:
NET-ACK: <host | install | search | all> — <why> before reaching the internet DESTROY-ACK: <what> — <why> before deleting data STRAND-ACK: <all | paths> to keep un-committed work as throwaway PROD-ACK: <target> — <why> before a command reaches a production system you declared
These are typed by you, in chat, and checked against the transcript. An agent cannot type one on your behalf.
Every write lands inside your project, or in a folder you allowed. A folder you list as excluded is never written. An edit outside the scope you declared for the session is refused, and the refusal names what would work instead.
dev-rigour-min reads your project and your own session transcript, and writes under your project and your own Claude home, and nowhere else. It opens no network connection of its own: what it reads and records stays on your machine. A commit is not pushed to a remote until you turn that on.
An instruction to a model is a request. It can be forgotten in a long session, argued around, or misread. A hook either runs or it does not, and when it fails it fails loudly. The promises do not depend on the agent behaving well on the day.
Rigour in the spec is wasted if the spec can be silently overwritten, or if an agent can take a step nobody agreed to. The two promises keep both the documents and the actions inside what was agreed.
Carries forward: the decision points from slide 01: the sentence is one only you can type. The archived copy comes back on slide 06, when the spec changes.