Diff

A is the baseline demo-run-1 · 56032cb26229; B is the candidate demo-run-2 · 1880b4aa455b.

What changed between the two runs

The two runs differ.

tests ×2

tests (1st) · Same
tests (2nd) · Same

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

#	node	baseline	candidate	annotations	result
1	request	1	1		Same
2	context	2	2		Same
3	tests (1st)	3	3		Same
4	tests (2nd)	4	4		Same
5	model	5	5	instrument config_digest differs: sha256:a125ee0261f9a07bf3f58e1baba061c3a111d63624a66ddef6e1fa0477009a27 -> sha256:157ee8ba61daebe690746b2142fe14b7afa765cb0e3a9de80063e94b79c8fbf8; constant seed differs; output model-output.json differs	First difference
6	proposal	6	6	input model-output.json differs; output proposal.json differs	Changed after it
7	config applied	7	7	input proposal.json differs; output auth.json differs	Changed after it

Why model's output differs is not established by this evidence.

The text diff

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

first difference: model — output text changed; settings changed

model · FIRST DIFFERENCE

settings: 2 changed

instrument.config_digest: a125ee0261f9 -> 157ee8ba61da

constants.seed: 42 -> 17

model-output.json application/json verified

  {
    "action": {
      "changes": {
-       "auth_env": "production"
+       "auth_env": "staging"
      },
      "target": "auth_service",
      "type": "modify_config"

proposal · downstream

settings: none changed

input model-output.json (operator-authored) changed: 30e8e872af1f -> 3e6759062698; content not stored

proposal.json application/json verified

  {
    "changes": {
-     "auth_env": "production"
+     "auth_env": "staging"
    },
    "target": "auth_service",
    "type": "modify_config"

config applied · downstream

settings: none changed

input proposal.json (operator-authored) changed: 37520e6db342 -> bae93e89f127; content not stored

auth.json application/json verified

  {
-   "auth_env": "production"
+   "auth_env": "staging"
  }

Command: python -m onetrace diff RUN_A RUN_B --text --json --no-follow

The diff report as the SDK wrote it, with names from the records escaped

baseline   (the baseline run's folder)  demo-run-1  (run)
candidate  (the candidate run's folder)  demo-run-2  (run)

diff: diverged

node            A     B     verdict
--------------------------------------------------------------------
request         1     1     same
context         2     2     same
tests#1         3     3     same
tests#2         4     4     same
model           5     5     FIRST DIFFERENCE
                            instrument config_digest differs: sha256:a125ee0261f9a07bf3f58e1baba061c3a111d63624a66ddef6e1fa0477009a27 -> sha256:157ee8ba61daebe690746b2142fe14b7afa765cb0e3a9de80063e94b79c8fbf8
                            constant seed differs
                            output model-output.json differs
proposal        6     6     downstream
                            input model-output.json differs
                            output proposal.json differs
config applied  7     7     downstream
                            input proposal.json differs
                            output auth.json differs

first difference  model
comparisons performed 7 of 7 nodes; same 4, FIRST DIFFERENCE 1, downstream 2, reconverged 0, COULD NOT CHECK 0

carried:
  [baseline] [NOT-RUN] receipts/01-request.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/02-context.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/03-tests_1.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/04-tests_2.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/05-model.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/06-proposal.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/07-config-applied.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/01-request.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/02-context.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/03-tests_1.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/04-tests_2.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/05-model.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/06-proposal.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/07-config-applied.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
signing [baseline]: [SIGNED-UNTRUSTED] signatures/1.json: signature -- signed by an untrusted key sha256:311dc2859bb2dfcfa2c94184b682fff3f535ec4c8867c1437a29123b4c626777 -- signer not on the reader's trust list (claimed signer "reference demo")
signing [candidate]: [SIGNED-UNTRUSTED] signatures/1.json: signature -- signed by an untrusted key sha256:311dc2859bb2dfcfa2c94184b682fff3f535ec4c8867c1437a29123b4c626777 -- signer not on the reader's trust list (claimed signer "reference demo")

Repeat this yourself:

python -m onetrace diff RUN_A RUN_B --out OUT

Not shown for graph-shaped runs: where the change started, and other runs with the same change.

This console draws where the change started only for two linear runs; the SDK's localize report for this pair is below, as it wrote it.

The localize report as the SDK wrote it, with names from the records escaped

baseline   (the baseline run's folder)  demo-run-1  (run)
candidate  (the candidate run's folder)  demo-run-2  (run)

localize: diverged

node            A     B     verdict
--------------------------------------------------------------------
request         1     1     same
context         2     2     same
tests#1         3     3     same
tests#2         4     4     same
model           5     5     FIRST DIFFERENCE
                            instrument config_digest differs: sha256:a125ee0261f9a07bf3f58e1baba061c3a111d63624a66ddef6e1fa0477009a27 -> sha256:157ee8ba61daebe690746b2142fe14b7afa765cb0e3a9de80063e94b79c8fbf8
                            constant seed differs
                            output model-output.json differs
proposal        6     6     downstream
                            input model-output.json differs
                            output proposal.json differs
config applied  7     7     downstream
                            input proposal.json differs
                            output auth.json differs

first difference  model
comparisons performed 7 of 7 nodes; same 4, FIRST DIFFERENCE 1, downstream 2, reconverged 0, COULD NOT CHECK 0

CAUSE at node 'model'
  instrument   stand-in-model  1.0.0 -> 1.0.0
  config       a125ee0261f9 -> 157ee8ba61da
    constant seed differs
  blast radius not applicable — run-scoped

carried:
  [baseline] [NOT-RUN] receipts/01-request.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/02-context.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/03-tests_1.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/04-tests_2.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/05-model.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/06-proposal.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [baseline] [NOT-RUN] receipts/07-config-applied.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/01-request.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/02-context.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/03-tests_1.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/04-tests_2.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/05-model.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/06-proposal.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
  [candidate] [NOT-RUN] receipts/07-config-applied.json: originality -- record is declared unanchored; this verifier can establish consistency, not originality
signing [baseline]: [SIGNED-UNTRUSTED] signatures/1.json: signature -- signed by an untrusted key sha256:311dc2859bb2dfcfa2c94184b682fff3f535ec4c8867c1437a29123b4c626777 -- signer not on the reader's trust list (claimed signer "reference demo")
signing [candidate]: [SIGNED-UNTRUSTED] signatures/1.json: signature -- signed by an untrusted key sha256:311dc2859bb2dfcfa2c94184b682fff3f535ec4c8867c1437a29123b4c626777 -- signer not on the reader's trust list (claimed signer "reference demo")

Repeat this yourself:

python -m onetrace localize RUN_A RUN_B --out OUT

Other runs with the same change are not looked for: this console doesn't match a graph comparison's first differences against other runs.

Compared with onetrace 0.2.0, build wheel:0e8df2304582e1ab7, at 2026-10-10 19:42:47 UTC.

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