Validate-bug runs after reproduction has supplied a finding and a PoC package. The validating agent reads the finding, the proof type, the commands and the raw receipts, and does not read the reproducer’s transcript.
It reruns the same compiler command or rebuilds and reruns the unchanged runtime PoC, saves its own receipts, and judges whether the diagnostic or assertion shows the exact claim and violates the stated invariant. The decision is confirmed, not confirmed or inconclusive, stored with a short reason.
What You Get
- A validate.json with the outcome, a short reason and the validator’s agent identity
- Rerun receipts with stdout, stderr, exit status and timing under validate/receipts
- A manifest of the validate directory and a record check
Common Use Cases
- Independently confirming a reproduction before spending effort on a patch
- Rejecting a PoC that does not demonstrate the stated claim
- Flagging unreliable observations as inconclusive
What Makes It Unique
The validator is blind to the reproducer’s narrative and must not repair the PoC to make the claim work. If an observation is unreliable it returns inconclusive and never infers presence or absence of the bug.
Under The Hood
The agent reads SKILL.md, a record contract and the reproduction package. It rebuilds the target and reruns the saved PoC or compiler command in the local checkout, writes receipts and a JSON record into a validate directory, and uses a bundled Python helper through uv to write a manifest and check records. The commands it runs are those of the project under test, and it does not change the PoC or the finding.