Most flaky bug reports end in one of two places: "cannot reproduce" or a patch nobody can prove fixed the problem.
Verdict turns a GitHub issue into a bounded investigation. It runs an approved command repeatedly under approved conditions, keeps every observation and refuses to claim a reproduction unless the evidence crosses a deterministic threshold.
This is not an autonomous patch generator. It is an evidence-producing agent harness for the difficult step that comes before a patch.
An LLM can read a stack trace and propose a plausible explanation quickly. Plausible is not the same as reproduced.
For an intermittent failure, the questions that matter are concrete: Which condition actually triggers it? How often does it fail under that condition? What happens under a contrasting control? Which repository range does the evidence support? What regression test would prevent the same failure from returning?
Hunter searches only the condition matrix and command budget approved by the maintainer. Successful, failed, partial and unresolved runs all stay in the evidence ledger. An inconvenient result cannot disappear just because it weakens the story.
Surgeon narrows the reproduced condition to the smallest suspect range the records support. Static inspection stays visibly different from a proven execution boundary. Surgeon does not author a patch.
Insurance converts the reproduction into a regression plan: the test name, fixture, failing assertion and publication manifest. A draft pull request can only be created through a workflow the maintainer explicitly approves.
Each act is allowed to claim less than the act before it. None can talk the deterministic reducer into a stronger verdict.
Verdict reproduced TrueForge issue #417, where snapshot registration can wait indefinitely when an upstream request never resolves.
The pinned runtime used @truefoundry/trueforge-core@0.1.4#DaytonaSandboxProvider and ran two conditions:
| Condition | Result | |---|---| | daytona-stalled-endpoint | 10 of 10 runs matched, REPRODUCTIONPINNED | | daytona-responsive-endpoint | 0 of 10 matched, NOTREPRODUCED |
The control is the important half. A condition that fails every time next to one that never fails is stronger evidence than twenty failures with no contrast.
The evidence binds the observations to the TrueForge session, Hunter thread, repository commit, npm provenance commit and shared source blob.
The model gathers candidate observations. It does not decide what those observations prove.
Verdict's evidence contract is simple: Issue text and repository content begin as untrusted input. The investigation may use only approved commands, knobs and budgets. Every accepted observation must match the evidence schema. Pure reducers decide which claim the records support. Missing or conflicting evidence produces an honest partial result. A maintainer controls the only public write.
The same records always produce the same verdict. That is the boundary between an agent exploring a problem and a system making a claim.
The recorded case renders the executed artifact. It includes both conditions, all twenty runs and the recomputable hash.