Reliability

Don't take our word for it. Here are the numbers.

We run every employee against a fixed set of held-out tasks and grade the results with tests the employee never sees. This page shows what those runs found — including where the sample is still too small to publish, and where a run needs credentials we don't have in the test environment.

Snapshot as of 2026-09-04, generated from gate run 33916352182. Numbers below are read directly from that snapshot.

How we measure

Each employee runs its real execute_task against a fixed corpus of held-out tasks. Correctness is judged by hidden tests and structure oracles the employee never sees, not by an LLM grading itself. The metric is pass@1: the fraction of tasks solved correctly on the first attempt. A number is only called publishable once at least 30 tasks ran with zero degraded; below that it is directional and labelled as such.

Real execution

Each task calls the employee's actual execute_task path — the same code a customer would hit.

Hidden grading

Correctness is decided by hidden tests and structure oracles the employee never sees — not by a model grading itself.

pass@1

The score is the share of tasks solved correctly on the first attempt. A corpus is only “publishable” at 30+ tasks.

Publishable today

22 employees with a proven number

Each of these ran its full corpus of 30+ held-out tasks with zero degraded runs. These are the numbers we stand behind.

bastion
36 tasks, full corpus
100.0%
pass@1
blair
30 tasks, full corpus
100.0%
pass@1
finn
32 tasks, full corpus
100.0%
pass@1
forge
30 tasks, full corpus
100.0%
pass@1
guardian
34 tasks, full corpus
100.0%
pass@1
hunter
30 tasks, full corpus
100.0%
pass@1
kenna
32 tasks, full corpus
100.0%
pass@1
lexi
30 tasks, full corpus
100.0%
pass@1
madison
31 tasks, full corpus
100.0%
pass@1
morgan
30 tasks, full corpus
100.0%
pass@1
nova
33 tasks, full corpus
100.0%
pass@1
peyton
30 tasks, full corpus
100.0%
pass@1
river
30 tasks, full corpus
100.0%
pass@1
skylar
30 tasks, full corpus
100.0%
pass@1
teagan
30 tasks, full corpus
100.0%
pass@1
warren
33 tasks, full corpus
100.0%
pass@1
rankin
36 tasks, full corpus
97.2%
pass@1
codex
35 tasks, full corpus
97.1%
pass@1
prudence
34 tasks, full corpus
97.1%
pass@1
quinn
31 tasks, full corpus
96.8%
pass@1
canvas
30 tasks, full corpus
90.0%
pass@1
echo
30 tasks, full corpus
83.3%
pass@1

A score belongs here only after the whole corpus runs cleanly. Everything below is early signal we are still growing.

Directional — not yet publishable

22 employees with early signal

These corpora did not fully run — most need customer credentials the test environment doesn't hold, so only part of each corpus could be scored. A partial score is an early read, not a claim, and where one runs low we show it rather than hide it. Wiring the remaining credentials is in progress.

aria
22/33 ran
100.0%
directional
ashton
35/39 ran
100.0%
directional
avery
23/30 ran
100.0%
directional
catalyst
21/30 ran
100.0%
directional
dexter
23/33 ran
100.0%
directional
dylan
23/30 ran
100.0%
directional
juno
26/30 ran
100.0%
directional
maestro
28/30 ran
100.0%
directional
maxwell
15/15 ran
100.0%
directional
parker
20/30 ran
100.0%
directional
porter
23/30 ran
100.0%
directional
pulse
2/30 ran
100.0%
directional
riley
30/32 ran
100.0%
directional
rowan
10/13 ran
100.0%
directional
ryder
24/34 ran
100.0%
directional
sage
28/28 ran
100.0%
directional
scribe
35/40 ran
100.0%
directional
sentinel
28/32 ran
100.0%
directional
sterling
32/34 ran
100.0%
directional
scout
21/21 ran
95.2%
directional
oracle
15/15 ran
93.3%
directional
atlas
26/30 ran
92.3%
directional

For context only: the mean pass@1 across all 44 scored corpora is 98.7%. Because that average is dominated by these small samples, we treat it as directional context, not a headline. 22 corpora meet the publishable bar in gate run 33916352182. The 0.987 mean is over all scored corpora including sub-floor samples, so it is directional context, not a headline claim.

Not run this cycle

0 employees we couldn't score

These need credentials or a database that the test environment doesn't hold, so they were skipped rather than guessed. We would rather show a gap than invent a number.

What “publishable” means to us: a corpus of at least 30 held-out tasks, run against real execution with zero degraded runs, graded by hidden tests. Today that bar is met by 22 employees. Reporting it that plainly — instead of averaging small samples into a flattering headline — is the point of this page. As more corpora reach the floor, they appear here under the same rules.

Evaluating LiquidCortex and want the raw per-task detail? Email [email protected].