Autonomous Settlement & Verification Ledger

What this establishes, and what it does not

• Settlement is not delivery. These rows establish USDC transfers; price matches alone do not prove a particular endpoint was called, how it was discovered, or whether a buyer received or accepted the payload. Product attribution is inferred from price where unambiguous.
• Operator-controlled wallets are labelled and excluded from every external figure. Canary traffic converts by construction and is not demand.
• A few operator test payments made while two offers shared a price are attributed from our own canary receipts instead of the amount. Each such row records the receipt source and what the amount alone would have indicated, and cannot be recomputed from the chain alone. Receipts never apply to external payers, and conflicting receipt evidence leaves a row unattributed.
• Counts cover the scanned block range only. A payer whose settlements straddle the range boundary reads as fewer settlements than they made.
• Counterparty addresses are truncated by convention. The full address is one click away on the block explorer; nothing here is concealed.