Work loops
Built from the work loop up, not the model down
Loops in the backlog
Each will bring its own methods, evidence standards, rubric and artifact, while reusing the generic capability underneath.
plannedDataset to biomarker hypothesis
From cohort data to a candidate biomarker with a validation design.
Scientific explanation leading to hypothesis generation
plannedEvidence to mechanism
From scattered published evidence to a defensible mechanistic account.
Scientific explanation
plannedSafety-signal investigation
From a detected signal to a qualified assessment with required action.
Scientific explanation
plannedDisease biology to target hypothesis
From disease understanding to target hypotheses without a starting dataset.
Scientific hypothesis generation
plannedCompetitive pipeline assessment
From the competitive landscape to a differentiated scientific position.
Scientific explanation and scenario analysis
plannedExperimental result to next-best experiment
From a result to the experiment whose outcome would be most informative.
Scientific hypothesis generation
Why loops, and not one general-purpose scientific agent
Each loop is specialized, but most of what it needs is not. Separating the four kinds of capability is what lets validated loops accumulate into a general AI scientist instead of remaining isolated demonstrations.
- Generic AI scientist capability
- Reusable infrastructure. Built once, used by every work loop — runtime, memory, provenance, orchestration.
- Scientific skill
- A validated scientific method, reusable across related scientific problems. Versioned and testable, like a library function for science.
- Loop-specific configuration
- Unique to one work loop. The recipe, thresholds and rubric that make omics-to-target different from safety-signal investigation.
- Organization-specific context
- Your therapeutic strategy, internal datasets, platform capabilities, prior failures and scientific preferences. Cannot be bought off the shelf.