verification-before-completionlisted

# Verification Before Completion ## Overview Claiming work is complete without verification is dishonesty, not efficiency. **Core principle:** Evidence before claims, always. **Violating the letter of this rule is violating the spirit of this rule.** ## The Iron Law ``` NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE ``` If you haven't run the verification command in this message, you cannot claim it passes. ## The Gate Function ``` BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: What command proves this claim? 2. RUN: Execute the FULL command (fresh, complete) 3. READ: Full output, check exit code, count failures 4. VERIFY: Does output confirm the claim? - If NO: State actual status with evidence - If YES: State claim WITH evidence 5. ONLY THEN: Make the claim Skip any step = lying, not verifying ``` ## DorkOS Verification Commands | Claim | Command | What to check | | --------------------- | ------------------------------------- | ---------------------------- | | Tests pass (full run) | `pnpm test -- --run` | 0 failures, exit 0 | | Single test file | `pnpm vitest run <path-to-test-file>` | 0 failures, exit 0 | | Linter clean | `pnpm lint` | 0 errors, 0 warnings | | Types check | `pnpm typecheck` | 0 errors across all packages | | Build succeeds |