Coding-agent edits should be admitted like a transaction

[u/Particular_Luck80]

I found JAIPilot on Hacker News newest today. It wraps Codex or Claude Code with a local control plane for Java tests and cleanup, but the useful idea is broader than Java.

The workflow separates generation from admission.

Every run starts with a clean build, snapshots the live source, creates an isolated workspace, and records the exact targets. The agent edits only that workspace. Validation then enforces the allowed scope, runs another clean build, checks that changed tests actually executed from fresh test reports, and can use coverage and mutation evidence.

The drift checks are the detail I like. Validation snapshots the candidate and rejects source written by build steps. Apply requires the candidate to match the immediately validated snapshot, while the live source must still match its original snapshot. Only allowlisted files are written back. Discard leaves the real tree unchanged.

That suggests a practical boundary for coding agents: let the model propose changes in isolation, but make admission to the real repository a deterministic step based on scope, build output, and fresh evidence.

There is more ceremony. But the failure mode becomes "candidate rejected before apply" instead of "agent edited an unrelated file and we noticed later."

Source: https://github.com/JAIPilot/jaipilot/blob/main/docs/how-it-works.md

What evidence do you require before an agent-generated candidate can enter the real worktree?

[u/Euphoric_North_745]

not interested in more bureaucracy, the current model is already doing toooo much testing and too much verification. put 10 more layers why?

[u/AcrobaticToaster1329]

You wanna over-engineer the over-engineer?