MechInfer is an independent assessment of a programme's evidence. It takes the mechanism and the data you have, and returns the quantities you cannot measure directly, the probability that the whole path from molecule to patient holds, where that path is weakest, and the measurement that would most change the answer.
It is built on mechanism-informed inference: a declared model of the process that produced the data, fitted by Bayesian inference, reported as a calibrated distribution rather than a point estimate. Where the data cannot support a quantity at all, that is the finding, and it is reported as such rather than computed anyway.
The page below is arranged so that it can be checked: the benchmark, the reanalyses, the document you would receive, the method, and what the method does not do.
The framework is checked against published reference values rather than against itself. On the standard population pharmacokinetic benchmark — the theophylline dataset, 12 subjects, 132 samples — it recovers the published estimates:
| Parameter | Posterior median | 95% interval | Published | Ratio |
|---|---|---|---|---|
| Clearance | 0.0400 L/h/kg | 0.0333 – 0.0483 | 0.0403 | 0.99 |
| Volume | 0.459 L/kg | 0.414 – 0.508 | 0.458 | 1.00 |
| Absorption rate | 1.51 1/h | 1.01 – 2.31 | 1.57 | 0.96 |
The claim that matters is not the agreement in the last column but the calibration: the 95% posterior intervals contain 94.7% of the observations, against a nominal 95%. An interval that is honest about its own width is the only kind worth propagating into a decision.
Published studies, reanalysed with the same core, to show what the method finds in real data. These are methodological: the point is what a design can and cannot support, not a verdict on anyone's science.
In a published gut–liver barrier transport study, the signal had levelled off before the first measurement at 30 minutes. A permeability calculated from those points describes the sampling schedule rather than the barrier, so it is reported as not estimable. One sample inside the first ten minutes would recover it. The same fit confirms the authors' conclusion on the combination of agents and puts an interval on it: 1.90× control, 1.61 – 2.22.
Reanalysis of published transport data, two-concentration control check: observed 11.6×, interval 5.3 – 36.1, containing the predicted 20×.In a published single-concentration drug screen, the Hill slope cannot be identified from one concentration per compound. Fixing it is unavoidable; what it costs is measurable. Across plausible slopes the implied potencies move by a median factor of 2.5, and for the most potent compounds by 33. Three of eighteen measurements report no activity — those are bounds, not values, and are reported as bounds.
Reanalysis of a published RBD–ACE2 repurposing screen, 18 compound–strain measurements.Strain difference per compound from the same published screen, with 95% credible intervals. Teal where the data support a difference, grey where the interval spans one. Two compounds are an order of magnitude more potent against the variant, which percentages of 45 → 95 and 57 → 99 obscure: the percentage scale compresses exactly where inhibition approaches complete.
The process that produced the data is written down, with parameters that mean something physically: clearance, permeability, potency. Nothing is learned from a corpus. The structure is declared, so it can be argued with, and the fit can contradict it.
A development decision rests on a sequence of separate studies. Each is propagated on common posterior draws, so correlations induced upstream survive into the joint result. The chain reports two different weakest links — the one least likely to hold, and the one least well evidenced. They are rarely the same link, and reporting only the first is how a chain of weak evidence comes to look like a confident conclusion.
Every uncertain quantity is ranked by how much measuring it would change what the programme does, at a stated measurement precision rather than a perfect one. A quantity can carry wide uncertainty and still be worth nothing to measure, if no value it could take would alter the decision. Weak evidence and decision relevance are different things, and only one of them is worth an experiment.
The inference core, the modules built on it, and the scripts that reproduce every number on this page are maintained as a single codebase. It is the working platform rather than a public release, but any number on this page can be reproduced on request, with the script that produces it.
Send the decision you are facing and the evidence you have. Published or summary-level data is enough to begin.