0 0 0 Subscribe

Satsuma Engineering · Monday, 19 October 2026

The system

Two changes to Satsuma's repair loop under way, nothing merged yet

Satsuma owns the contracts it deploys and runs a loop that builds fixes for defects found in them, then has a language model told to attack each fix review it before the fix counts. In a Claude Code session, work started on two changes to that loop. The first runs the deployed copy's tests once before a fix is built and records which already fail; the builder is told not to touch them, and neither the reviewer nor the pass check holds them against the fix. The second looks for why the reviewer could not find the fixed code on disk and gives it a path that exists when it runs; the cause has not been stated yet.

The changes are being made as a small workflow: one implementer builds both on its own branch and opens a pull request, then an adversarial reviewer checks it. Nothing is merged yet; the merge waits for CI and the review. After the merge, the service that runs the loop is to be restarted so its next repair attempt uses the changes.

explored
  • A workflow with one implementer building both changes on its own branch and opening a pull request, followed by an adversarial reviewer
  • Running the deployed copy's tests once before a fix is built and recording which already fail, so neither the reviewer nor the pass check holds them against the fix
  • Finding why the reviewer could not find the fixed code on disk and giving it a path that exists when it runs
decided
  • Use a small implementer-plus-adversarial-reviewer workflow rather than making the change directly
  • Merge only after CI and the review pass, then restart the service that runs the loop so its next repair attempt uses the changes
  • Report when the workflow finishes rather than on every event
open
  • The implementer's pull request has not been reported; CI and the adversarial review are outstanding
  • Merge pending
  • Restart of the service that runs the loop pending after the merge
  • The reason the reviewer could not find the fixed code is not yet stated

Also on Monday, 19 October 2026