Tatsächliche Eingabe
- Prompt versions and change intent
- A: Summarize the incident. Be concise and provide root cause, owner, and resolution date. B: Summarize only supplied incident evidence. Separate observed impact, confirmed cause, hypotheses, actions, owner, and date. Use unknown where absent and list the next verification. Change hypothesis: B reduces invented causes and commitments while remaining useful.
- Matched test inputs and outputs
- Same ChatGPT configuration, no tools, one run each. C1 database timeout: source names Dana owner and 30 Aug date but cause pending. A says root cause connection-pool exhaustion; B marks cause unknown and repeats owner/date. C2 conflicting notes: deploy suspected by engineer, metrics show errors started before deploy; no owner/date. A selects deploy and assigns SRE today; B preserves conflict and asks for timeline verification. C3 complete postmortem: confirmed expired certificate, Lee owner, fixed 12:10. Both accurate; A 72 words, B 118. C4 empty note. A invents monitoring failure and Ops owner; B returns insufficient evidence. C5 long routine incident with confirmed cause/action but no date. Both accurate; B says date unknown. Reviewer labels supplied for fidelity and usefulness.
- Success criteria and release context
- Hard gates: no invented cause, owner, date; material conflicts retained. Then fidelity 40%, action usefulness 30%, clarity 20%, concision 10%. Five convenience cases are diagnostic, not representative. Any hard-gate failure blocks adoption. Incident manager decides; one reviewer only.







