{"id":"ops-door-damage-timeline-corrected-clock","audience":"operations","category":"operations-work","track":"operations","technique":"verification","level":"advanced","title":"Build an incident timeline correcting a camera clock, without blame","free":false,"task":"Write a prompt for a markdown table with columns Time, Event and Source and exactly five rows in time order, then one line starting \"Conflicts:\". Use 24-hour times. Correct any source whose clock is known to be off and show the corrected time. The Conflicts line notes where accounts disagree or cannot be verified. Do not say who was at fault. Under 190 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"INCIDENT: Dock door 3 frame damaged - Tuesday\n\nGATE LOG: Truck T-5521 (Calder Freight) entered 13:52, exited 14:40.\n\nCCTV (door 3 camera): IT checked on Monday and found this camera's clock runs 4 minutes fast. Camera shows: 14:12 truck begins backing to door 3. 14:13 trailer corner touches door frame. 14:15 truck pulls forward and stops. 14:16 driver steps out.\n\nDRIVER STATEMENT (Aziz Karim): \"I had the all-clear from the dock lead. It was around 2:10 when I felt a bump. The door seal was already bent when I got there.\"\n\nRADIO LOG: Dock lead Joel Pike reported \"door 3 damaged\" to the supervisor at 14:11.\n\nMAINTENANCE INSPECTION (Wednesday): Frame bent at top left, seal torn. Photos taken. The inspection does not say when the seal was damaged.\n\nNo injuries. Claims and fault are decided by the safety lead and the carrier relations manager.","rules":[{"type":"maxWords","max":190}],"promptHints":[{"label":"Names the columns","patterns":["time.*event.*source","table"]},{"label":"Fixes the clock","patterns":["4 minutes","subtract","corrected","fast"]},{"label":"Asks for a Conflicts line","patterns":["conflicts:","disagree","verified"]},{"label":"Rules out fault","patterns":["fault","blame"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]}],"mistakes":[{"title":"Using the raw camera times","why":"The AI copies 14:12 and 14:13 from the CCTV.","fix":"Say: \"The CCTV clock runs 4 minutes fast; subtract 4 and show it.\"","checks":["r1"]},{"title":"Assigning fault","why":"The AI concludes the driver caused the damage.","fix":"Say: \"Do not say who was at fault.\"","checks":["r2"]},{"title":"Wrong row count","why":"The AI lists every minor event or leaves out the gate rows.","fix":"Say: \"Exactly five rows\" and name them.","checks":["r0"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"hint":"Name the columns, say how to fix the camera clock and what the Conflicts line holds.","mission":"Build the door damage timeline, fixing the camera clock.","musts":["Show corrected times","Exactly 5 rows","No fault assigned"],"rubricLabels":["The output is a markdown table with the columns Time, Event and Source and exactly five rows in time order, followed by a line starting \"Conflicts:\"","The CCTV events use corrected times (14:08 backing and 14:09 contact, 4 minutes earlier than shown) and the other rows include the 13:52 gate entry, the 14:11 radio report and the 14:40 exit","The Conflicts line notes the driver's \"around 2:10\" versus the corrected 14:09 and that the claim the seal was already bent is not verified, and nothing says who was at fault"]}