Agent Change Record: evidence for agent work

Coding agents can now produce large, plausible diffs faster than reviewers can reconstruct the work behind them. The missing object is not another dashboard. It is a durable artifact that travels with the repository.

Agent Change Record v0.1 is that artifact.

An ACR is a deterministic JSON projection of one Agentplane task. It records the task intent, the accepted plan, the agent and toolchain context, policy decisions, changed files, verification results, approvals, evidence pointers, and closure state. It is generated from the same task lifecycle that Agentplane already writes into .agentplane/tasks/<task-id>/.

The point of naming it is practical. Review tools, CI gates, security scanners, and future agent runners need a stable thing to parse. "The agent said it ran tests" is not stable. A repo-local acr.json validated against an open schema is.

Generate one:

agentplane acr generate <task-id> --work-commit HEAD --write

Validate it:

agentplane acr validate .agentplane/tasks/<task-id>/acr.json

Use it as a merge gate:

agentplane acr check <task-id> --require-plan-approved --require-verification

ACR v0.1 is intentionally narrow. It does not store prompts, transcripts, private tool output, or model internals. It stores evidence pointers and hashes: enough for review, audit, and handoff without turning agent context into a second source of truth.

The trust model stays local-first. The repository remains the record. Agentplane derives the ACR from task files, policy state, verification evidence, and Git revisions, then validates the result against @agentplane/spec.

The schema is public:

https://agentplane.org/schemas/acr-v0.1.schema.json

In 0.5, the runner work can build on this artifact instead of inventing a separate reporting layer. Runner execution should produce the same kind of durable evidence that human-supervised agent work does today. ACR is the shared record that makes that possible.