gate

# gate

Verify before claiming completion.

## Trigger

Before claiming: "done", "fixed", "complete", "working", "ready"

---

## Pre-Work Gate (Before Starting)

Run before substantial work begins. Blocks execution if missing.

```
□ Verification method locked (not "assumption")
  → What type: execution output / observation / measurement?
  → What evidence will you show?

□ At least 2 "must NOT" criteria exist
  → What should this NOT do?
  → What scope should NOT expand?

□ Fit score determined workflow shape
  → <25: BLOCKED - clarify first
  → 25-29: Colleague-shaped (iterate each step)
  → 30-39: Tool-with-review (checkpoint major steps)
  → 40+: Tool-shaped (milestones only)
```

**If any unclear:** Pause here. Clarifying these now prevents rework later.

---

## Post-Work Gate (Before Claiming Done)

### Expert Review Check (Loop Integration)

When invoked after loop execution, check expert review status:

```
□ Thorough expert review passed?
  → Check .loop/workflow-state.json for reviews.thorough.passed
  → Must be true to proceed
  → If false: "⚠️ Expert review has {N} unresolved blockers. Resolve before gate."
```

If `reviews.thorough.passed` is false → resolve findings to ensure quality before proceeding.

### Verify Integration

Before running workflow-specific checks, ensure verify passed:

```
□ hope:verify thorough tier passed?
  → Check .loop/verify-config.json for results
  → All criteria must show PASS
  → Evidence must be captured
```

If verify not run or failed → address findings before completion to ensure quality.

---

## Workflow A: Build

```
□ Feature executes without errors (show output)
□ Edge cases tested (empty, null, boundary)
□ Rollback tested if Type 2B/1
□ Dependencies verified
```

## Workflow B: Debug

```
□ Root cause identified with evidence
□ Fix tested and resolves symptom
□ Prevention added (test/automation/guard)
□ Related bugs checked (same class)
```

## Workflow C: Refactor

```
□ Existing tests pass unchanged
□ Behavi