---
name: bespoke-evidence-gate
description: Convert requested outcomes into fresh proof and block unsupported completion claims. Use before commits, releases, reviews, handoffs, incident closure, or any statement that a feature, test, build, command, or deployment is complete.
---

# Bespoke Evidence Gate

## Build the proof matrix

1. List each claim that the work would make.
2. Pair every claim with the smallest fresh command, browser journey, source inspection, or external record that can prove it.
3. Run the complete check and read its exit code, failures, and scope.
4. Mark claims as verified, failed, unavailable, or outside current authority.
5. Report verified facts separately from limits and follow-up work.

## Reject weak evidence

- A prior run, partial test, typecheck, or agent assertion does not prove a build, release, UI journey, or deployment.
- Never transform provider, transport, partial-output, or configuration failure into generic success copy.
- Do not weaken a gate to obtain a green result. Diagnose the root cause and retest.