{"criteria_id":"settlement-evidence/v1","criteria_family":"settlement-evidence/v1","version":"1.0.0","corpus":{"id":"dispute-evidence-corpus/v1","sha256":"4742fb28cd75380f51e75247e97a9db2969a2c34a74d6ca720dbf10597d97161"},"corpus_pin_definition":"The corpus pin is the SHA-256 of the corpus's canonical serialization (the corpus object excluding its sha256 field), computed and verifiable by the published harness (harness.mjs).","network":"solana-mainnet","asset":{"mint":"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v","symbol":"USDC","decimals":6},"price":{"usdc_units_per_call":50000,"label":"$0.05","basis":"per packet"},"free_tier":{"per_day":100,"min_interval_ms":5000,"on_exhaustion":"402"},"input":{"body":"One JSON request body: { challenge, paymentResponse, settlementSignature?, delivery, timestamps?, caller? (free pre-check only) }. challenge is the captured 402 challenge object; paymentResponse is the PAYMENT-RESPONSE header value from the paid call (base64 JSON string; a raw JSON string or the already-decoded object are also accepted); settlementSignature is the optional explicit settlement reference (when absent, the header's transaction field is the settlement reference); delivery is the delivery artefact as received: { status, body } or { status, bodyHash } — exactly one of body / bodyHash.","challenge":"Required captured challenge. The quoted terms are taken from the challenge itself — accepts[0].payTo (recipient), accepts[0].asset, accepts[0].maxAmountRequired or amount, accepts[0].network, and the challenge memo when one is carried (challenge.memo or accepts[0].extra.memo) — never from the caller's say-so.","payment_response":"Required PAYMENT-RESPONSE header value. It is UNSIGNED (see unsigned_statement) and is never upgraded into an attestation. A header whose content cannot be decoded is recorded in the packet as a decode failure; when an explicit settlementSignature is supplied the chain leg still runs.","delivery":"Required delivery artefact AS RECEIVED by the submitting party: an object with status (integer HTTP status, 100-599) and exactly one of body (the response body as a string, recorded verbatim, with its SHA-256 computed by this service) or bodyHash (the SHA-256 hex of the body as computed by the submitter, recorded as submitted). The delivery leg is BUYER-SUBMITTED evidence and is NOT VERIFIED — see honesty_statement.","over_cap":"A request body over 262,144 bytes is a free pre-gate refusal naming the cap."},"packet_states":["SETTLED-MATCH","SETTLED-MISMATCH","NOT-FOUND","PENDING","FAILED","UNVERIFIABLE"],"engine_verdicts":["SETTLED-MATCH","SETTLED-MISMATCH","NOT-FOUND","PENDING","FAILED"],"legs":["terms_as_quoted","payment_as_settled","delivery_artefact_as_submitted"],"rules":{"honesty":"HONESTY FENCE: this packet proves what was QUOTED (the captured challenge's terms) and what was PAID (the settlement transaction as read from the chain by the settlement-evidence/v1 engine). The delivery leg is BUYER-SUBMITTED evidence: the artefact is recorded exactly as the submitting party supplied it and is NOT VERIFIED by this service — no field, grade, or summary line in the packet presents or implies the delivery as verified. A payment mismatch, when the chain disagrees with the quote, is recorded plainly in the packet; nothing is hidden or softened.","delivery_label":"BUYER-SUBMITTED — NOT VERIFIED","delivery":"The delivery artefact is recorded exactly as submitted and labelled BUYER-SUBMITTED — NOT VERIFIED on the packet's face, in this served criteria, in the catalog, and in every delivery. This service performs no check that the artefact is the response the seller actually sent, and no surface of the packet presents or implies the delivery leg as verified.","header_unsigned":"The PAYMENT-RESPONSE header is UNSIGNED: it is a plain statement emitted by seller/facilitator software (success, transaction, network, payer), not a cryptographic attestation, and its signing key story is not the payTo key. This service reports what the header IS — its decoded fields and how they compare with the challenge and with the chain — and never upgrades it into an attestation.","chain":"The settlement transaction (the explicit settlementSignature when supplied, else the header's transaction) is chain-verified with the settlement-evidence/v1 engine (verifySettlement, build/engine.mjs imported unchanged, sha256 pinned in this config) using expected fields taken from the challenge: payTo = challenge recipient, amountUnits = challenge amount (EXACT u64 equality, never >=), memo = challenge memo when carried.","mismatch_recording":"When the chain disagrees with the quote, the packet records the mismatch PLAINLY: payment_state SETTLED-MISMATCH, the mismatched field named (payment_mismatch.field), and the expected and found values both printed. A mismatch is never hidden, softened, or rounded into a match.","propagation":"The engine's NOT-FOUND, PENDING, and FAILED states propagate to the packet's payment_state unchanged and are named as such. When no settlement reference can be resolved (header undecodable and no explicit settlementSignature, or the header carries no transaction), payment_state is UNVERIFIABLE and the reason is recorded.","reverse_tx":"The packet carries a reverse_tx field that ships EMPTY (null). A seller refund transfer made later can have its signature placed in that field; the transfer is verifiable with the same engine (verifySettlement) with reversed roles (refund recipient and amount as the expected fields). This service does not itself fill the field or store packets.","signature":"The packet signature (Ed25519, service signing key) covers the packet's contents as assembled by this service: it attests that THIS service assembled these quoted terms, this chain read, and this buyer-submitted delivery artefact into this packet at the stated time, unaltered since assembly. It does NOT attest that the delivery artefact is genuine, complete, or the artefact the seller actually sent — the delivery leg is buyer-submitted and unverified.","adjudication":"Adjudication is NOT offered by this service. The packet is an evidence artefact: either party can present it to any adjudicator of their choosing. This service takes no side, issues no ruling, and awards nothing.","packet_signature_meaning":"The packet signature (Ed25519, service signing key) covers the packet's contents as assembled by this service: it attests that THIS service assembled these quoted terms, this chain read, and this buyer-submitted delivery artefact into this packet at the stated time, unaltered since assembly. It does NOT attest that the delivery artefact is genuine, complete, or the artefact the seller actually sent — the delivery leg is buyer-submitted and unverified.","no_composite_score":"Factors are printed per leg; there is NO composite score."},"engine_interface":"verifySettlement({ signature, expected }, rpc) -> verdict object; rpc is async (signature) => getTransactionResult | null. The engine is build/engine.mjs (sha256 960bf69968eba82249a0cf44f874dea3a09f17591108db03b3fb10e446248567), copied BYTE-IDENTICAL from the M-20 build and consumed through this pinned interface only; the identical block is delimited in this worker.","engine_sha256":"960bf69968eba82249a0cf44f874dea3a09f17591108db03b3fb10e446248567","boundary_b1":"Boundary vs B1 (M-20 settlement verification): B1 verifies one transaction against expected fields the caller itself supplies. B3 (this service) assembles an EVIDENCE PACKET: it takes the quoted terms from the captured challenge, chain-verifies the settlement with B1's engine imported unchanged, records the delivery artefact as buyer-submitted evidence, and signs the assembled packet. B1 returns a verdict on one transaction; B3 returns a signed multi-leg packet a party can present to an adjudicator (adjudication itself is not offered).","boundary_b2":"Boundary vs B2 (M-21 receipt verification): B2 grades one receipt (challenge + PAYMENT-RESPONSE header) field by field and returns a verdict. B3 assembles the full dispute packet — quoted terms, chain-verified payment, AND the buyer-submitted delivery artefact, plus the empty reverse-tx field — as one signed artefact. B2 does not record a delivery artefact and issues no packet; B3's payment leg reuses the same engine and the same unsigned-header discipline.","boundary_q25":"Boundary vs Q-25 (C5 subset-S reconciliation): Q-25 is a post-hoc signed report over submitted record sets inside subset S; B1 is a per-payment, per-call live chain read. The two do not share deliverables.","honesty_statement":"HONESTY FENCE: this packet proves what was QUOTED (the captured challenge's terms) and what was PAID (the settlement transaction as read from the chain by the settlement-evidence/v1 engine). The delivery leg is BUYER-SUBMITTED evidence: the artefact is recorded exactly as the submitting party supplied it and is NOT VERIFIED by this service — no field, grade, or summary line in the packet presents or implies the delivery as verified. A payment mismatch, when the chain disagrees with the quote, is recorded plainly in the packet; nothing is hidden or softened.","adjudication_statement":"Adjudication is NOT offered by this service. The packet is an evidence artefact: either party can present it to any adjudicator of their choosing. This service takes no side, issues no ruling, and awards nothing.","signature_statement":"The packet signature (Ed25519, service signing key) covers the packet's contents as assembled by this service: it attests that THIS service assembled these quoted terms, this chain read, and this buyer-submitted delivery artefact into this packet at the stated time, unaltered since assembly. It does NOT attest that the delivery artefact is genuine, complete, or the artefact the seller actually sent — the delivery leg is buyer-submitted and unverified.","custody":{"ledger_closed_fields":["payer wallet","timestamp","day","price (USDC units) with the CAD fair-market-value block (rate, rate date, basis, cad_pending, refund — null unless refunded)","payment tx id","Solana fee (lamports)","criteria version","op","verdict line","settlement signature","payment state","engine verdict","house flag"],"ledger_note":"The ledger list above is closed: adding a field is a criteria/handling version change.","retention":"Submitted challenges, receipt headers, settlement references, and delivery artefacts are read once at call time and are never stored — not in KV, not in logs, not in the payments ledger, not in metrics. The payments ledger records only the closed field list published in the criteria (payer, time, price, the service's own payment tx, the settlement transaction signature, and the payment state). Because nothing is kept, a paid retry re-sends the packet input."},"payment_includes":"$0.05 per packet. The payment includes: one signed dispute-evidence packet for the one paid call you name — the terms as quoted in the captured 402 challenge, the payment as settled on-chain (verified with the settlement-evidence/v1 engine for the settlement transaction), the delivery artefact exactly as submitted (status, and body or body hash), timestamps, and an empty reverse-transaction field a seller refund transfer can later fill. The packet is signed by this service's signing key; the signature covers the packet's contents as assembled. The delivery artefact is BUYER-SUBMITTED evidence and is NOT verified by this service — the packet proves what was quoted and what was paid, not what was delivered. The PAYMENT-RESPONSE header is UNSIGNED and is stated so plainly. Factors are printed per leg; there is NO composite score. Adjudication is NOT offered: either party can present the packet to any adjudicator. Nothing about the submitted artefacts is stored beyond the payments ledger's closed field list.","unsigned_statement":"The PAYMENT-RESPONSE header is UNSIGNED: it is a plain statement emitted by seller/facilitator software (success, transaction, network, payer), not a cryptographic attestation, and its signing key story is not the payTo key. This service reports what the header IS — its decoded fields and how they compare with the challenge and with the chain — and never upgrades it into an attestation.","kill_line":"Kill line (M-24, under the operator's 2026-11-03 zero-demand doctrine): build, bank, and hold; judged at the fleet's periodic reviews. There is NO demand kill line for this item. Tripwires, all stop-and-review: refunds >5% of paid calls in any 30-day window; free use >10x paid use; a wrong packet from undisclosed stale or partial data (stop-serving under the affected criteria version, per the corpus re-pinning discipline in the criteria); ANY presentation of a packet as 'verified delivery' (the delivery leg is buyer-submitted — the honesty fence in the criteria).","service":"dispute-packet","endpoints":{"criteria":"GET /criteria (free)","precheck":"POST /precheck (free, input-shape validation + assessability only; no chain read, no packet)","packet":"POST /packet (paid, $0.05 per packet: ONE signed dispute-evidence packet — terms as quoted, payment as settled (chain-verified), delivery artefact as submitted and labelled BUYER-SUBMITTED — NOT VERIFIED, timestamps, empty reverse-tx field; adjudication NOT offered)","metrics":"GET /metrics"}}