Docs guide
These docs follow the shape of Omic itself — run an eval, compare it against a baseline, understand what moved, then gate it in CI. Each area assumes the one before it, but nothing stops you jumping straight to the reference.
If you’re brand new, start with Quick start, then Your first eval. If you already run evals locally, go straight to Set up CI.
How the docs are organized
The docs are split into areas that mirror how you actually use Omic:
•
Getting Started — install, run your first eval, and gate it in CI.
•
Concepts — runs, baselines, suites, scorers, and the .eno file format.
•
Integrations — GitHub Actions, model providers, and your own scorers.
•
Reference — the CLI, the Python SDK, and the configuration spec.
Conventions
A few things hold across every page:
•
omic — prefixed lines are shell commands.
•
.eno — files are the on-disk result of a run — portable, and yours.
•
baseline — means the run you’re comparing against, not a frozen golden set.
Getting help
Stuck or missing something?
•
Discord — the fastest way to reach the team.
•
GitHub — open an issue for bugs or gaps in these docs.
•
/ — search every page from anywhere in the docs.