Diff

baseline p6-36-fill-baseline · c1dba1d637c4 against candidate p6-37-fill-exposure-changed · c7e88d418153

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

The short answer

The runs first differ at measure, where its configuration changed.

No stage comes before it. Both stages after it are the same again.

  1. measureFirst difference
  2. classifySame again
  3. reject_commandSame again

Checked from the records. The same answer every time.

What changed between the two runs

The two runs differ.

First difference: stage 1 · measure.

No stage comes before it.

Both runs' records agree. measure's recorded configuration differs (see Details). Its output differs, and 0 of the 2 stages after it changed too; 2 are the same again.

onetrace diff runs/p6-36-fill-baseline runs/p6-37-fill-exposure-changed --text

recorded as a straight line (no graph recorded)

measure · First differencemeasureFirst differenceclassify · Same againclassifySame againreject_command · Same againreject_commandSame again
  1. measureFirst difference
  2. classifySame again
  3. reject_commandSame again

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

Settings that changed

No readable setting differs; only a recorded fingerprint, under Details.

Details
StageSettingBaselineCandidate
measureconfig_digest
sha256:459d3946…05516dsha256:459d3946e4eede9afd932cd4a4dc6d89adbaaa148aef5c47d3943dbd9a05516d
sha256:9a42b08e…76a207sha256:9a42b08e2137a675abb97734dcf58109d5b1907cc81dd660b7145e4db476a207

The first difference is at stage 1 · measure. 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: measure — output text changed; settings changed

measure · First difference

settings: 1 changed

configuration fingerprint: differs, both values under Details

Details

config_digest: 459d3946e4ee → 9a42b08e2137

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

1 line removed · 1 added

11  {
2-   "fill_level_mm": "110"
2+   "fill_level_mm": "130"
33  }

classify · Same again

reject_command · Same again

Command: onetrace diff runs/p6-36-fill-baseline runs/p6-37-fill-exposure-changed --text

Repeat this yourself:

onetrace diff runs/p6-36-fill-baseline runs/p6-37-fill-exposure-changed

Other runs that recorded the same value

Matching rule: the same settings digest at stage 1 · measure, by exact equality:
sha256:9a42b08e2137….sha256:9a42b08e2137a675abb97734dcf58109d5b1907cc81dd660b7145e4db476a207

1 of 3 stored runs in P6 recorded the same settings digest at stage 1 · measure, the candidate among them.

Nothing here says what the change did in those runs.

What may have happened

This demo kept no explanation of this comparison.

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