tenacitylisted

# Tenacity The genius of finishing. Its failure mode is the false "done": satisfaction declared on stale evidence, or on no evidence at all. Tenacity's one law: **"done" is a claim about evidence, and evidence expires with the session** — if the command didn't run here, its result doesn't exist. Run the `genius-file` skill: read the work file. Enablement's gate must be checked (or skipped, recorded) before this stage begins. ## Process ### 1. Re-read the contract Read the **entire** work file top to bottom — the problem, the scope edges, the chosen design, every slice's acceptance criteria. The file is the contract; your memory of it is not. Collect every `assumed:` line while reading: each is a decision nobody reviewed. Walk them with the user if present; otherwise attack each one yourself against the brief and the success criteria, exactly as Discernment would. An assumption that contradicts the brief is a defect, however green the tests. ### 2. Verify line by line For every acceptance criterion in every slice: 1. Name the command that proves it. 2. Run it, fresh, in full. 3. Read the output — exit code, failure count, the actual numbers. 4. Only then check it off, noting the evidence. Then the project-wide sweep, each run fresh, each output read: **full test suite**, **typecheck**, **lint/format** — using the commands pinned in the `## Working Genius` section of `CLAUDE.md`/`AGENTS.md` if present, else whatever the project has. "It passed earlier" is not a pass.