FICTIONAL CHAIN TRIAL K-01 — version A Not a customer case, measurement or resend instruction. Discuss cases as a tabletop exercise; transfer no real files. Review expectations before use. Fictional chain K-01: assess arrival, validation, processing and recovery of ten order lines. A green transport status does not prove processing. Start: scheduled delivery at 06:00. End: per-line evidence by 07:00; investigate unknown state first. Fictional times, not an SLA. Simulation only, no production transfer. Fictional source, transport log, receipt register, validator and order application. Use chain references L-001–L-005, unique lines R01–R10, version and attempt reference; all clocks in Europe/Amsterdam. Record expected and observed evidence for receipt, validation and processing per case; assess ten unique lines, alarm response and duplicate processing. No results measured yet. Test missing arrival, schema rejection, partial processing, missing processing acknowledgement and authorised recovery. Do not resend blindly when processing is unknown. Fictional roles: chain owner, source administrator, application administrator and authorised recovery decision maker. Name actual roles and backup before a real trial; no authority granted. 1. Normal chain L-001: 10 unique order lines received, valid and processed once before 07:00. Compare chain reference, receipt evidence and processing per line; transport status alone is insufficient. 2. File has not arrived L-002 is missing at 06:15; the owner investigates source and destination. No resend based only on a missing screen signal. Check expected file, source log, receipt evidence and clock. Record alarm, owner and investigation. 3. Arrived but rejected L-003 is received; validation rejects an incorrect schema. Processing remains stopped. Record error and source version. A corrected version keeps a traceable relationship with the original delivery. 4. Partially processed L-004: R01–R08 processed, R09–R10 rejected. No full resend without a recovery decision. Per-line evidence determines recovery scope; counts of 8 and 2 alone do not prove which lines were processed. 5. Processing acknowledgement missing L-005 received and valid, but processing unknown. Stop blind resubmission. Investigate application state and unique order references; a missing acknowledgement does not prove failed processing. 6. Controlled recovery For L-004 only R09–R10 are resubmitted after a recorded decision by the authorised trial owner. Final state: R01–R10 each processed once. Use a new attempt reference linked to L-004; check correction, authorisation, duplicate processing and final evidence. A simulation, not a resend instruction. Record receipt, validation and processing evidence separately in observation and evidence reference for each case. Do not prefill success. A case can include multiple stages; record unknown where evidence is missing. In a real environment store evidence with agreed access and retention, not files or secrets in this worksheet. Evaluation is a proposed decision, not production or recovery authorisation.