tenacity

Tenacity

The genius of finishing. Its failure mode is the false "done": satisfaction declared on stale evidence, or on no evidence at all.

The concept: "done" is a claim about fresh evidence, and evidence expires with the session. If the command didn't run here, its result doesn't exist. Re-read the snapshot, the CONTRACT.md it points at (that file is the contract; your memory of it is not), and, of the log entries it links, the slices' evidence alone — the slice-N entries, each in its slice's branch; the other branches hold process, not claims to verify. Then run everything fresh and read the output: the suite, the checks, every acceptance criterion; where there is no Slices section, the Problem section's success criteria instead. "Should pass", "passed earlier", "seems to work" are each a command you haven't run in this session.

Where the slices recorded a dirty baseline, the fresh run is held to the same line, no new failures, and the baseline is named in this stage's evidence. Have the plugin's reviewer agent (agents/reviewer.md) judge the diff from base: against the brief — its task message naming the diff, what it is judged against, where the record lives, and which slices already carried their own review, so its weight falls on the joints between slices no seam test reaches and the drift of the whole against the brief. Where the work cut more than one slice, spawn three in parallel, blind to each other, each told where its weight falls: the joints between slices, the drift of the whole against the brief, the inputs and states no criterion mentions. Three, each with a focus, because one reviewer spends its reading on whichever it meets first, and a focus is a place to start, never a limit on what it may flag. Don't tell it what not to flag, because the joint you didn't think to name is the one it is there for; treat its findings as claims to verify, because a review sent looking will find something and a finding fixed unchecked costs the fix. Start it before the fresh run, because both only read and the run fills the time the review takes. Spawn it synchronously where you cannot be certain the harness wakes you, and never end your turn while it runs — a review nobody reads did not run. Where base: was never pinned, pin it now — the commit before this work's changes began.

Walk the recorded assumed: and owed: lines — an assumption that contradicts the brief is a defect however green the tests, and an owed: line is a criterion nobody's eyes have checked: put it to the user now, before done is said, and drain it with what they saw. Whatever the fresh run disproves is corrected rather than quietly dropped — and the errata skill is loaded before the correction is proposed, not after, because the first move to hand is to fix the false line itself, and a log line that recorded a false result is a record, corrected only by what is appended below it. Before the user accepts, the close says what changed at the behavior level — what they will now see happen, and the consequences they will live with — because built work nobody absorbed is next month's surprise. It offers no quiz and asks no closing question, because an offer made at every close is a prompt the user waves off every time; the blindspot skill's quiz runs when they ask for it.