A-Comm Technologies opened public comment on July 13 for a draft protocol aimed at a real gap in agent-driven shopping: nobody has agreed on what counts as proof when an AI agent buys something on a person's behalf. The company published the A-Comm Evidence Protocol (AEP) and is taking feedback through August 14, 2026. The premise is straightforward. Human checkout never had to prove much beyond a receipt and a card swipe. Agentic checkout is different: trustworthy agentic commerce needs three things human checkout never had to provide: observability into what an agent did and why, traceability from a consumer's intent to settlement, and auditability that any party can rely on in a dispute. AEP's answer is to turn every stage of a transaction into a signed record. Every step — discovery, referral, intent, delegation, policy, cart, authorization, and fulfillment — becomes an evidence artifact in a tamper-evident hash chain that is sealed at authorization, and the complete record then exports as portable evidence any party can independently re-verify. What's notable is the framing: AEP doesn't try to replace the protocols agents already use for payment or delegation. It acts as a witness, not a competitor to other agentic commerce protocols: it wraps the protocols already used across agentic commerce without assigning weight, outcome, or liability. That's a deliberate scope limit — it's an accountability layer, not a rail. The comment process itself is set up to be checkable rather than performative. The standard will be shaped by the ecosystem it serves: comment is open to anyone building or securing agentic commerce, and every submission receives a public, logged disposition. The spec is released under a permissive license: the A-Comm Evidence Protocol (AEP) is open-source and Apache 2.0-licensed with no fees or lock in. This lands amid a broader push toward evidentiary infrastructure for agent transactions — academic work like TessPay is proposing similar tamper-evident audit trails for dispute resolution in agentic payments, and standards bodies have been circling the same problem from the identity side (DIDs, verifiable credentials, signed agent cards). AEP is a narrower, more concrete entry: a draft spec, a comment window, a GitHub repo, and a specific claim about what an audit-ready record should contain. Whether it gets adopted depends on whether merchants, agent platforms, and payment processors actually converge on one evidence format instead of each building their own. The four-week comment window is short; it closes August 14.