Rule
Every verified result becomes the new floor. Commit it, record the verdict that made it acceptable, and make the baseline something the system cannot silently slip back below.
Done is a verdict, not a merge. A pull request that merges on optimism is not progress; a change that passed its gate and became the baseline is. One large open-source repository's ten-month public dataset makes the social version of this rule visible: hundreds of agent-authored pull requests, every one held at draft until a human reviewed it, over half needing human follow-up commits before landing. The airlock is what made the throughput safe.
What AgentOps Enforces
- Commit and push verified work; unverified work stays in the airlock.
- Record the proof that made each change acceptable alongside the change.
- Close or update the issue that tracked the work; file follow-ups for unfinished scope.
- Treat any regression below a ratcheted baseline as a stop-everything event, not a flaky test.
Failure Signal
- A fix exists only in an unpushed local checkout.
- Work merges because it looked finished, and the gate runs afterward — or never.
- A later agent reopens solved ground without knowing it was solved.
- The project cannot tell a failed attempt from accepted progress.
Done Looks Like
The remote has the commit, the tracker has the state, the verdict is attached, and the next agent starts from a floor that yesterday's work raised.