Next gen: a record of how agents worked (signed, replayable provenance for agent changes) issue #299
open andymccall opened this · 0 comments
andymccall
Andy's next-gen list (2026-10-24), fifth. Every change an agent makes carries a signed record of how it was produced: the session and grant, the tools it ran, the files it read, the commands and checks it ran, linked from the change and its proposal. Reviewers can audit or replay it; policies can require it for agent changes. As agents write more of the code, this is the compliance answer git cannot give. Builds on keyless agent grants and certificates (issue #241).
Andy's next-gen list (2026-10-24), fifth. Every change an agent makes carries a signed record of how it was produced: the session and grant, the tools it ran, the files it read, the commands and checks it ran, linked from the change and its proposal. Reviewers can audit or replay it; policies can require it for agent changes. As agents write more of the code, this is the compliance answer git cannot give. Builds on keyless agent grants and certificates (issue #241).