Predicting binding affinity / ADMET / toxicity? Generating molecules? Running GLP studies? Orchestrating instruments via SiLA2? GreatCTO auto-attaches drug-discovery-pack (trio: drug-discovery-ml + GLP + lab-automation) with scaffold/time/cluster split, applicability-domain, uncertainty calibration, ALCOA+ data integrity, CSA validation, and IQ/OQ/PQ qualification.
rdkit · chembl · bindingdb · pdbbind · alphafold · rfdiffusion · LIMS · ELN · SiLA · GLP · GMP
The pack rides on top of your base archetype (web-service, ai-system, fintech, …) — it doesn't replace it. Auto-injects reviewer agents into the pipeline + opens human gates listed below.
Scaffold/time/cluster split + Tanimoto/sequence-identity threshold + AD bounds + UQ + retrospective validation + IP/patent FTO
21 CFR 58 + 21 CFR 211 + OECD GLP + ALCOA+ + EU GMP Annex 11 + FDA CSA (2024) + audit-trail SOP
SiLA2 + OPC-UA + LIMS chain-of-custody + IQ/OQ/PQ + protocol static analysis + scheduler safety
gate:plan + gate:ship.| Gate | Owner | Trigger |
|---|---|---|
gate:model-card-signoff | ML lead + clinical lead | before wet-lab spend |
gate:csv-validation | independent QA lead | before GLP/GMP production |
gate:iq-oq-pq | engineering + QA | per instrument qualification |
Each EVAL has ≥5 test cases, pass threshold, regression interpretation, cross-refs to TM + gates. Run via your existing test framework.
EVAL-drugml-data-leakage-target-similarity.mdEVAL-drugml-applicability-domain-coverage.mdEVAL-glp-alcoa-tamper.mdEVAL-labauto-sample-chain-of-custody.mdListed companies operate in this space. Inclusion is based on publicly available product descriptions and does not imply endorsement of or by GreatCTO.
packs: in PROJECT.md./migrate to re-run detection with updated rules.$ npx great-cto init