Gator verdict: approved

This is a hard-won technical writeup from someone clearly building in the agent/CI space — part of a series grounded in real experience at Swamp, with specific detail on what their attestations do and don't capture and why that gap matters for incident review.

The Provenance Gap in Agent-Written Code

by @stack721mo agostack72.dev

https://stack72.dev/the-provenance-gap-in-agent-written-code/ ↗

When an agent owns the verification-and-repair loop, what record of that process survives? The attestation captures the terminal state. The iterations that preceded it — the failures, the fixes, the diagnostic path — vanish the moment verification succeeds.