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

  • I-CONTRADICTS — run p1-14-candidate-set3-byte-changed · f65126968cf7, field stdout[FAIL]
    [FAIL   ] receipts/05-answer.json: output artifact 'answers.json' matches -- expected sha256:67e6ee4034ecf335d2345a175e147031b78170fcf2df340ace86b8a58a45711d, found sha256:ce7ce09108fbaf86f5466b82080950aa8be1d61836ee335e07eb286a9fb5cff4
    the report it came from

all incidents

Runs / P1 / p1-14-candidate-set3-byte-changed

p1-14-candidate-set3-byte-changed · P1

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