---
title: "Report, do not block"
url: /patterns/report-do-not-block
description: "A validator reports and routes. It does not gate the agent on uncertain findings."
---

## §0 · statement

# Report, do not block

A validator reports and routes. It does not gate the agent on uncertain findings.

## §1 · why

### Why it works

An agent has a limited number of fix attempts. A false blocker burns them on a problem that does not exist. Reporting with a route (who fixes what) keeps the agent working and the findings visible. A single score was rejected for the same reason: it can read perfect while blocking findings sit under a baseline.

## §2 · example

### Copy this

```json
{
  "finding": "spacing-off-scale",
  "origin": "implementation",
  "evidence": { "value": "18px", "nearest": "--space-4 (16px)" },
  "route": "implementation agent",
  "blocks": false
}
```

## §3 · breaks

### Where it breaks

Reports nobody reads are noise. The route must reach an owner.

## §4 · cases

Used in: [Case 4](/cases/validator-for-a-banking-app). About 13% signal at first contact with real files; precision and recall of 1.0 on the tuning corpus only [claim case4-signal: Own project. The 1.0 holds on the tuning corpus only; source: author's project, internal; confirmed]
