Runs / p4-30-reply-14-days · P4 / Inputs & outputs

Stage question · inputs and outputs

step 1 of 4 · p4-30-reply-14-days · 8409b23e21c1

Recorded with the stage: instrument ticket-intake (reader) 1.0.0 · its configuration's fingerprint
sha256:388eef47ed64…sha256:388eef47ed64d7880d08c4fec9370078db79093951d9fbe98cbf5f128138b5b0

What is shown: Outputs are stored and shown after checking; inputs from outside the run are fingerprinted, and an input's text is shown only where its step kept it and the text matches its digest.

Same in p4-29-reply-30-days · fafd4aa5a67e

Inputs

Recorded asWhat's kept
question · operator-authored

not kept

sha256:8c3df5048fd1…sha256:8c3df5048fd188a0063dac72b0e16c9fda8734ecea7fff2f7625361cd521de4d
· 87 bytes
ticket · externally-sourced

Verified kept text, matches its digest · 157 characters in all

Ticket from an example customer of an example shop. Subject: leaking kettle. Message: I bought a kettle last week and it leaks. Can I return it for a refund?
sha256:87015ed0122f…sha256:87015ed0122f6278c29ae696b849faacf4f66fe45fd9eae151b05cef5ce3ce22
· 159 bytes

A fingerprint shows whether an input changed between runs. This page shows an input's content where its bytes match a stored output of an earlier stage, or where its step kept its text and the text matches its digest.

Outputs

  • question.json ·
    sha256:4a5490ea1248…sha256:4a5490ea1248c2b62c88ddad88a32655312a3571bcefff03180711a8e86e4d78
    · 86 bytes

    Verified

    {
      "question": "I bought a kettle last week and it leaks. Can I return it for a refund?"
    }

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-31-reply-60-days-declined · 3824694f30abCompleted.onetrace.kept_inputs ticket same as this runticket-intake 1.0.0
sha256:388eef47ed64…sha256:388eef47ed64d7880d08c4fec9370078db79093951d9fbe98cbf5f128138b5b0
same as this run
question.json
sha256:4a5490ea1248…sha256:4a5490ea1248c2b62c88ddad88a32655312a3571bcefff03180711a8e86e4d78
same as this run
p4-29-reply-30-days · fafd4aa5a67eCompleted.onetrace.kept_inputs ticket same as this runticket-intake 1.0.0
sha256:388eef47ed64…sha256:388eef47ed64d7880d08c4fec9370078db79093951d9fbe98cbf5f128138b5b0
same as this run
question.json
sha256:4a5490ea1248…sha256:4a5490ea1248c2b62c88ddad88a32655312a3571bcefff03180711a8e86e4d78
same as this run
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