FAILURE CARDS — SYNTHETIC LAB INJECTIONS

F-A Temporary read failure: the policy retrieval step says unavailable. No draft or queue write has happened. A second read succeeds. Use a clearly labeled simulated retry; do not fabricate a vendor error.

F-B Unknown write outcome: the review queue accepted a write for R109 revision 1, but its acknowledgment did not reach the workflow. The learner only sees a timeout initially. A later queue lookup finds record Q109. Do not create a second record. Confirm the existing effect and mark it reconciled.

F-C Permission failure: the queue returns access denied. Repeating the same write will not repair missing permission. Stop, retain the non-sensitive run reference and ask the workflow owner to inspect access. Do not weaken permissions or reconnect accounts as part of this course.

F-D Invalid AI shape: the assistant returns the status APPROVED and leaves out source_ref. The draft fails validation. It must not reach the review-ready route. One controlled correction may be attempted; failure again becomes HUMAN_REVIEW with reason invalid_output. This is separate from a network retry.

F-E Review changes content: a reviewer approved draft version 1. An edit changes duration in version 2. The old approval no longer applies. Return version 2 to pending review.

F-F Concurrent duplicate: two workers both check an empty duplicate ledger, then both attempt to create the same queue item. A check-then-write sequence alone is unsafe. In the beginner lab use one operator processing one record at a time. A production release needs a verified unique key or an atomic claim at the destination, or another proven concurrency control.