A new open-source gate compares what an agent says it changed with what Postgres recorded

The README describes a tool that sits between an agent and a database. Rules allow, deny or require approval for each tool call, and Deedglass then compares the agent's report with a read-back from the target. For Postgres it uses the database's change log, and it seals each result as a signed record. Its sample scene: an agent was told to mark one order shipped, its tool reported 1 row updated, and a legacy trigger shipped 300 more in the same transaction. The README says Deedglass reported "Postgres changed 301 rows" and planned an undo that waits for a person's countersignature.

The project labels how sure each check is: Claimed, Checked or Proven, with "Can't check" when it cannot tell whether a tool ran. It lists what the Proven level cannot see, including schema changes and anything outside that database's change log. The README also says the project is pre-1.0, has one maintainer and no outside penetration test, and the repository showed 2 stars when we read it. We read the README only and did not run it, so the 301-row result is the author's demonstration.

Why it matters: An agent's own log cannot show a side effect it did not know about. If agents write to production databases in your factory, the useful idea here is independent read-back after each write, whether you adopt this tool or build that check yourself.