verification-gateslisted

# Verification Gates ## Overview Verification gates are mandatory quality checkpoints that must pass before any implementation work is considered complete. These gates prevent broken code from being committed, ensure type safety, maintain code style consistency, and validate that all tests pass. **Owner Agent**: Alphonse (Verifier Agent) ### Key Principles 1. **Non-Negotiable Quality**: Every code change must pass all applicable gates 2. **Automated Enforcement**: Gates are triggered automatically via hooks 3. **Clear Feedback**: Failures provide actionable error messages 4. **Project-Aware**: Commands adapt to detected project type and tooling 5. **Fail-Fast, Fix-First**: When any gate fails, work stops until resolved ### Verification Hierarchy ``` Loid (Executor) Alphonse (Verifier) | | Quick sanity tests Full verification gate during implementation before completion | | +----------> Handoff >----+ ``` --- ## Gate Types ### Pre-Commit Gates | Check | Example Command | Timeout | |-------|-----------------|---------| | Lint | `npm run lint` / `ruff check` | 30s | | Format | `npm run format:check` / `black --check` | 15s | | Quick Tests | Changed file tests only | 60s | ### Pre-Complete Gates | Check | Example Command | Timeout | |-------|-----------------|---------| | Full Test Suite | `npm test` / `pytest` | 300s | | Type Checking | `npx tsc --noEmit` / `mypy .` | 120s | | Linting |