{
  "id": 13497035,
  "title": "Hold OSS Model Notes Behind a Local Review Contract",
  "url": "https://urgent.news/2026/10/10/hold-oss-model-notes-behind-a-local-review-contract",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-10T18:53:40.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/gitrs_5994/hold-oss-model-notes-behind-a-local-review-contract-1f85"
  },
  "original_language": "en",
  "account": "Once an OSS model note remains unbound, only after a local review contract is approved can it provide any value. Long model replies often resemble completed reviews but lack rerun evidence. This workflow divides tasks into three stages, with local reproduction owning the bug claim and the model acting as a secondary reviewer. The contract file, located at review-contract.json, must contain verifiable facts, excluding coding style preferences. It records the exit codes before and after a patch, along with the command to run and the allowed paths. Three distinct lanes are involved: local reproduction, a disposable server rerun, and a free model read. The model may only identify risks not covered by the command, without approving the patch. To initiate the process, select a command that fails on the current base commit and record its exit code. Limit the patch to specific paths, ensuring the diff matches the allowed_paths list. Capture the local after log by running the command within the review worktree and saving the combined log and exit marker. Confirm the results on a disposable server by cloning the public base, applying the same patch, and recording the server's exit code. Generate a redacted read packet containing the contract, path list, both exit lines, and a scoped diff. Finally, request a non-binding read from the free model, requiring each bullet point to cite a path or contract key and prohibiting any approval of the patch.",
  "summary": "An OSS model note stays non-binding until a local contract passes. The contract locks one command, one diff scope, and two exit codes. A free model may comment only after that gate. Why unbound notes fail A long model reply can sound like a finished review. It still lacks a rerun of the failing command. Maintainers then merge model confidence instead of local evidence. This workflow splits the…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}