A verified wet-lab design assistant
You describe an experiment goal. The language model proposes the raw inputs; deterministic calculators derive every number; a verifier re-proves each derived value from its own inputs โ€” so a design cannot carry a hallucinated number.
How it works

The calculator, not the model, is the knowledge base

Frontier LLMs write confident-but-wrong numbers. Labwright changes the contract: the model only proposes raw inputs (geometry, flows, seeding), and everything derived โ€” shear stress, volumes, cell counts, dosing โ€” is computed by deterministic physics calculators and re-proved by a verifier before a design is ever submitted.

Labwright pipeline: goal โ†’ LLM proposes raw inputs โ†’ calculators derive โ†’ verifier re-proves โ†’ verified design
Pipeline: raw-in / derived-out. A number may not enter a design unless a calculator produced it and the verifier re-proved it.
What you get

Verified numbers, reverse-verified protocols

Benchmark

Bare LLM vs Labwright

Two frontier models (deepseek-v4-flash / deepseek-v4-pro), five systems, six gold sets. A design is usable only if it is internally consistent and recovers every target within ยฑ5 %.

SetSystemusable (flash)usable (pro)
24-reading
targets stated in goal
bare-LLM0 %12 %
Labwright92.5 %95.8 %
15-blind
targets not stated
bare-LLM0 %0 %
Labwright44 %49 %
15-3D-spheroid
3D-culture conventions
bare-LLM20 %27 %
Labwright93 %96 %
14-plate-culture
2D plating & seeding
bare-LLM0 %7 %
Labwright90 %79 %
14-perfused-PK
on-chip pharmacokinetics
bare-LLM36 %36 %
Labwright81 %76 %
14-new-domains
seven post-v1 domains
bare-LLMโ€”โ€”
Labwright98.6 %78.6 %

Percentages are seed-pooled usable rates (reading / new-domains ร—5 seeds, the rest ร—3; Wilson 95 % CI in the repo). Bare-LLM numbers are the single run โ€” the gap is so wide that no Labwright CI overlaps a memory-system CI on any set.

The seven post-v1 domains (barrier, oxygen, pumpless, breathing, pulsatile, scaling, gradient) were benchmarked end-to-end with the Labwright system on the 14 new-domain goals (no bare-memory baseline was run on this set). Flash submits 13/14, pro 11/14; among submitted designs hallucination is 0.000 on both. The honest boundary: the gradient-fgf8-pattern goal ends in silence on both models, and Labwright's fast-path front-end โ€” the fixed local fine-tuned extractor, trained across all eleven domains on ~61k synthetic goals โ€” answers 4/14 here (v4 scored 0/14), 5/14 with schema repair: the v6 retrain adds natural-register variants for these domains, closing part of the phrasing gap; the failures are silence-dominated rather than fabrication: six of the nine still-unanswered goals end in silence, the rest in wrong-target or calculation errors (base hallucination mean 0.512).

Memory-only systems (bare, soft-gate, self-verify) rarely produce a usable design. Labwright's derived numbers are architecturally consistent โ€” the honest headline is the blind-set drop: the gate stops fabricated numbers, but it cannot supply domain knowledge the model does not have. That boundary is the point. The gap is stable across seeds (95 % Wilson intervals never overlap the memory systems), and an iterating fix-and-resubmit agent (labwright_iter) repairs all 41 verifier-fired entries yet is a wash on usable rate โ€” iteration is a correctness loop, not a domain-knowledge loop.

Benchmark: self-consistent rate, usable rate and hallucination rate across six sets and two models
Self-consistent rate, usable rate and hallucination rate across the 24-reading, 15-blind, 15-3D-spheroid, 14-plate-culture, 14-perfused-PK and 14-new-domain sets.
Reverse-verify: per-field verdict matrix on published protocols
Reverse-verification verdict matrix on published protocols โ€” each field flagged as consistent, inconsistent, or unverifiable.

The same verifier runs over the literature: a large-scale audit (21,094 SciRecipe protocol summaries, titles resolved to Crossref DOIs) is under methodology review โ€” its lessons are shaping the evaluation framework. The verifier itself ships today.

Try it

Run it yourself

The CLI runs the exact same pipeline as the Space. Reverse verification is pure deterministic physics โ€” no API key needed; design needs a DEEPSEEK_API_KEY.