Home / Incident

The agent kept speaking 1,960 ms after the caller interrupted.

One recording, one command, one incident with a timestamp and an id. This is the page hotato autopsy writes for the bundled example call, and the same page it writes for yours.

the command that produced everything below
$ hotato autopsy examples/autopsy/audio/autopsy-01-barge-in-say-do.example.wav
incident apx-cc33f46fad58#1 · autopsy-01-barge-in-say-do.example.wav
CRITICAL BARGE-IN apx-cc33f46fad58#1

The agent kept speaking for 1,960 ms after the caller interrupted.

barge-in · overlap 1.96s dead air 1.94s 0s 2s 4s 6s 8s 10s 12s caller takes the floor · t=2.99s
observed
t=2.99s into a 12.0s call, 2 channels, stereo
measured
overlap 1.96 s; the agent did not go silent within 3.0 s
evidence
dual-channel energy over time, one lane per party
pin
apx-cc33f46fad58 (incidents #1..#2)
The same fields land in the self-contained HTML report each run writes to hotato-output/.

What the run printed.

Every line names an incident kind, the second it happened, and the number that made it one.

hotato autopsy: autopsy-01-barge-in-say-do.example.wav  (12.0s, 2 channels, stereo)
  [CRITICAL] BARGE-IN       t=2.99s  overlap=1.96s  agent did not go silent within 3.0s
      the caller took the floor and the agent kept talking over them for 1.96 s without going quiet within 3.0 s
  [WARNING]  DEAD AIR       t=6.65s  trailing silence=1.94s  no caller energy within 0.50s
      the agent went quiet for 1.94 s with no caller energy nearby
  2 incidents: 1 critical, 1 warning
  report: hotato-output/autopsy-apx-cc33f46fad58.html
  pin: apx-cc33f46fad58  (incidents apx-cc33f46fad58#1..#2)

Generated from Hotato 1.17.1 on the example call bundled in the repo. Timing is read from energy over time, one lane per party, so each number is re-derivable from the waveform. What every verdict rests on →

Send it. Then pin it.

The id in the corner is the handle for both.

  1. 01 / SHARE

    One file, whoever owns the fix

    The run writes this report as a self-contained HTML file. Attach it to the ticket and the timeline travels with it.

  2. 02 / PIN

    The incident becomes a check

    hotato pin apx-cc33f46fad58#1 stores the evidence as a portable, content-addressed failure check.

  3. 03 / PROVE

    CI reads the exit code

    hotato prove --contracts contracts/ re-runs the stored evidence and fails closed: 0 pass, 1 fail, 2 refuse.

How the timing is measured → · how say-do is graded → · full walkthrough →

Run it on your recording.

One call in, every measured incident out, with the report already written.

$ hotato autopsy ./call.wav

pip install hotato is the whole setup. Get started →