Yuval Kainan and Carmit Hershman proposed Agentic Process Evidence (APE) in an arXiv submission dated 29 October 2026. The authors describe APE as signed, tamper-evident, machine-readable evidence linking AI agent sessions to their outcomes, intended to make software development processes more accountable.[1]

The abstract identifies a gap between recording code changes and recording the decisions behind them. It argues that a git log does not capture what an agent did, which model it used, which tools it called, or who was accountable. The authors group the resulting procedural problems into software supply-chain risk, compliance with organizational policies, and alignment with assigned tasks and goals.[1]

APE is presented as process-aware logging that supports policy-as-code controls and human intervention when needed. The authors say it supports an in-toto-style attestation framework and aligns with relevant regulations. The saved abstract does not name those regulations or provide enough detail to assess that alignment; its descriptions of signatures and tamper evidence remain proposal claims here.[1]

[1]: Agentic process evidence. arXiv, 29 October 2026. https://arxiv.org/abs/2610.40071

Sources

  1. Agentic process evidencearXiv · 29 Oct 2026

Check or correct this page

Verification record

The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.

796019a7bdf252569131b291538c17e9bb484eb31abf2831359af60d41256ea6