{"criteria_id":"subset-s-reconciliation/v1","corpus":{"id":"subset-s-reconciliation-corpus/v1","sha256":"f267bb4a42ff85f48846445d100935de54e7b8c1adfd5a96b7615ad0c9df1c49","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)."},"subset_s":["S1 on-chain public finalized (Solana-USDC proven shape)","S2 memo-bound in the transaction itself","S3 enforced acceptance (s3_enforcement_evidence field; else S3-UNVERIFIED)","S4 key fixed before settlement","S5 unique per-payment nonce, singly claimed","S6 reveal available"],"s3_rule":"S3 enforcement-evidence field (design-pass settle, from c5-deepening-pass Lane 1 section 8.4): a settlement grades S3-VERIFIED only when s3_enforcement_evidence is present with attestor (non-empty), expected_memo byte-equal to the on-chain memo, rule (the settled-only-if-accepted rule applied, non-empty), and tx_signature equal to the record's signature. Otherwise the settlement grades S1, S2, S4, S5, S6 — S3 UNVERIFIED — and is never presented as a full subset-S record.","chain_scope":"Solana-USDC is the proven shape. A settlement record naming any other chain grades UNVERIFIED (chain scope): its step is never anchored and its figures print only under OPERATOR-ASSERTED.","memo_forms":{"clear_key":"subset-s:<run_id>:<task_key>:<nonce>","hashed_key":"subset-s:<sha256hex(run_id + ':' + task_key)>:<nonce>","counterparty_echo":"clear form plus a submitted challenge whose challenge_memo equals the full on-chain memo"},"factors":{"F1":"Coverage — anchored step share: steps with a resolved settlement anchor / submitted steps (count basis), both numbers printed.","F2":"Anchored share by value: settlement-anchored priced value / total priced value, per currency, both amounts printed; anchored / declared total prints only when reconciliation HOLDS EXACTLY.","F3":"Unpriced residue: UNPRICED step count, their token/usage counts in full, their asserted amounts in total (OPERATOR-ASSERTED).","F4":"Unmetered residue: UNMETERED step count, their asserted amounts in total (OPERATOR-ASSERTED), and how many carry a resolved settlement.","F5":"Task-key binding rate: binding rate (asserted) and binding rate (anchored) as two numbers, never merged; the S3-UNVERIFIED count among anchored settlements prints in the same block.","F6":"Reconciliation result: HOLDS EXACTLY (delta 0) / DOES NOT HOLD (signed delta) / CANNOT CLOSE (steps without value), under the partition identity priced total + unpriced residue + unmetered residue + unallocated remainder = declared submitted total.","F7":"Allocation disclosure: every allocation key used (K1-K5 with target sets), every remainder assignment, and the UNALLOCATED total with its step count.","F8":"Consistency observations (non-grading): steps outside the declared window; dangling retry_of references; amount != usage x unit price (both figures); ANCHOR-FAILED and DOUBLE-CLAIM steps.","F9":"Retry and duplication load: retry steps count + total; per-original retry-chain totals; branch count + per-branch totals — what repetition cost as submitted, never a waste verdict."},"labels":["SETTLEMENT-ANCHORED","OPERATOR-ASSERTED"],"no_composite_score":true,"epistemic_fence":"A third party can check that a payment was bound to a key at or before settlement — never that the task caused it. An anchored binding proves a payment was bound to a key at or before settlement; it does not prove the named task caused the payment.","coverage_block":"COVERAGE — PART OF THE RECORD. This report covers only the settlements listed in it that are individually verified against the public chain and bound, in the settlement transaction itself, to the task/run key they are listed under, with that key fixed before settlement as described in the record. For on-chain spend, settlement records are the complete and checkable evidence of what a wallet paid, to whom, in what asset and amount, and when — for the settlements so listed and bound. This report is silent for token burn and model-provider usage, and silent for off-chain billing of every kind (provider accounts, cards, invoices, subscriptions, and any charge that does not settle as a readable public-chain transaction). It is also silent for on-chain payments that are not listed, not memo-bound, made from wallets not named in the record, or settled without the binding — whether or not they belonged to the same run. Every total in this report is a total of the listed, bound, settled slice only. No total in this report is a run's total cost or a task's total cost, and no figure in this report may be presented as one, as a percentage of one, or as complete cost attribution. An anchored binding proves a payment was bound to a key at or before settlement; it does not prove the named task caused the payment. Payments absent from this report are not proven absent.","scope_sentences":["This report attributes spend to the run and task keys exactly as submitted by the operator. Settlement anchoring, where present, establishes that a payment of the stated amount settled; it does not establish that the payment was caused by, or served, the task named beside it, beyond the operator's own binding of payment to task.","This report does not establish whether any spend was necessary, efficient, well-priced for its purpose, or wasteful. Retries and duplicated branches are attributed at full submitted value; whether they should have occurred is outside this report.","This report covers only the records submitted with it, identified by the submission hash in its header. Steps the operator did not submit, runs not submitted, and costs recorded nowhere in the submission are not covered, and nothing in this report is evidence about them.","Token and model-usage figures are operator-asserted: no settlement record exists for token usage, none was anchored, and unpriced usage is reported unpriced — no rate has been estimated or applied by this service.","This report is an after-the-fact record of submitted spend. It is not a spend approval, a budget check, or a control on future spend, and it does not replace any pre-spend governance the operator may run.","A settlement-anchored figure is a figure whose payment leg was checked against a settlement record and matched exactly. Anchoring attests to the payment only; it is not a certification of the operator, the agent, the run, or the task."],"tripwire":"TRIPWIRE (published): a report circulating as proof that a named task, run, or agent action caused a settlement, incurred a cost, or was responsible for a spend = stop-and-review with serving paused — an anchored binding never establishes task causation. Keep-test: Day-0 is the first outside paid settle (house proofs never start Day-0); Day-0 + 60 days is report-only; Day-0 + 6 months is the keep/park decision. Refunds over 5% of paid calls in any rolling 30 days, or free use over 10x paid use, are stop-and-review tripwires.","boundary_m25":"Boundary vs M-25 (B4 chain-reconcile, settlement-evidence/v1): M-25 reconciles payment-to-payment — a submitted hop record set, each hop chain-verified, with ancestor-cap arithmetic over the submitted caps. This service reconciles decision-to-effect — one submitted run record (the decision side) against anchored settlement records (the effect side) inside subset S only, factors F1-F9. The two share no deliverable: this service does no hop or cap arithmetic, and M-25 issues no F1-F9 report.","retention":"Submitted records are not retained. After this report is issued, the service keeps only the submission hash, this report, aggregate counters, and the payment record for the report fee; the submitted step records are discarded.","fee_rule":{"base_units_per_block":50000,"block_steps":1000,"rule":"$0.05 per report for one run up to 1,000 steps; $0.05 per started 1,000-step block above (fee = $0.05 x ceil(steps/1000)), quoted at the free pre-check as a plain per-block fee.","attestation_rung":"NONE — no $5 attestation rung is offered (recommended against in the source design)."},"body_cap_bytes":262144,"free_tier":{"per_day":100,"min_interval_ms":5000,"on_exhaustion":"402"},"ledger_fields":["payer","ts","date","price_usdc_units","payment_tx","solana_fee_lamports","criteria_version","op","verdict_line","run_id","step_count","fee_blocks","anchored_steps","s3_unverified_count","reconciliation","house","cad_rate_usdcad","cad_rate_date","cad_basis","cad_fmv","cad_pending","refund"],"price_sources":{"PS-1":"published price list, re-readable at grading time","PS-2":"settlement-implied price","PS-3":"operator price sheet (prints as PRICED-ASSERTED)"},"allocation_keys":{"K1":"equal split","K2":"usage share","K3":"priced-value share","K4":"time share","K5":"declared weights"},"service":"subset-reconcile","version":"1.0.0","endpoints":{"criteria":"GET /criteria (free)","precheck":"POST /precheck (free: input-shape validation + F1-F9 assessability + pricing-state census + the step/block/fee quote; no settlement resolution, no report)","reconcile":"POST /reconcile (paid, per-block fee: $0.05 for one run up to 1,000 steps, $0.05 per started 1,000-step block above — the signed subset-S reconciliation report)","metrics":"GET /metrics"}}