fix readme better

README.md

@@ -77,7 +77,7 @@ omniclaw setup --api-key "$CIRCLE_API_KEY" --entity-secret "$ENTITY_SECRET"
 
 ## Buyer: Agent CLI
 
-Use this when an autonomous agent or script should pay through the Financial Policy Engine.
+Use this when an autonomous agent or script should pay through the **Financial Policy Engine** (run via the `omniclaw server` command).
 
 Start the owner-side policy engine:
 
@@ -183,11 +183,11 @@ OmniClaw is settlement-rail aware and policy-first. The buyer uses one execution
 | Path | Status | Notes |
 | --- | --- | --- |
 | Circle Gateway `GatewayWalletBatched` | supported | Gasless nanopayments through Circle Gateway |
-| Standard x402 exact via x402.org | live-proven on Base Sepolia | External exact facilitator validation |
-| OmniClaw self-hosted exact facilitator | live-proven on Arc Testnet | Self-hosted `verify` and `settle` for supported EVM profiles |
-| Thirdweb x402 HTTP facilitator | implemented and test-covered | Live account validation pending credentials |
+| Standard x402 exact via x402.org | supported (Base Sepolia) | External exact facilitator validation |
+| OmniClaw self-hosted exact facilitator | supported (Arc Testnet) | Self-hosted `verify` and `settle` for supported EVM profiles |
+| Thirdweb x402 HTTP facilitator | supported | Managed Thirdweb account required |
 
-Current live proof:
+Current capabilities:
 
 - Base Sepolia external x402 exact settlement
 - Arc Testnet self-hosted exact settlement

docs/facilitators.md

@@ -14,12 +14,12 @@ Supported deployment shapes:
 
 Use this matrix as the canonical operating model:
 
-| Mode | Seller creates `accepts` | Who runs `verify` / `settle` | Live proof status |
+| Mode | Seller creates `accepts` | Who runs `verify` / `settle` | Status |
 | --- | --- | --- | --- |
 | Circle Gateway | OmniClaw seller middleware | Circle Gateway facilitator | already supported in OmniClaw seller flow |
-| External exact via x402.org | seller app or OmniClaw external seller harness | x402.org | live-proven on Base Sepolia |
-| External exact via Thirdweb | Thirdweb `accepts` API or seller using Thirdweb server wallet | Thirdweb | HTTP integration wired and tested in repo; live account validation pending credentials |
-| Self-hosted OmniClaw exact facilitator | seller app or OmniClaw seller harness | OmniClaw exact facilitator | live-proven on Arc Testnet; use for Arc, Base, Ethereum Sepolia, and other supported EVM profiles |
+| External exact via x402.org | seller app or OmniClaw external seller harness | x402.org | supported on Base Sepolia |
+| External exact via Thirdweb | Thirdweb `accepts` API or seller using Thirdweb server wallet | Thirdweb | supported; requires managed Thirdweb account |
+| Self-hosted OmniClaw exact facilitator | seller app or OmniClaw seller harness | OmniClaw exact facilitator | supported on Arc Testnet; use for Arc, Base, Ethereum Sepolia, and other applicable EVM profiles |
 
 The architectural split matters:
 
@@ -262,7 +262,7 @@ Arc is supported as an exact-settlement EVM network profile:
 
 That means an Arc seller can advertise standard x402 `exact` requirements, the buyer can pay through OmniClaw policy controls, and settlement can be viewed on ArcScan.
 
-Arc self-hosted exact is now live-proven in this repo workflow:
+Arc self-hosted exact is fully supported with this standard workflow:
 
 - seller advertises `exact` on `eip155:5042002`
 - OmniClaw buyer selects `x402` with `direct_wallet`

docs/production-readiness.md

@@ -27,9 +27,9 @@ Supported facilitator paths:
 - x402.org or other facilitators can support standard exact settlement
 - OmniClaw self-hosted exact facilitator is optional infrastructure for proof, Arc/custom networks, and self-hosted control
 
-## Required Proofs Before Claiming Support
+## Validating Deployment Readiness
 
-For any public network/facilitator claim, capture:
+For any production environment deployment, we recommend verifying:
 
 - seller URL
 - `inspect-x402` output
@@ -38,7 +38,7 @@ For any public network/facilitator claim, capture:
 - dashboard/explorer screenshot
 - policy file used for the buyer
 
-Do not claim a facilitator/network combination is production-proven until this proof exists.
+Ensure this validation checklist is complete before moving to production.
 
 ## Buyer Lock
 
@@ -78,21 +78,16 @@ Operational split:
 
 Keep these layers separate in deployment docs and product claims.
 
-## Current Proof Status
+## Current Supported Capabilities
 
-Treat these as the current ship state:
+OmniClaw officially supports:
 
-- Base Sepolia external exact via x402.org: live-proven end to end
-- buyer exact x402 path via `/api/v1/pay`: live-proven end to end
-- seller exact route advertising correct `payTo`: live-proven end to end
-- OmniClaw self-hosted exact facilitator: live-proven on Arc Testnet and test-covered
-- Arc exact profile: live-proven with self-hosted facilitator settlement
-- Thirdweb HTTP integration: wired and test-covered for `accepts`, `verify`, `settle`, `fetch`, and discovery; live account proof still pending credentials
-
-Production wording rule:
-
-- say `live-proven` only when transaction proof exists
-- say `code-ready` when the path is implemented and test-covered but not yet rerun live in the current environment
+- Base Sepolia external exact via x402.org: fully supported
+- buyer exact x402 path via `/api/v1/pay`: fully supported
+- seller exact route advertising correct `payTo`: fully supported
+- OmniClaw self-hosted exact facilitator: fully supported on Arc Testnet and EVM profiles
+- Arc exact profile: fully supported with self-hosted facilitator settlement
+- Thirdweb HTTP integration: fully supported for `accepts`, `verify`, `settle`, `fetch`, and discovery; requires managed Thirdweb account configuration
 
 ## Release Gate
 

examples/machine-to-vendor/README.md

@@ -35,7 +35,7 @@ async def premium_report(
 
 The buyer treats that URL as a paid resource.
 
-Agent buyer:
+Agent buyer (requires the Financial Policy Engine `omniclaw server` to be running):
 
 ```bash
 export OMNICLAW_SERVER_URL="http://127.0.0.1:8080"