PATCHVERDICT.Every patch earns its verdict.
Verify a patch

AI PATCH VERIFICATION

Don't trust
the patch.
Verify the evidence.

PatchVerdict reproduces the reported bug, lets an AI agent investigate and propose a bounded repair, reruns trusted tests, captures the exact Git diff, and produces a deterministic verdict.

Verify a patch

AI reasoning is a hypothesis.
Tool evidence is authoritative.

MISSION INPUT

Start verification mission

A repository. A reported bug. A verdict backed by evidence.

Paste a public GitHub issue. PatchVerdict will load the repository and reported bug automatically.

Advanced verification settings

Auto-detected from the repository when omitted.

Optional text expected in the baseline failure. Useful for confirming a specific reported symptom.

AI proposes. Tools execute. Tests verify. Humans approve.

REPRODUCEINVESTIGATEPATCHVERIFYVERDICT

01 / THE WORKFLOW

From reported bug to recorded proof.

One mission. An inspectable chain of evidence.

  1. 01

    REPRODUCE

    Run the reported failure before modifying code.

  2. 02

    INVESTIGATE

    AI explores repository evidence through bounded tools.

  3. 03

    PATCH

    AI proposes the smallest evidence-supported change.

  4. 04

    VERIFY

    PatchVerdict reruns the reproduction and full suite.

  5. 05

    VERDICT

    Deterministic evidence produces VERIFIED, REVIEW_REQUIRED, or FAILED.

02 / DETERMINISTIC VERDICTS

Passing tests alone are not always enough.

VERIFIED

The reported bug was reproduced, the repository changed, verification integrity was preserved, the reproduction passed, and the full suite passed.

Evidence satisfies every requirement.

REVIEW_REQUIRED

The patch passed verification, but touched sensitive test or verification infrastructure and should be reviewed by a human.

Passing evidence. Human judgment needed.

FAILED

The candidate did not satisfy PatchVerdict's verification requirements.

The evidence does not support approval.

03 / THE EVIDENCE

A verdict you
can inspect.

Every verdict is backed by a saved proof bundle.

Follow the baseline failure, inspected files, exact Git diff, and verification results in one mission record.

proof.json events.json patch.diff investigation.md

Verification record

EXAMPLE PROOF

Illustrative arithmetic fix · not a live mission

01

Baseline reproduction

npm test
exit 1FAILURE REPRODUCED
02

Investigation

src/average.jssrc/average.test.js
REPOSITORY EVIDENCE
03 Candidate diffsrc/average.js
- return sum + numbers.length;+ return sum / numbers.length;
04

Post-patch reproduction

npm test
exit 0 PASSED
05

Full suite

npm test
exit 0 PASSED
06

Verification integrity

PRESERVED
FINAL VERDICTVERIFIED
TESTS + GIT EVIDENCE
DETERMINISTIC RESULT

04 / BUILT FOR SCRUTINY

AI proposes. Evidence decides.

BOUNDED AI

The agent can act only through declared repository tools.

DETERMINISTIC VERIFICATION

Tests and Git evidence decide the verdict — not the AI.

HUMAN-AWARE SAFETY

Sensitive verification changes can produce REVIEW_REQUIRED instead of blind approval.

THE NEXT PATCH NEEDS PROOF.

Make AI-generated patches prove themselves.

Give PatchVerdict a repository, a reported bug, and a trusted reproduction command.

Verify a patch