deliver

1# deliver
2 
3Carry out the named charter. Its `## Success checks` are the definition of done; nothing else
4is. Read the whole charter and the existing work first. The owner (whoever owns the work,
5often the user) can override this skill and any plan an agent wrote. Any kind of project uses
6it: for code and tests also read `references/proof.md`.
7 
8Prerequisites: `sno deliver-proof` needs bash 4+ and GNU coreutils (Linux) and prints one message
9and stops when they are missing; its selftest also needs python3. On macOS, install bash 4+ and
10GNU coreutils (for example with Homebrew) and put them first on PATH. If `sno deliver-proof` is not
11available, run `scripts/deliver-proof` from this skill's folder instead.
12 
13## Keep the work useful
14 
15- Before adding a prerequisite, test, record or approval step, name the requested result it
16  proves and what changes if it fails. If nothing changes, leave it out.
17- Check an uncertain fact by reading or calling what exists. If checking needs something built
18  first, building it is the first task, not a permission gate.
19- Records, telemetry, formatting, identifiers, checksums and review sign-offs never block the
20  work. Log the failed action, its place and the actual error, and continue. Do not turn such
21  a failure into an assertion, a silent return or a swallowed error. If the main operation
22  fails, say so with its cause; never report success. Stop only what cannot proceed and keep
23  independent work moving.
24…