AAP: Agent Accountability Protocol
draft-wang-aap-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | yuqiang wang | ||
| Last updated | 2026-03-26 | ||
| Replaced by | draft-wang-jac | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-wang-jac | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines the Agent Accountability Protocol (AAP) v0.0, a minimal infrastructure layer for tracking task chains in multi- agent systems. Built on JEP [draft-wang-jep-judgment-event-protocol-01] and HJS [draft-wang-hjs-accountability-02], AAP adds a single field—task_based_on—to establish verifiable causality between tasks across agents, platforms, and trust domains. AAP follows the same narrow-waist design philosophy as JEP and HJS: a minimal mandatory core with all advanced features defined as optional extensions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)