1 of the 3 incidents raised from stored runs when this page was generated came from this page's reports

  • I-CONTRADICTS — run p7-41-cold-chain-decision-tampered · 1f1a56f63152, field stdout[FAIL]
    [FAIL   ] receipts/03-release.json: output artifact 'decision.json' matches -- expected sha256:ef859d7a959e824c714948716216749164b563fb8e87a7901a76f962cb809e87, found sha256:aa79bfb8d85c45f06b446282dfae7285671177667a667be8d43fc55af32abdf7
    the report it came from

all incidents

Runs / P7 / p7-41-cold-chain-decision-tampered

p7-41-cold-chain-decision-tampered · P7

recorded in the format stage-receipt-chain/0.3 · ran · received by this console

  • Records agree No
  • Signed by a known recorder Yes
  • Committed by a known time Not anchored

Not shown: this record does not hold up. Proof says why

Contradicts its record: this console's check, with the run's output files required, failed. The step-by-step comparison is not shown on this view: the record does not hold up. Proof says why

What could be re-checked

No re-check from the record was run, so this page does not say whether anything comes out the same.

Repeat the check

Run it from the run's folder:

onetrace-verify --trust trust.json MANIFEST.json

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

Where this answer came from