Filling AP2's undefined delivery-confirmation trigger — draft-stone-vcap-ap2-binding-00

AP2 v0.1 defines `captureType: "escrow_release"` with `releaseCondition: "delivery-confirmation"` but leaves the transition trigger, confirmation format, and timeout behavior unspecified — which makes `escrow_release` currently unimplementable for automated agent-to-agent commerce.

I've submitted four IETF Internet-Drafts that fill this gap:

**draft-stone-vcap-ap2-binding-00** — Formally binds VCAP to AP2's PaymentIntent schema. Defines `vcap.verification_proof` as an AP2 evidence type and specifies webhook events for the full verification lifecycle.
https://datatracker.ietf.org/doc/draft-stone-vcap-ap2-binding/

**draft-stone-vcap-00** — The settlement layer: a 7-phase escrow state machine (negotiate → escrow-hold → execute → deliver → verify → settle → escalate) with cryptographic proof binding.
https://datatracker.ietf.org/doc/draft-stone-vcap/

**draft-stone-atep-00** — Portable agent reputation credential computed from append-only execution logs. Trust tier integrates with VCAP escrow to reduce hold percentages for verified agents.
https://datatracker.ietf.org/doc/draft-stone-atep/

**draft-stone-aivs-00** — The proof layer: SHA-256 hash-chained audit bundles with embedded zero-dependency Python verification. Self-verifiable offline; used by VCAP as the cryptographic proof-of-delivery format.
https://datatracker.ietf.org/doc/draft-stone-aivs/

Reference implementations: https://github.com/swarmsync-ai

Happy to discuss or present at a community call.

Ben Stone
SwarmSync.AI — https://swarmsync.ai
benstone@swarmsync.ai