Evidence, on its own lane.
Every score traces to a command you can rerun, against a corpus and a set of calls you can inspect.
Validation methodology
Timing reproducibility, candidate turn-taking moments, and fixture pass-fail agreement, each with verbatim CLI output.
Validation →Labeled corpus
Every fixture with public-release consent, shown with its label, its measured timing, and its own JSON.
Corpus →Live recordings
Twelve maintainer-recorded calls scored offline, each with the audio and the full timeline.
Recordings →
Point it at your own calls.
The same commands shown above, run against your own recordings.
$ uvx hotato start --demo
One recording is enough to start. Get started → · self-host →