brugada.net · The search
Updated 16 July 2026
The point of a screen isn’t to find winners. It’s to kill things cheaply, in the right order, before they waste anyone’s time.
There are millions of small molecules. You cannot test them all in a lab — each real experiment costs money and weeks. So you test them in a computer first, in stages, cheapest first, and you throw away everything that fails. Whatever survives has earned a real experiment. That’s all a screen is.
Here the stages get progressively more honest and progressively more expensive:
A nanosecond is a billionth of a second, which sounds absurd until you remember these are individual molecules bouncing around. Twenty nanoseconds is long enough for a molecule to find a grip, settle in, get bored, and let go. Watching that happen is the entire test.
Step 2 — the fast one, the one that can rank thousands of molecules a day — was tested to see whether it could tell the broken protein from the healthy one. It cannot. The difference it reports between them is indistinguishable from noise.
That result invalidates this project’s own cheapest instrument, which is why it’s printed here in large type instead of buried in an appendix. Everything downstream has to be decided by the slow, expensive physics simulation instead. If the fast tool worked, this would be a weekend project. It doesn’t, so it isn’t.
Docking the same compounds against R104Q and wild-type gives a mean score difference of −0.01 kcal/mol (SD 0.15). Zero of 120 compounds separated beyond ±1 kcal of noise.
Splitting cationic from non-cationic compounds on raw D84 contact: Mann–Whitney p = 0.29. Statistically blind.
Across both cationic docking screens, zero purchasable compounds reproduced the bidentate grip (both carboxylate oxygens engaged). The best are monodentate — which turned out to be exactly agmatine’s eventual failure mode.
05_docking_and_pockets · 12_mechanism_fix
This is not a historical summary — it’s the current state of an automated screen that is still going. It has put 12 molecules through the 20-nanosecond test. 4 gripped and held. 6 fell off. 2 grabbed on and then let go partway through — which is the exact failure this stage exists to catch, and the reason nobody should trust a short test.
4
held the grip
6
let go entirely
2
held, then peeled off
11
waiting for the long test
Nothing has finished the long test in this round. Zero. The queue has 11 molecules in it and not one result. Anyone telling you this project has found something is reading a different page than this one.
Distances in ångströms — smaller is a tighter grip. “Occupancy” is the fraction of the second half of the run spent gripping. GO needs a tight mean and high occupancy; EARLY-ONLY is the signature of a molecule that starts well and drifts.
| Compound | 1st half (Å) | 2nd half (Å) | Occupancy | Verdict |
|---|---|---|---|---|
| ZINC000020219130 | 2.887 | 2.788 | 0.98 | GO |
| ZINC000038823067 | 2.802 | 2.736 | 1.0 | GO |
| ZINC000390834886 | 2.7 | 2.698 | 1.0 | GO |
| ZINC001857795693 | 2.708 | 2.7 | 1.0 | GO |
| ZINC000019330031 | 2.847 | 5.078 | 0.066 | EARLY-ONLY |
| ZINC000065734265 | 5.463 | 3.827 | 0.656 | EARLY-ONLY |
| ZINC000020533506 | 10.195 | 10.183 | 0.0 | NO-GO |
| ZINC000031672439 | 15.49 | 22.612 | 0.0 | NO-GO |
| ZINC000067350947 | 5.237 | 17.638 | 0.0 | NO-GO |
| ZINC000101358517 | 4.12 | 4.31 | 0.016 | NO-GO |
| ZINC001857795646 | 36.684 | 74.707 | 0.0 | NO-GO |
| ZONIPORIDE | 8.778 | 18.364 | 0.002 | NO-GO |
Look at ZINC001857795646: it ends up 74.7 Å away. It didn’t let go, it left the building. And ZINC000019330031 is the textbook case — 2.85 Å in the first half, 5.08 Å in the second, occupancy collapsing from 0.52 to 0.07. A shorter test would have called that a hit.
Queued for the long test: 4-guanidinobenzamidine, METFORMIN, ZINC000005933192, ZINC000006785879, ZINC000007717177, ZINC000008627589, ZINC000013570540, ZINC000020219130, ZINC000390834886, ZINC001857795693, ZINC000038823067. Note that metformin and 4-guanidinobenzamidine are in that queue — both were previously killed, and are being re-run as benchmarks.
r2_backups/results/ · orchestrator cycle 19 · read at build time, not transcribed
What survived from the previous round — and the problem with how it was counted →
onwards.