Incidentloom: Postmortem

Reconstruct the outage before you explain it. Incidentloom is an evidence workbench for engineers who write postmortems and want the timeline to survive scrutiny. Give every event its three clocks. Capture when it occurred, when someone observed it, and when a system recorded it. Let the normalizer check each wall-clock reading against its declared IANA zone. Watch it refuse to invent a time inside a daylight-saving gap and flag the fold when one reading maps to two instants. Keep the stated precision; a minute-level entry stays an honest one-minute window. Compare windows, not guesses. Read the relation between any two events as before, after, tied, overlapping, or unknown. Open the conflict drawer when sequences collide, record a disposition, and write the rationale beside it. Leave a conflict unresolved when the evidence is genuinely ambiguous; the exported package will say so. Capture evidence by hand in Scribe, or bring in CSV and JSON exports through a bounded preview that shows format, encoding, byte count, and SHA-256 checksum before anything is committed. Draft hypotheses and link the events that support or oppose them. Record decisions beside the alternatives that were on the table. Close a corrective action only with a verification record, never a checkbox. Assemble the package: a source manifest with checksums, a redaction assist for tokens and private addresses, and JSON, CSV, and PDF exports. Start from the bundled SEV-2 worked example, or create a separate incident with its own title, severity, service labels, and time zone. The workspace is stored locally. Import and export happen through your actions; you choose whether to save or share exported files. Public reference links open in the system browser.