Diff

baseline p8-42-invoice-tolerance-2pct · 6c9049dc342a against candidate p8-43-invoice-tolerance-5pct · 1250813d6b0b

Both runs' records agree. Every check behind this is on Proof

The short answer

The runs first differ at match, where price_tolerance went from 2.00% to 5.00%.

Every stage before it is the same. The stage after it differs.

read_invoiceSame
matchFirst difference
approve_paymentChanged after it

Checked from the records. The same answer every time.

What may have happened

AI-generated, may be wrong · model anthropic:claude-sonnet-4-6

Hide the detailsShow the details

Lead (possible culprit)

The `match` node is identified as the first difference point, and its output `match.json` differs in both size and digest between baseline and candidate.

Ruled out

The `approve_payment` node is downstream of `match` and its differing input `match.json` and output `payment.json` are a consequence of the upstream change in `match`, not an independent source of divergence.

Ruled out

The `read_invoice` node, its instrument, inputs, and outputs are identical between runs, ruling it out as a source of divergence.

Checks

onetrace can run these. A lead is confirmed or ruled out only by what they report. This demo runs none of them.

onetrace match a
onetrace diff a b --text --stage match
onetrace diff a b --text --stage approve_payment
onetrace reproduce b match --runner <your runner>

6 claims checked against the record · 3 left out

3 quotes a value its cites don't hold

Its record: explain/2026-10-25T13-50-49.727866Z/, onetrace-verify: 88 pass, 0 fail, 3 not-run -> PASS (exit 0)

What changed between the two runs

The two runs differ.

First difference: stage 2 · match.

Stages identical before it: 1 of 1.

Both runs' records agree. read_invoice was the same in both. match's settings differ in price_tolerance: 2.00% → 5.00%. Its output differs, and the stage after it changed too.

onetrace diff runs/p8-42-invoice-tolerance-2pct runs/p8-43-invoice-tolerance-5pct --text

recorded as a straight line (no graph recorded)

read_invoiceSame
matchFirst differenceprice_tolerance 2.00% → 5.00%
approve_paymentChanged after it

A link shows which recorded output a stage read. It does not by itself prove that one stage caused the next.

Settings that changed

Stage	Setting	Baseline	Candidate
match	price_tolerance	2.00%	5.00%

Details

Stage	Setting	Baseline	Candidate
match	config_digest	sha256:3e1015e3…b6586b `sha256:3e1015e3c7bae9e3fb83fd2c50b8bea9bea38f7103e5ac22e0a3e8b502b6586b`	sha256:824a2366…89a060 `sha256:824a2366fff3ce418a48864bb0501ff02b8396b0cfede1f37935ae87b389a060`

The first difference is at stage 2 · match. No smaller set was reported.

The text diff

Shown with at most 200 lines per output (the SDK's default).

Open the text diff on its own page

first difference: match — output text changed; settings changed

match · First difference

settings: 2 changed

configuration fingerprint: differs, both values under Details

price_tolerance: 2.00% → 5.00%

Details

config_digest: 3e1015e3c7ba → 824a2366fff3

match.json application/json Baseline: verified Candidate: verified

4 lines removed · 2 added

11  {
22    "amount": "512.00",
3-   "matched": false,
3+   "matched": true,
44    "order": "PO-501",
5-   "problems": [
6-     "unit price 12.80 is 2.40% over the order's 12.50, past the tolerance of 2.00%"
7-   ]
5+   "problems": []
86  }

approve_payment · Changed after it

settings: none changed

input match.json (operator-authored) changed: 5b0f7e319dbf -> e61819271007; content not stored

payment.json application/json Baseline: verified Candidate: verified

4 lines removed · 2 added

11  {
22    "amount": "512.00",
3-   "decision": "hold",
4-   "problems": [
5-     "unit price 12.80 is 2.40% over the order's 12.50, past the tolerance of 2.00%"
6-   ]
3+   "decision": "pay",
4+   "problems": []
75  }

Command: onetrace diff runs/p8-42-invoice-tolerance-2pct runs/p8-43-invoice-tolerance-5pct --text

Repeat this yourself:

onetrace diff runs/p8-42-invoice-tolerance-2pct runs/p8-43-invoice-tolerance-5pct

Other runs that recorded the same value

Matching rule: the same recorded setting at stage 2 · match as the candidate, by exact equality: price_tolerance 5.00%.

3 of 4 stored runs in P8 recorded price_tolerance 5.00% at stage 2 · match, the candidate among them.

Nothing here says what the change did in those runs.

p8-43-invoice-tolerance-5pct · this comparison
p8-45-invoice-over-limit-declined · compare
p8-44-invoice-quantity-changed · compare

This record shows what was verified and evaluated at the time — not what was ultimately true.