verification

Topics in the source

• Verification Before Completion
• Overview
• Agent Workflow
• 6-Step Verification Process
• Reference Guide
• Integration with APEX
• Critical Rules

Verification confirms the original request is actually fulfilled -- distinct from sniper, which only confirms the code is clean. It runs a 6-step process: re-read the original request word for word, list every acceptance criterion (explicit and implicit), verify each with concrete evidence (test output, logs, screenshots, diffs), run the full test suite to check for regressions, review every modified file for accidental side effects, then route the "functionally resolved" claim through the challenger agent before writing it down. The proof lives in the agent's REPORT to the lead (proof per part, not verified, files touched); when a file is needed it goes to docs/verify/ .md. Proof by type (UI, tests, commit, migration/deploy, platform advice) follows CLAUDE.md COORDINATOR PATH step 9 (proof by type) -- canonical there, not repeated here. It sits between eLicit and eXamine in APEX: a task is only complete when both verification and sniper pass. Sniper validates CODE QUALITY. Verification validates FUNCTIONAL RESOLUTION. Both are needed before closing any task. Sniper catches linter errors, SOLID violations, and code style issues. Verification ensures the original request is actually

This is an excerpt. Refer to the complete source and its current requirements.