The .eno format, explained

A run is written to a single .eno file. This post walks through what is inside one, how to read it without our tooling, and why we published the spec instead of keeping it internal.

What’s inside

Three things: the cases and their outputs, the scores each scorer returned, and the provenance — the commit, the model, and the settings used for the run. That is enough to reproduce a comparison months later without asking anyone what the configuration was.

Reading one

Use omic show to inspect a run from the terminal, omic diff to compare two directly, or omic export --json to convert it for your own tooling. None of those require an account.

Why the spec is public

Because the format is the guarantee. If you stop paying for Cloud, your history becomes read-only and nothing is deleted — but that promise only means something if you can read the files without us. So the spec is public, and it stays public.