# WARDALE Commerce Assurance

UCP-first delegated authority and execution assurance. The evaluation binds an organisation's permission and shared budget to specific operations, records provider-native outcomes, and supplies independently verifiable evidence.

## Implemented evaluation profiles

Adyen Visa and Mastercard TEST payment authorisation; Revolut Merchant sandbox order creation; PayPal sandbox checkout order creation. All four profiles have passing local HTTP-fixture tests. An order-created result is not a completed payment. Provider-account runs are a distinct evidence level.

## Operator integration

A Node 22 single-host evaluation runner uses the existing WOS authority engine. Connect only approved sandbox credentials, identify the accountable operator and agent, select the permitted scope and spending limit, and preserve the private local ledger. The client submits an order identifier and retry identifier; it cannot supply its own approval, amount or merchant.

The evaluation lasts at most 30 days. All evaluation operations are non-billable. Budget is reserved before network execution, including across providers. A timeout remains reserved for reconciliation; switching providers does not permit repeating an uncertain operation. Historical results remain retrievable without re-executing the payment.

In the approved source checkout:

```sh
npx tsx scripts/commerce-evidence-runner.ts --preflight
npx tsx scripts/commerce-evidence-runner.ts --output=commerce-evidence.json
```

The default runner uses local HTTP fixtures and makes no external payment request. An account-connected run additionally requires `--sandbox`, explicit `WOS_SANDBOX_CONSENT=I_AUTHORISE_PROVIDER_SANDBOX_ONLY`, and a private persistent `WOS_SANDBOX_STATE_DIR`. Credentials enter secure operator configuration, never GitHub issues, logs or public evidence. One USD 1.00 operation per selected profile is admitted, and subsequent identical requests recover the recorded outcome. Keep the same ledger; do not reset it to retry uncertain payment operations.

## Machine introduction

Read the descriptor at `https://wardale.io/.well-known/commerce-assurance.json`, the read-only OpenAPI at `https://wardale.io/.well-known/commerce-assurance-openapi.json`, and release metadata at `https://wardale.io/api/v1/commerce/evidence`.

## Evidence verification

The published local test report covers 36 adapter and ledger cases. The verification script accepts a runner's JSON evidence file plus a public key obtained from a separately trusted source. It verifies exact payload signatures, sequence, linked hashes and retry result identity. Check the file hash against the release record to detect omissions as well as altered records. Local fixture outcomes, provider sandbox outcomes, network certification and settlement are separate evidence categories.

## Participate

Developers, merchants and payment integrators can start a bounded evaluation through `https://wardale.io/build` or discuss an integration at `https://wardale.io/contact`. The core authority engine remains protected. Public interoperability descriptions and verifier examples are provided for evaluation; they do not imply a payment-network endorsement.