What is the adoption and standardization status of Agent Audit Record?

Internet-Draft, Intended Status: Informational; expires 19 April 2027 — phase draft, governed by Individual Internet-Draft submitted to the IETF Network Working Group; discussed on the AUDIT BoF mailing list. Adoption: unmeasured. Version: draft-gilda-audit-agent-audit-record-00 (2026-10-16). Last verified 2026-10-19.

How does Agent Audit Record compare to other account protocols?

Agent Audit Record is one of 8 standards at step 9, Account (Prove what happened; be judged). It pairs with WIMSE AI Identity Management System, An Audit Record Format for AI Agent Authorization Decisions. It builds on WIMSE AI Identity Management System. Every standard at this step is listed at https://agenticweb.wiki/category/account/.

Agent Audit Record

9 · Account

Candidate · auto-drafted, unreviewed · confidence 80%

Agent Audit Record
Category	Account
Governed by	Individual Internet-Draft submitted to the IETF Network Working Group; discussed on the AUDIT BoF mailing list
Status	Internet-Draft, Intended Status: Informational; expires 19 April 2027
Phase	draft
Implementation	unknown
Adoption	unmeasured
Version	draft-gilda-audit-agent-audit-record-00 (2026-10-16)
Specification	https://datatracker.ietf.org/doc/html/draft-gilda-audit-agent-audit-record
Found at	None defined; records are in-toto Statements in DSSE envelopes, identified by a predicateType URI
Last checked	2026-10-19
Freshness	current · checked 2026-10-19
Solves	Audit what an agent did

Agent Audit Record is an agentic-web standard (document format) at step 9, Account, governed by Individual Internet-Draft submitted to the IETF Network Working Group; its own status is "Internet-Draft, Intended Status: Informational; expires 19 April 2027" (draft). It answers: How can an AI agent's authorization decision and its observed effect be recorded in one signed, canonical record that a party trusting neither the agent nor its operator can verify from the bytes? Adoption is unmeasured, last verified 2026-10-19.

Account Defines one in-toto predicate type, signed in a DSSE envelope, for recording an AI agent's authorization decisions and the effects that followed. A record carries the decision, the observed effect and the derived agreement between them, decision-point evaluability and input freshness, and an RFC 8785 canonicalization contract so a third party can recompute consistency from the bytes. It also specifies what a retaining party keeps beside a record so it can later be dated from external anchors. It carries the seven minimum audit fields of the WIMSE AIMS framework, defines no policy, and replaces draft-gilda-wimse-agent-audit-record-02.

Discovery and probe

None defined; records are in-toto Statements in DSSE envelopes, identified by a predicateType URI

NONE 
parse:     
on absent: Support cannot be observed from a site; it is a record format exchanged between parties, not a published endpoint.

Not probed live: no-fixed-path. candidate record; probe rule pending

History

2026-10-19 — auto-drafted candidate from exa (https://datatracker.ietf.org/doc/html/draft-gilda-audit-agent-audit-record)

Instances

No instances recorded yet.

References

Internet-Draft defining an in-toto predicate type (agent-audit-record) in a DSSE envelope, carrying the decision, the observed effect, decision-point evaluability and input freshness, and an RFC 8785 canonicalization contract; carries the seven minimum audit fields of the WIMSE AIMS framework and is offered as a data model for the proposed AUDIT working group. — https://datatracker.ietf.org/doc/html/draft-gilda-audit-agent-audit-record (2026-10-16) REPORTED

JSON · Markdown