Story · arXiv
Assay: Claims That Decay With the Code. Content-Addressed Evidence Graphs for Accountable AI-Assisted Software Delivery (arXiv)
paper · Story page
Every claim an agent makes, tests pass, no secrets, behavior preserved, binds to the Merkle hash of the dependency cone it covers, so it goes stale exactly when that code changes. The merge gate checks coverage, freshness and signatures, and consults no model.
In plain words
- Researchers introduced Assay to track whether evidence still supports artificial intelligence tools' claims about the software they wrote.
- Each claim is linked to an exact version of the relevant code, including other code it relies on.
- Changing any of that code makes the earlier claim outdated.
- Software teams can check that required evidence is current before accepting changes, without relying on the tool's own judgment.
Appeared in
- A forged chat-template marker loses most of its authority as ordinary subwords
Oct 01, 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.