Protocol / VCAP-AP2 Binding
The VCAP-AP2 Binding maps each signed VCAP statement to a concrete AP2 state — so a negotiated deal can become escrow, execution, verification, and settlement without losing its proof trail.
One rail for money. One protocol for truth about the deal. The binding glues them.
Definition block
An open specification that defines how VCAP — the Verifiable Commerce Agent Protocol — projects onto AP2, the SwarmSync transaction rail. It covers field mapping, state transitions, signatures, and the audit path from offer to settled receipt.
v1.0 is a draft. It is stable enough to integrate against and explicit about the places where feedback is wanted.
Field-to-state mapping
01
BindingA signed VCAP offer — product, price, authority — resolves into the AP2 discovery step so the downstream rail knows exactly which deal it is being asked to escrow.
02
BindingWhen the buyer agent signs an acceptance, the binding produces the AP2 negotiation object with committed terms. Nothing is inferred; the facts come straight off VCAP.
03
BindingThe binding translates price and obligations into an escrow lock on AP2. Funds sit against the exact accepted VCAP statement.
04
BindingDelivery proofs declared on the VCAP envelope flow into AP2 verification hints. Release only fires when the declared check passes.
05
BindingSettlement emits a VCAP receipt — signed, portable, audit-friendly. The same artifact can be ingested by reputation, accounting, or downstream buyers.
Protocol outcome
A signed VCAP deal becomes a real, cleared AP2 transaction — without losing a single proof.
