Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.

Verification Loop

Overview

Verify after each small change—not only at the end. Two modes share the same discipline:

1. Routine verification — run the right checks for the change type.
2. Claim-based verification — prove or disprove a specific, measurable claim with baseline vs treatment evidence.

When to Use

• After every code, dependency, or configuration change
• Before every commit or merge
• When the user asks to "verify this", "prove it works", or "show evidence"
• When tests pass but user-visible behavior still needs confirmation

Do not use claim-based mode for vague assertions like "the code is cleaner". Ask for a falsifiable claim first.