Your agent says it's done. An Agent Work Record (AWR) says who let it, what proves it and who said it was good, in one JSON file any tool can write.
Every record answers three questions:
- Who was allowed to do this? Which agent, acting for which person, with what permission, until when.
- What shows it was done? The pull request, the CI run, the screenshot, the review.
- Who said it was good? Which person accepted or rejected it, and on what basis.
It also keeps an append-only audit trail of how the work happened. A system that does not own the work, such as a CI service, can send one piece of evidence or one event as a fragment.
- The spec: spec/agent-work-record-v0.md (v0, with the additive v0.1)
- The JSON Schema: spec/agent-work-record-v0.schema.json
- A full example: spec/examples/end-to-end.json
One script, no dependencies, Node 24:
git clone https://github.com/Background-Craft/agent-work-record
cd agent-work-record
node spec/validate.mjs # every example, and every broken one fails as it should
node spec/validate.mjs my-record.json # your recordsThe check is strict on purpose: it is the writer conformance check. Readers must still ignore fields they don't know.
Writing or reading records? Add a line to IMPLEMENTERS.md with a pull request. See CONTRIBUTING.md.
Apache-2.0. See LICENSE.