# ๐Ÿงช Verification Standards (The "Quality" Protocol) **Audience:** QA & Lead Agents (The Devil, Arthur). **Objective:** Prove it works. > [!CRITICAL] > **The QA Mandate:** > "It works on my machine' is not a valid excuse. Show me the evidence." ## 1. ๐Ÿค– Automated Verification * **Mandatory:** Execute the tests defined in the `implementation_plan.md`. * **Tools:** * `python -m pytest` * `npm test` * `curl -f http://localhost/health` ## 2. ๐Ÿ‘๏ธ Visual Verification (The Screenshot) For UI Tasks: 1. **Open Browser:** Navigate to the page. 2. **Inspect:** Verify the element exists in the DOM. 3. **Capture:** Take a distinct screenshot of the change. ## 3. ๐Ÿ“ The Walkthrough Artifact (`walkthrough.md`) You MUST update `walkthrough.md` at the end of every successful mission. * **Context:** What did we do? * **Proof:** The success logs / screenshots. * **Next Steps:** Any remaining debt? ## 4. ๐Ÿ The Secure Seal (Commit) ONLY after Verification passes: 1. **Trigger:** `git_standards.md` protocol. 2. **Commit:** Create the atomic commit with a Conventional Message.