{"id":"cx-chat-log-utc-timeline-duration","audience":"it","category":"support-work","technique":"verification","track":"support","level":"advanced","title":"Build a UTC incident timeline from a chat log with mixed time zones","free":false,"task":"Convert each event to UTC and list them oldest first, one per line in the form \"HH:MM UTC - event\" (event under 6 words), then a last line \"Duration: N minutes\" from the alert to resolution. Eastern Standard Time is UTC minus 5 and Pacific Standard Time is UTC minus 8 on Nov 5. Plain text, under 70 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"INCIDENT CHAT LOG (Nov 5)\n- 9:58 a.m. ET: first customer report arrives in support.\n- 6:55 a.m. PT: monitoring alert fires.\n- 15:10 UTC: engineer starts the fix.\n- 10:30 a.m. ET: status page updated.\n- 16:05 UTC: resolved and confirmed.\n\nNOTE\nTimes are written as people typed them in the log, so the order in the log is not the order they happened. Daylight saving ended on Nov 1, so the offsets above are the ones to use. Duration is measured from the alert to the resolution.","rules":[{"type":"plainText"},{"type":"maxWords","max":70}],"mistakes":[{"title":"Keeping the log order","why":"The AI lists events as typed.","fix":"Say: \"Oldest first after converting to UTC.\"","checks":["r0"]},{"title":"Wrong offset","why":"The AI adds 4 or 7 hours.","fix":"Say: \"ET is UTC minus 5, PT is UTC minus 8.\"","checks":["r0"]},{"title":"Duration from the customer report","why":"The AI starts at 14:58.","fix":"Say: \"Duration is from the alert to resolution.\"","checks":["r2"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords","r1"]}],"promptHints":[{"label":"States the offsets","patterns":["utc minus 5","utc minus 8","add 5","add 8"]},{"label":"Asks for oldest first","patterns":["oldest first","chronological"]},{"label":"Gives the line form","patterns":["hh:mm utc","duration:"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]}],"hint":"State the offsets, the sort order, the line format and how duration is measured.","mission":"Build a UTC timeline of the chat and the incident's duration.","musts":["Convert to UTC","Oldest first","Duration in minutes"],"rubricLabels":["The events are listed oldest first as 14:55 UTC alert, 14:58 UTC first customer report, 15:10 UTC fix started, 15:30 UTC status page updated, 16:05 UTC resolved","Each line has the form \"HH:MM UTC - event\" with a short event","The last line is exactly \"Duration: 70 minutes\""]}