Documentation

Docs / Benchmark Results

Benchmark Results

As of March 15, 2026, the live IsoPose registry at /static/wasm/demo_assets/isopose_targets_v1.json contains 48 GOLD_LOCKED entries:

  • 46 launch-roster targets
  • 2 native-docking variants (CDK2 (Native Docking) and P38A (Native Docking))

This page replaces the older 14-target snapshot with the current registry-backed benchmark table.

How These AUCs Are Collected

  • Values are pulled from the target bundles referenced by the live registry.
  • The page prefers bundle-level benchmark fields in this order: manifest.auc, manifest.validation.full_set_auc, manifest.validation.expected_auc, then explicit registry promotion fields or lock notes when the manifest only stores routing overrides.
  • Launch-roster targets are listed separately from native variants so the public launch set stays easy to scan.

Reading The Table

AUC Interpretation
>= 0.90 Excellent discrimination
0.80 - 0.899 Strong validation signal
0.70 - 0.799 Launch-usable with clear caveats
< 0.70 Gold-locked only where the bundle is intentionally retained for an honest product path or a native-variant diagnostic track

Registry Snapshot

  • Launch roster: 46/46 GOLD_LOCKED
  • Native variants: 2/2 GOLD_LOCKED
  • Docs note: the benchmark table now mirrors the live bundle metadata instead of a hand-maintained subset list

Launch Roster

Target Family Current AUC Source
A2A GPCR 0.816 Bundle expected validation
ACE (Geometric) General 0.979 Bundle full-set validation
ACE (IsoPose) Metalloprotease 0.979 Bundle full-set validation
AChE General 0.842 Registry reference lock
ADRB2 (IsoPose) General 0.834 Bundle manifest
AKT1 General 0.850 Bundle manifest
AmpC General 0.827 Bundle expected validation
AR General 0.721 Bundle manifest
AURKA General 0.818 Bundle manifest
BACE1 Aspartyl Protease 0.941 Bundle expected validation
BCL2 General 0.768 Bundle/lock note
BRAF General 0.888 Bundle manifest
CATL General 0.842 Bundle manifest
CDK2 Kinase 0.756 Bundle full-set validation
COX2 (IsoPose) General 0.894 Bundle manifest
CTSK General 0.804 Bundle manifest
DHFR (IsoPose) General 0.879 Bundle manifest
EGFR Kinase 0.933 Bundle expected validation
ESR1 Nuclear Receptor 0.839 Bundle full-set validation
FKBP1A General 0.939 Bundle manifest
FXa Serine Protease 0.792 Bundle expected validation
GBA General 0.806 Bundle expected validation
HDAC2 General 0.985 Bundle expected validation
HIV1PR (IsoPose) General 0.928 Bundle manifest
HIVRT (IsoPose) General 0.700 Registry wave3 promotion
HMGR General 0.946 Bundle manifest
HSP90 Chaperone 0.844 Bundle expected validation
JAK2 General 0.908 Bundle manifest
JNK1 General 0.604 Bundle/lock note
MCL1 PPI hotspot 0.915 Bundle expected validation
MDM2 (IsoPose) PPI hotspot 0.849 Bundle full-set validation
MMP2 General 0.705 Bundle manifest
NA General 0.942 Bundle manifest
P38A Kinase 0.826 Bundle expected validation
PARP1 DNA repair 0.786 Bundle expected validation
PDE5 General 0.877 Bundle full-set validation
PNP General 0.832 Bundle manifest
PPARA General 0.917 Bundle manifest
PPARG (IsoPose) General 0.670 Registry wave3 promotion
RXR General 0.974 Bundle full-set validation
SIRT2 General 0.772 Bundle manifest
SRC (IsoPose) General 0.759 Bundle manifest
Thrombin Serine Protease 0.800 Bundle expected validation
TS General 0.836 Bundle manifest
UROK General 0.792 Bundle expected validation
VEGFR2 General 0.733 Bundle manifest

Native Variants

Target Family Current AUC Source
CDK2 (Native Docking) Kinase 0.700 Bundle expected validation
P38A (Native Docking) Kinase 0.826 Bundle expected validation

Notes

  • Bundle manifest means the pack ships a direct auc value in manifest.json.
  • Bundle full-set validation and Bundle expected validation come from the bundle's validation block and are used where the product path is pinned to the validated benchmark configuration.
  • Registry reference lock, Registry wave3 promotion, and Bundle/lock note appear only where the gold-lock decision was recorded outside the standard manifest fields.
  • Some families are shown as General because the bundle metadata does not currently provide a more specific class label.