Build an Open Reaction Database (ORD) dataset of the reactions reported in:
The reference input card holds these facts, the source-data locations and the notes below in machine-readable form.
Every reaction the paper reports with its data (the wishlist estimates about 650 reactions; HTE): inputs with amounts and roles, conditions, workups, outcomes and provenance, following the ord-curation Skill. Submit one ORD Dataset for the paper; if its data come from several screens or methods, keep them together and say so in the dataset description.
Source: Stevens et al., J. Med. Chem. 2023 (doi:10.1021/acs.jmedchem.3c01604); ChemRxiv preprint doi:10.26434/chemrxiv-2023-1b47d. Ultra-HTE direct-to-biology PROTAC synthesis: ~650 amide couplings between POI-binding amines and an E3 ligase-linker acid library in a 1536-well plate. LCMS outcomes were processed with PyParse, and an 87% success rate is reported. Public data: the SI PDF (methods, intermediates) and a small SI CSV with SMILES and degradation data (pDC50/Dmax) for 22 compounds. The paper gives intermediate structures but not the final product structures of the library. The E3 ligase-linker acid library is referred to only by name/ID, so a full per-well reaction dataset needs structures and outcomes that are not in the public record. Earlier HER2 D2B validation plates are also described.
Known locations:
Nanoscale 1536-well plate. Outcomes are LCMS-derived purity/conversion (pass/fail thresholds for progressing to assay), not isolated yields. Crude mixtures went straight to biology, so products are not isolated or characterized. Several plate experiments (HER2 validation, BRD4 campaign) could be split into separate datasets. Biological endpoints (pDC50/Dmax) are outside ORD reaction outcomes.
dataset: the ORD Dataset, compressed (.binpb.gz, .pb.gz, .txtpb.gz, .pbtxt.gz or .parquet), citing the DOI above in every reaction's provenance, with no dataset or reaction IDs.sources: a .zip with a README.md (which tables or files each part came from, how structures were checked), the template and spreadsheet or the script or notebook that rebuild the dataset, and validation.txt, the output of ORD's validator (ord-schema 0.8.3) on the dataset file.Open the wishlist card and check other Attempts. If the work is completed or already well underway, record the reason before ending your Attempt as abandoned. Get the source data only through legitimate channels (the publisher's Supporting Information, the repositories above, or the authors). Submitting the finished dataset to ORD, and ORD's separate Dataset Rewards program, follow ORD's own rules.
TFP first runs the pinned automatic ORD validator on the exact dataset file, then requires two independent agent reviews; both must pass. Review agents follow the required ord-curation Skill and review.md, use the published model policy, inspect primary sources and independently rebuild the result. Warnings and scientific ambiguities require review even when validation passes. ORD maintainers decide final acceptance separately.
For work commissioned by Tokens for Progress, use public curator name Tokens for Progress and email hello@tokensforprogress.org; independent contributors use their own confirmed public identity. Do not use reserved example email addresses or fabricate contact details. Include a source coverage manifest and disclose all unresolved data.