{"id":"comp-risk-register-from-incident-notes","audience":"compliance","category":"legal-compliance","track":"legal","level":"intermediate","technique":"constraints","title":"Turn four incident notes into risk register entries as JSON","free":false,"task":"Turn the incident notes into risk register entries. Output one JSON array in one code block, nothing else. Merge incidents with the same cause into one entry. Each object has exactly these keys: risk, source_incident, first_reported, owner, status, likelihood, impact. risk is under 12 words, source_incident is one string of the incident ids joined by \"; \", first_reported is the earliest incident date as YYYY-MM-DD, owner comes from the notes (Unassigned if none), status is Proposed, and likelihood and impact are both TBD because the risk owner rates them.","materialLabel":"Incident log (attached to your prompt automatically)","material":"INCIDENT LOG, October 2026 (Corvane Insurance, fictional)\n\nINC-114 (Oct 3): A courier delivered 40 printed customer statements to the wrong office. Owner: Ines Varga, Mailroom. Statements were retrieved the same day.\n\nINC-118 (Oct 9): The overnight sanctions-screening batch job failed. 212 onboarding checks were delayed by one day. Owner: Tomas Eklund, Onboarding Ops.\n\nINC-121 (Oct 14): A second parcel from the same courier, 12 statements, went to the wrong office. Owner: Ines Varga, Mailroom.\n\nINC-125 (Oct 20): The AP clerk found a vendor invoice approved with only one signature. The second-signature rule applies above $5,000. Nobody has been named to follow up.","rules":[{"type":"codeBlocks","count":1},{"type":"maxProseWords","max":15}],"mistakes":[{"title":"Not merging duplicates","why":"The AI gives each incident its own entry.","fix":"Say: \"Merge incidents with the same cause into one entry.\"","checks":["r0"]},{"title":"Inventing ratings","why":"The AI fills in likelihood and impact scores.","fix":"Say: \"likelihood and impact are both TBD.\"","checks":["r1"]},{"title":"Guessing owners","why":"The AI assigns someone to the invoice issue.","fix":"Say: \"owner is Unassigned if the notes name nobody.\"","checks":["r2"]},{"title":"Extra code blocks or chatter","why":"The AI adds a second block or explains around the code.","fix":"Say: \"One code block only, no text outside it.\"","checks":["codeBlocks"]},{"title":"Chatter around the block","why":"The AI adds an intro and notes outside the code.","fix":"Say: \"Output only the code block, no other text.\"","checks":["maxProseWords"]}],"promptHints":[{"label":"Merge duplicates","patterns":["merge","same cause"]},{"label":"Exact keys","patterns":["risk","source_incident","owner","status","likelihood","impact","first_reported"]},{"label":"TBD ratings","patterns":["tbd"]},{"label":"Unassigned owner","patterns":["unassigned"]},{"label":"Code block only","patterns":["one code block","only the (json|code)","nothing else"]},{"label":"Date format","patterns":["yyyy-mm-dd"]}],"hint":"Name the exact keys, the id and date formats, and say to merge same-cause incidents.","mission":"Convert incident notes into proposed risk register entries.","musts":["Merge same-cause incidents","Ratings stay TBD","Owner from the log"],"rubricLabels":["Output is one valid JSON array with exactly three objects, because INC-114 and INC-121 are merged into one entry","Every object has exactly the keys risk, source_incident, first_reported, owner, status, likelihood, impact; status is Proposed and likelihood and impact are TBD in all three","Owners are Ines Varga, Tomas Eklund and Unassigned; source_incident is a string like \"INC-114; INC-121\" and first_reported is 2026-10-03, 2026-10-09 and 2026-10-20 respectively"]}