Diff

baseline p7-39-cold-chain-baseline · 1430d422a164 against candidate p7-40-cold-chain-one-reading-changed · 24b9fadf3a0d

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

The short answer

The runs first differ at fill_gaps, where input logger changed.

No stage comes before it. Both stages after it differ.

  1. fill_gapsFirst difference
  2. excursion_checkChanged after it
  3. releaseChanged after it

Checked from the records. The same answer every time.

What changed between the two runs

The two runs differ.

First difference: stage 1 · fill_gaps.

No stage comes before it.

input logger changed: 709f68a73b08 -> 6752c73d29ad · the changed lines

Both runs' records agree. No recorded setting of fill_gaps differs. Its output differs, and all 2 stages after it changed too.

onetrace diff runs/p7-39-cold-chain-baseline runs/p7-40-cold-chain-one-reading-changed --text

recorded as a straight line (no graph recorded)

fill_gaps · First differencefill_gapsFirst differenceexcursion_check · Changed after itexcursion_checkChanged after itrelease · Changed after itreleaseChanged after it
  1. fill_gapsFirst difference
  2. excursion_checkChanged after it
  3. releaseChanged 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

No recorded setting differs between the two runs.

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

fill_gaps · First difference

settings: none changed

input logger (externally-sourced) changed: 709f68a73b08 -> 6752c73d29ad; text kept

logger kept input text Baseline: verified Candidate: verified

1 line removed · 1 added

33  0,4.1
44  10,4.2
55  20,4.4
6- 30,4.6
6+ 30,9.4
77  40,
88  50,4.7
99  60,4.5

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

2 lines removed · 2 added

1818      {
1919        "filled": false,
2020        "minute": "30",
21-       "temp_c": "4.6"
21+       "temp_c": "9.4"
2222      },
2323      {
2424        "filled": true,
2525        "minute": "40",
26-       "temp_c": "4.6"
26+       "temp_c": "9.4"
2727      },
2828      {
2929        "filled": false,

excursion_check · Changed after it

settings: none changed

input filled.json (operator-authored) changed: 70d05ede16e8 -> f4e8f20a1362; content not stored

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

1 line removed · 12 added

11  {
22    "allowed_c": "2.0 to 8.0",
3-   "excursions": []
3+   "excursions": [
4+     {
5+       "filled": false,
6+       "minute": "30",
7+       "temp_c": "9.4"
8+     },
9+     {
10+       "filled": true,
11+       "minute": "40",
12+       "temp_c": "9.4"
13+     }
14+   ]
415  }

release · Changed after it

settings: none changed

input excursions.json (operator-authored) changed: d2ecf56c0f10 -> efa46b61912c; content not stored

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

2 lines removed · 2 added

11  {
2-   "decision": "release",
2+   "decision": "quarantine",
3-   "excursions": "0"
3+   "excursions": "2"
44  }

Command: onetrace diff runs/p7-39-cold-chain-baseline runs/p7-40-cold-chain-one-reading-changed --text

Repeat this yourself:

onetrace diff runs/p7-39-cold-chain-baseline runs/p7-40-cold-chain-one-reading-changed

Other runs that recorded the same value

Matching rule: the same input logger digest at stage 1 · fill_gaps, by exact equality:
sha256:6752c73d29ad….sha256:6752c73d29adf47b578f4c92d54e5fbe8d730cb4d67340f3bb9606960183ef0e

1 of 3 stored runs in P7 recorded the same input logger digest at stage 1 · fill_gaps, 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.