Engineering brief
Your Models Are Learning Chemist Sociology, Not Chemistry
At a glance
The brief is enough
- Relevance
- Practical value
- Time horizon
- Now
- Warnings
- None
Leash Bio ran 10,000 drug-discovery campaigns in a weekend using an RL environment built from stored screens. The catch: models trained on human-generated data learn chemist taste, not physics.
If training data encodes human choices, ML models learn people, not physics. Data provenance changes model behavior.
Watch if you're designing ML systems from historical data, or evaluating whether agent workflows truly generalize.
Summary
The claim. Leash Bio's CEO Ian Quigley argues that small-molecule drug discovery is being held back by weak data, not weak models. The company built DNA-encoded libraries (DELs) that screen millions of molecules against thousands of protein variants at basement-lab cost. He claims 2,000 protein constructs, roughly 5,000 screens, 6.5 million molecules per library, and more than 10,000 structure-activity relationship (SAR) campaigns run by language-model agents in a single weekend.
The evidence. In a Kaggle competition with about 2,000 teams, Leash released a dataset with billions of physical interactions, a thousand times larger than BindingDB. With shared building blocks, models improved. On truly novel chemistry, nobody beat chance. A separate classifier identified the chemist who made a molecule from the molecule alone with 60% top-5 accuracy across 1,815 chemists. A representation built purely from creator probabilities predicted activity as well as chemical formulas.
The trap. This is the Clever Hans problem. Models trained on public chemistry data learn the sociology of medicinal chemists: what was made, what was skipped, which building blocks the chemist likes. Heavier molecules appear to bind better mostly because chemists keep adding groups to a working lead, not because molecular weight is chemistry. Training on human-generated "exhaust" encodes intent, taste, and institutional history rather than ground-truth physics.
The fix. Leash engineered mutations in binding pockets, rescreened, and used those activity cliffs as hard negatives. Hermes, their deliberately simple cross-attention model, initially ignored binding pockets and memorized short non-conserved protein sequences as a "nickname." Adding mutation data made it spread attention across the real interaction sites. This is a concrete method for testing whether a model learns the problem or a shortcut.
The frontier. The latest shift is to language-model agents with readable English descriptions of molecules and proteins. Agents get 10 binders and 10 non-binders, choose molecules from a catalog, get instant feedback from stored screening data, and update hypotheses. That turns thousands of experiments into reinforcement rollouts. The trade-off: the environment is only as good as the data. DELs miss chemical space, have DNA-barcode artifacts, and still need wet-lab validation before molecules become drugs.
The bottom line. The most transferable lesson for engineering leaders is that data provenance is an architectural decision. If your training data reflects what people chose to build, your model may learn their behavior, not the underlying system. Teams need adversarial eval splits, negative examples from engineered perturbations, and a way to distinguish signal from style.
My take
I'm not convinced the language-agent rollout is the headline. The Clever Hans result is the strongest argument I've seen for treating data provenance as a first-class design constraint. Most ML teams still run random splits and call it validation. Leash's move to cluster-based splits and engineered mutations shows what rigorous evaluation actually costs: infrastructure, process, and people who notice batch effects. The 10,000-campaign number is a demo of the environment, not proof of better drugs. I'd be careful before generalizing it beyond that narrow assay. What I'd take back to a software org: ask who created your training data, what they chose not to do, and whether the model could predict the author instead of the task.
What to do with this
- Audit your training data for author fingerprints: build a classifier that predicts which team or person generated each sample.
- Replace random splits with cluster-based eval splits that exclude similar examples before measuring generalization.
- Turn logged human decisions into a fast RL sandbox, and test agents against historical outcomes before trusting them.
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
AI engineers are the whole team now, a leadership risk
AI engineers are told they are the team. A Moshi founder argues recommendation design, not model quality, decides whether AI tools get used.
Physical AI's real test is napkin folding, not demos
Dyna Robotics says its robots fold thousands of napkins across multiple Din Tai Fung sites. The real signal is customer validation, not the world model demo.
Digital twins are 85% accurate—but only if you collect the right data
Simile AI achieves 85% accuracy in digital twin behavior prediction, outperforming frontier models by 2-3x on niche populations. The tradeoff: proprietary…
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.