diff options
Diffstat (limited to 'claude-rules')
| -rw-r--r-- | claude-rules/verification.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/claude-rules/verification.md b/claude-rules/verification.md index 8993736..673a54d 100644 --- a/claude-rules/verification.md +++ b/claude-rules/verification.md @@ -31,6 +31,19 @@ If you find yourself using these words, you haven't verified: Replace beliefs with evidence. Run the command. +## When You Cannot Verify + +Sometimes the verification command cannot run: the tool is absent, there is no network, a sandbox blocks it, or the environment is missing a dependency. A check that did not run must never be reported as a pass. "Unable to verify" is an honest, required outcome — not silence, and not an optimistic "should work." + +When a check cannot run, report it in this order: + +1. **Command attempted** — the exact command you tried to run. +2. **Why it could not run** — tool absent, no network, sandbox limit, missing environment, etc. +3. **Risk left unverified** — what might be broken that you would not know about, given the check did not run. +4. **Next command to close the gap** — the smallest command the user can run to verify themselves. + +Do not let an unverifiable check vanish into a confident summary. State it plainly and hand the gap to the user. + ## Before Committing Before any commit: |