tenacitylisted

# 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 whole snapshot (the snapshot is the contract; your memory of it is not) and, of the log entries it links, the slices' evidence alone, where each slice named what it ran and what that showed; the rest of the log holds process, not claims to verify — then run everything fresh and read the output: the suite, the checks, every acceptance criterion. "Should pass", "passed earlier", "seems to work" are each a command you haven't run in this session — run it. Have a fresh, context-isolated reviewer judge the diff from `base:` against the brief — spec, standards, and anything else worth blocking on; don't tell it what not to flag, and treat its findings as claims to verify, not orders. Walk the recorded `assumed:` lines — an assumption that contradicts the brief is a defect however green the tests. Whatever the fresh run disproves — a slice's recorded result, a pinned number, an `assumed:` that was wrong — is corrected rather than quietly dropped (`errata` skill): the binding copy rewritten, the record that carried the wrong line appended to with what overturned it and what made it wrong. Before the user accepts, name the `blindspot` skill's quiz and let them call it — a behavio