The most common failure mode I see when teams adopt AI coding agents is not a bad diff. It is a good diff that no one can defend. The agent ran. The session closed. Three days later, somebody asks how the change came to be, and there is nothing to point at. This article is about closing that gap with three commands. Akmon's trust pipeline is audit verify , evidence verify , and slo verify . Each one is fast, deterministic, and gates cleanly in CI. With them, "the agent did it" stops being a hand wave and becomes an artifact. The code in this post uses real commands from Akmon v2.0.0. What "trust pipeline" means Every Akmon session writes two files when it ends. .akmon/audit/<session-id>.jsonl : a tamper-evident audit chain of every prompt, model response, tool call, and policy decision. .akmon/evidence/<session-id>.json : a structured evidence summary, with replay metadata and a hash that links back to the audit chain. Three commands take those files and produce signals you can trust. # 1.…