The evidence
Where the numbers come from
Around fifty live public-data connectors, seven of them load-bearing, each pinned to the snapshot it was read from — and an honest ledger of the ones that returned nothing.
The engine does not have proprietary trial data, and does not claim to. It reads the public record — thoroughly, repeatedly, and with the receipts kept — which is exactly what a defensible feasibility argument is built on.
Around fifty live connectors are pulled for a study. Seven of them are the backbone that most of the assessment leans on.
The backbone sources#
These seven carry most of the load. Each one is a public source with a published update cadence, listed in full — with what it feeds and how often it refreshes — on the data sources page and on the service status page.
- ClinicalTrials.gov — registered studies worldwide: enrollment, status, sponsors, sites, outcomes.
- AACT — the queryable relational mirror of ClinicalTrials.gov, and the analytical backbone for site and enrollment statistics.
- PubMed — the biomedical literature index behind indication baselines and standard-of-care evidence.
- FDA — approvals, labels, guidance and adverse-event signals.
- EMA — European approvals, assessment reports and scientific guidance.
- Open Targets — target–disease association evidence.
- ChEMBL — curated bioactivity data for drug-like molecules.
Beyond the backbone, the run also reaches national trial registries, preprint servers, patent offices, drug-pricing sources and public company filings, depending on what the study needs.
Snapshot pinning#
Public data moves. A trial that was recruiting in March is completed by September, and a feasibility argument that cannot say which version it read is not auditable.
- Every record pulled is pinned to the snapshot it was read from, with the date attached.
- Citations carry that snapshot date, so a number can be defended months later against the record as it stood.
- Re-running a study pulls fresh records and produces a fresh, separately pinned assessment — the earlier one is not overwritten.
The evidence ledger#
A source that returns nothing is a fact about your study, not an embarrassment to be hidden. The Evidence surface lists every connector the run touched and what it returned.
- Connectors that returned data, and how much.
- Connectors that returned nothing for this indication or molecule.
- Analyses that were consequently computed on thinner evidence — which is also why their band drops.
This is the difference between a sparse assessment and a confident one. Both are useful; only one of them is safe to act on without asking further questions, and the product tells you which you are looking at.
Freshness and third-party cadence#
Refresh cadence is set by the source, not by us. Registries and literature indexes publish daily; regulatory sources weekly; some curated databases quarterly. Where a source is behind, the assessment inherits that — which is why the snapshot date travels with the citation.
The service status page lists each dependency, what it is used for, and its stated cadence, and marks plainly which parts are third-party and outside our control.
Related
Next
The evidence
Citations & the audit trail
What a citation contains, how the hash-chained Part 11 record makes a run tamper-evident, and how to re-open a verdict long after the meeting that used it.
OpenStart here
Reading an assessment
The six pillars, the questions each one answers, and how to tell a number backed by several independent sources from one resting on a single record.
OpenThe evidence
Limits & caveats
The honest boundaries: what public data cannot tell you, which numbers are upper bounds, and where a human has to make the call.
OpenSee a verdict you can actually check.
Send us a protocol — or just a molecule and an indication. We'll return a fully cited feasibility assessment you can trace, line by line, back to public data — yours to defend in a bid, take to your board or investment committee, or hand to a regulator.