Methodology

How MBRS evaluates biological risk

MBRS is a biology-first system designed to surface differentiation, mispricing, and landscape shifts before clinical outcomes are known.

We quantify how drugs interact with biology, how those interactions translate into disease-relevant effects, and how each program compares within its competitive landscape.

Biological modeling & signal extraction

Systematically model drug–biology interactions to identify the underlying signals that drive efficacy and risk.

Disease alignment & outcome inference

Evaluate whether those signals restore, conflict with, or amplify disease biology to infer likely outcomes.

Ecosystem mapping & differentiation

Position each asset within its indication landscape to measure competitive density and biological advantage.

Integrated scoring & issuance

Combine signals into standardized outputs that enable cross-program comparison and decision-making.

Current MBRS oracle signal check

Where MBRS is currently most useful

We model mechanistic-biological risk, not regulatory approval or failure. The oracle run below asks a narrower and more useful question: when MBRS makes a high-margin biological call, does that stronger separation align with labeled real-world outcomes often enough to support risk triage and prioritization?

Current signal readout
Loading latest oracle run metrics…

Reading the deployed oracle run CSVs from the public plots folder.

High-margin accuracy
Higher-confidence calls at margin ≥0.50.
Coverage at that margin
Share of labeled calls retained.
Balanced accuracy
Calibration context, not the primary claim.
Labeled outcomes
Approved + Failed OOF records.
What this supports

Use MBRS as a biological risk-prioritization layer: high-margin calls help flag programs that deserve deeper diligence, comparison, or caution.

What it does not claim

MBRS is not presented as a standalone regulatory approval predictor; lower precision and calibration scores are shown to keep that boundary explicit.

Why approval labels are noisy

The current demo set is oncology-heavy, where approval decisions can accept more toxicity and uncertainty than many other indications. That can blur direct approval/failure calibration.

Real-world decision benchmark context
Context only. These benchmarks show why a biology-first signal can still add value.
Decision settingReported benchmarkWhy it matters for MBRS
Drug development base rate~14% Phase I→approval (2006–2022)Low base rate → small signal improvements matter
Current clinical success environment10.8% overall success (2023); Phase I 48%, Phase III 66%Uncertainty persists late → biology signal remains relevant
VC portfolio realityMajority of VC funds underperform public marketsPower-law outcomes → filtering matters more than prediction
BD / M&A executionFrequent miss on timelines and revenue post-acquisitionForecast error risk → biology adds downside checks
MBRS high-margin subset accuracy on of labeled approval/failure calls.Core signal: high-confidence biological separation
Sources: BIO/Informa/QLS clinical success report; Schuhmacher et al. 2025; IQVIA Global Trends in R&D 2024; Kauffman Foundation VC report; L.E.K. pharmaceutical M&A portfolio analysis.
Class-level calibration table
These values explain where the current oracle run is still conservative: broad labels and direct approval calls are harder than high-margin biological separation.
ClassPrecisionRecallF1Correct / totalMean marginCalibrationReadout
Loading class-level metrics…
Latest oracle run category margin histogram

Category margin shows how separated the model’s top biological call is from the competing class. This is the current advantage: margin filtering reveals the subset where MBRS is most informative, without overstating it as outcome prediction.

Calibration context
These metrics are still useful, but they should be read after the high-margin signal.

Simple readout: MBRS is strongest when margin is high. At that threshold, biological separation aligns with outcomes at a useful rate. Broad approval/failure metrics remain calibration-limited and should be treated as context, not the core signal.

Note: this page is intentionally high-level. Proprietary methods and model details are omitted.