Source Map
This page maps research-facing claims to primary sources. If a claim does not
have a stable primary source, it is explicitly marked for verification instead
of being promoted as fact.
AUMP Sources
| Claim |
Primary source |
| AUMP defines portable mandates for authority, preferences, negotiation policy, disclosure policy, escalation policy, evidence, and binding references. |
AUMP specification, Scope |
Agents must not act autonomously under mandates whose status is not active. |
AUMP specification, Mandate Lifecycle |
| Mandates include principal, agent, purpose, authority, preferences, negotiation, disclosure, escalation, and evidence fields. |
AUMP specification, Mandate Object |
Evaluate Action returns allowed, requires_escalation, or denied. |
AUMP specification, Evaluate Action |
| Downstream protocols should carry AUMP mandate ID, hash, URL when appropriate, and version rather than full private mandates. |
AUMP specification, Binding References |
AUMP canonical hashes are sha256- prefixed hashes of canonical unsigned mandate JSON. |
AUMP specification, Canonical Mandate Hash |
| Conformance requires schema validation, status and expiration enforcement, hard constraints, disclosure rules, action decisions, revocation, and evidence for material commitments. |
AUMP specification, Conformance |
Neighboring Protocol Sources
| Claim |
Primary source |
MCP defines _meta as a metadata field and includes structured tool result fields. |
MCP schema reference |
MCP tool annotations include readOnlyHint, destructiveHint, and idempotentHint, and annotations are treated as hints rather than as the whole policy boundary. |
MCP ToolAnnotations |
| A2A is an open protocol for communication and interoperability between opaque agentic applications, including agent discovery, modality negotiation, long-running collaboration, and collaboration without exposing internal state. |
Agent2Agent protocol repository |
| UCP includes discovery, governance, capability negotiation, profile advertisement, schema resolution, and payment architecture concepts for agentic commerce. |
UCP specification overview |
| AP2 packages user intent and payment context into verifiable credentials such as intent, cart, and payment mandates. |
Agent Payments Protocol introduction |
| OpenAI's Agentic Commerce Protocol is an open standard co-developed with Stripe for connecting buyers, AI agents, and businesses to complete purchases. |
OpenAI Instant Checkout announcement, ACP repository |
| JSON Schema is the validation technology family used for AUMP schemas. |
JSON Schema specification |
| RFC 2119 and RFC 8174 define the normative keyword interpretation used by the AUMP specification. |
RFC 2119, RFC 8174 |
Enterprise and Regulatory Sources
| Claim |
Primary source |
| Project Deal demonstrated a real internal marketplace where AI agents represented people, posted listings, negotiated, and closed deals without a prebaked negotiation protocol. |
Anthropic, Project Deal |
| Project Deal reported 186 deals across over 500 listed items and found that model quality affected objective market outcomes in ways participants did not always perceive. |
Anthropic, Project Deal |
| NIST AI RMF is voluntary guidance for organizations designing, developing, deploying, or using AI systems to manage AI risks. |
NIST AI RMF announcement |
| NIST AI 600-1 is a Generative AI Profile of the AI RMF that helps organizations manage risks for a specific technology and context. |
NIST AI 600-1 PDF |
| OWASP's GenAI Security Project covers LLMs, agentic AI systems, and AI-driven applications. |
OWASP Top 10 for LLM Applications |
| U.S. fair-housing obligations for home-buying examples should be mapped from HUD/Fair Housing Act resources into compliance profiles. |
HUD Fair Housing Act overview |
Source Status Pattern
Project Deal is now source-verified as a motivating research scenario. It is
not yet a canonical spec example or conformance fixture. Treat any Project
Deal-specific fixture, benchmark, or adoption claim as needing source
verification until it lands in the spec, conformance, or examples repositories.
flowchart TB
claim[Research claim] --> source{Stable primary source?}
source -->|yes| cite[Use direct footnote or source map row]
source -->|no| verify[Mark as needing source verification]
cite --> docs[Publish in docs]
verify --> docs
Claims Needing Source Verification
| Claim |
Verification needed |
| AUMP has external production adopters. |
Link to public implementation, release notes, or adopter statement. |
| AUMP is governed by a foundation or standards body. |
Link to governance charter or official announcement. |
| AUMP improves negotiation outcomes by a measured percentage. |
Link to dataset, evaluator implementation, methodology, and reproduction script. |
| AUMP prevents all private preference leakage. |
Replace with bounded test result; absolute prevention needs a formal threat model and proof. |