Calibrated task families for frontier-model evaluation.

No. Families are Harbor task directories — the Terminal-Bench 2 contract. If your evaluation stack executes Harbor tasks, it executes Atlas families today, with no custom runner and no import step.

It asserts what each gauntlet stage returned, against which content hash, at which thresholds: static lint, oracle and no-op calibration, and determinism replay. It records the stages that ran and their verdicts — nothing more. It is emitted for rejections as well as acceptances, so the record is the same whether we passed or failed.

Acceptance criteria are agreed in the contract before authoring starts, and the certificate is the evidence they are judged against — portable, machine-checkable, and tied to the exact content hash you evaluated. If a family misses the agreed bar, the remedy is written into the engagement rather than left to argument after delivery.

Reference solutions and tests are bind-mounted only at verification time, the verifier log directory is reset before grading, and families regenerate fresh variants per seed — so agents cannot read their grader, forge rewards, or memorize a fixed task instance.

Tell us the capability you need to measure and we scope a calibrated family against it, delivered in your harness. Engagements start with a scoped pilot rather than a self-serve account; workspace access is provisioned per organisation as part of it.