Incident Timeline Extractor

How Incident Timeline Extractor works

Press Load model once: your browser downloads Gemma 4 E2B instruction-tuned (web build) (2.0 GB) from this site and keeps it in its cache. Then add your text and press Extract locally. The model runs on this device using your graphics card, so nothing you enter is sent to a server. Until the model is loaded, or if your device cannot run it, the tool falls back to a simple keyword check and labels the result as the fallback.

Gemma 4 E2B instruction-tuned (web build) is a small open language model from Google. The tool sends it the instruction below plus your text, asks for a JSON answer with fixed fields, and shows each field as a card. It runs at temperature 0, so the same input gives the same answer on the same device, though different graphics cards can word it slightly differently.

Inputs longer than 6,000 characters are cut to that length before they reach the model, and the result says so. The model only sees what you paste: it does not look anything up.

The instruction the model gets

You turn messy incident notes into a clean timeline for a postmortem. Keep the times exactly as written; do not invent times or events.

What it returns

• Timeline: One entry per event in time order, written as 'HH:MM event'. Keep the original time text.
• First sign of trouble: The earliest event that shows the problem.
• Mitigation: The action that stopped the impact, with its time.
• Impact window: From first sign of trouble to recovery, using only the times in the notes.
• Open questions: Things a postmortem should still find out, based on gaps in the notes.

Worked example

The model's output for the built-in sample, recorded on a desktop browser. Your run may word things slightly differently.

Incident notes: 09:42 deploy started, 09:48 checkout errors increased, 09:53 rollback requested, 10:01 cache purge completed, 10:08 errors returned to baseline.

Timeline

09:42 deploy started 09:48 checkout errors increased 09:53 rollback requested 10:01 cache purge completed 10:08 errors returned to baseline

First sign of trouble

09:48 checkout errors increased

Mitigation

cache purge completed at 10:01

Impact window

09:48 to 10:08

Open questions

What caused the increased checkout errors? Why was a rollback requested at 09:53? What was the cause of the errors returning to baseline at 10:08?

The model

The files are served from this site, versioned so a cached copy is never stale. Nothing is fetched from a third party while you use the tool.

Limitations

• Small language models make mistakes: they can miss an item, merge two, or state something more confidently than the text supports. Check the result against your input before you rely on it.
• It needs WebGPU and about 8 GB of memory, so it is offered on desktops and laptops, not on phones and tablets. Devices that cannot run it get the keyword fallback, clearly labelled.
• Results describe the input you gave, not the real-world situation behind it. Review them yourself before acting.

Good uses

• Triage developer workflow notes before deeper review
• Prepare consistent labels for repeat workflows
• Reduce manual sorting on small batches
• Keep sensitive drafts in the browser preview