Story · arXiv
Don't Let the Model Write the YAML: Deterministic, Minimal-Diff GitOps Remediation from LLM-Proposed Field Changes (arXiv)
paper · Story page
On real Kubernetes manifests, no way of having a model write the fix was safe unattended: GNU patch applies 96% of unified diffs but silently misapplies about one in seven, and a frontier model's full-file rewrite drops a field on some runs. The alternative has the agent emit only a structured field-change intent while a deterministic parser-based pipeline makes the minimal edit.
In plain words
- Researchers found that letting artificial intelligence directly edit files controlling software was unsafe without human review.
- Generated patches, which list requested text changes, sometimes landed in the wrong place without reporting an error.
- The safer approach has artificial intelligence name the setting and replacement value, while a fixed program performs only that edit.
- This gives teams a more predictable way to automate software repairs without risking unrelated settings.
Appeared in
- Google's Mantis bug-fixing harness, and privilege escalation in 12 agent harnesses
Sep 03, 2026 · in the sections
Subscribe
Get the brief in your inbox
Pick daily, weekly, or both. Nothing is gated either way: every issue is on the site and in the feeds.
- Weekdays at 8:45am IST, one lead story and 6 to 9 items.
- Sundays, an argued synthesis rather than a recap.
- One click to leave, and quiet days say so in the subject line.