Records
Every run you saved, with the date on it
A score without a date is a rumour. Models get updated, providers swap the weights behind a name, and a result from March says nothing about July. So each saved run keeps the date, the model ids, the task set version and the score together.
Your runs
What a record contains
| Field | Why it is kept |
|---|---|
| Date and time | Model behaviour changes; a score is only meaningful against a date |
| Model ids | The exact ids tested, including any auto/ route — a route can resolve differently later |
| Task set version | So a score from v1 is never compared against a v2 run |
| Score per model | The headline number |
| Per-task failures | More useful than the total: it says which kind of task broke |
| Total time | Makes cost visible — the same score at half the latency is a different answer |
Where these are stored
Runs saved from Compare are stored in this browser only. They are not uploaded, and they are not visible to anyone else — which also means they do not follow you to another machine.
A shared record — every run, by everyone, on one page — needs a server-side store that does not exist yet. Until it does, this page reads your local runs and says so, rather than showing an empty list and implying nobody has ever run a test.