Report fields
Intent: the requested behavior, acceptance criteria, constraints, and non-goals.
Changes: the files, tests, dependencies, configs, and generated artifacts touched by the agent.
Evidence: the checks that support the completion claim, including tests, CI, static analysis, traces, or human notes.
Risks: shortcut signals, sensitive files, weak proof, drift, and unknowns.
Verdict: allow, request more evidence, or block.
Example shape
The report should be short enough for reviewers to read and structured enough for systems to store. It is not a replacement for the diff; it is the map that tells reviewers where to look first.
Why it helps
Agents often summarize work in natural language. A receipt is harder to hand-wave. It forces the acceptance decision to refer to intent, evidence, and risk.