Runs / p4-31-reply-60-days-declined · P4 / Inputs & outputs

Stage policy_check · inputs and outputs

step 3 of 3 · p4-31-reply-60-days-declined · 3824694f30ab

Recorded with the stage: instrument refund-policy (checker) 1.0.0 · its configuration's fingerprint
sha256:15365411adad…sha256:15365411adadf0ba324da9c280f369991f88ba8140d4f79688027aa3ea180e6e

What is shown: Outputs are stored and shown after checking; inputs from outside the run are fingerprinted, not stored.

Inputs

Recorded asWhat's kept
draft's recorded output · operator-authored

Verified matches the stored receipt of draft

sha256:d52124cd0c99…sha256:d52124cd0c99d1ce0eb3b11b445f57f2cab39b99f83faac12d366c81aef9ceb5
· 1664 bytes
draft.json · operator-authored

Verified matches the stored output of draft

{
  "question": "I bought a kettle last week and it leaks. Can I return it for a refund?",
  "reply": "We're sorry the kettle leaks. Please send it back within the refund window for a full refund."
}
sha256:28ee91f1478b…sha256:28ee91f1478b0243c2989623f4d63fe0575538923c7bfc2832fb350556baa202
· 190 bytes

A fingerprint shows whether an input changed between runs. This page shows an input's content only where its bytes match a stored output of an earlier stage.

Outputs

none recorded

This step in the other runs

Each other run of P4, newest first, with this step as its own receipt records it; where a run recorded the step more than once, its last attempt. "Same as this run" marks a value equal to this run's, by exact equality. Inputs are not compared across runs: an input that is an earlier step's receipt holds that run's own receipt, so it differs in every run.

RunOutcomeSettingsInstrumentOutputs
p4-30-reply-14-days · 8409b23e21c1Completed.refund_days 14refund-policy 1.0.0
sha256:15365411adad…sha256:15365411adadf0ba324da9c280f369991f88ba8140d4f79688027aa3ea180e6e
same as this run
checked.json
sha256:e7265ef350ac…sha256:e7265ef350acbe2726662c2939329353ca35d7c467d75aaa0d20c3c3a7534886
p4-29-reply-30-days · fafd4aa5a67eCompleted.refund_days 30refund-policy 1.0.0
sha256:15365411adad…sha256:15365411adadf0ba324da9c280f369991f88ba8140d4f79688027aa3ea180e6e
same as this run
checked.json
sha256:4f4a22093f01…sha256:4f4a22093f01287c2ecd1920b74b0157879691495b35e4b15f9fb0a37f528860
Signed by a known recorderYes · demo key (public seed: proves the record wasn't changed since signing, not who signed it) ·
sha256:6e20550ae0dc…sha256:6e20550ae0dc6b4471d54336d09d74d14f3f623b735045eddd053c444ec3b14c
Committed by a known timeNot anchored · no anchor beside the chain

The run, step by step