Only the harness can open the gate.
Paste a pull request. A model writes a test from the linked issue. The harness runs it on the base commit and on the fix, reverts the fix, and mutates it. If any pin sticks, the gate stays shut and you get the reason, never a guess.
What the gate has refused so far
Running live
Recent proofs
Only receipts saved on this server. Nothing here is a sample.
How the two Nemotron models split the work
- 1Read the pull request, its linked issue, and both commits. No model.
- 2Lightning maps the repository and triages the issue.
nvidia/Nemotron-3_5-Lightning - 3Ultra writes the test from the issue text alone.
nvidia/Nemotron-3-Ultra-550b-a55b - 4The harness runs the test on base and head, reverts the fix to check the test fails again, and sets the verdict. No model decides it.
Each receipt lists the calls it actually made. Anything a receipt did not record shows as not recorded.
What happens when the gate stays shut
If the proof test still fails on an agent's fix, a Nemotron coding agent rewrites the code and the harness runs everything again. The model never decides: the gate opens only when the frozen proof test is green and the repository's own suite stays green.