{
  "problem": {
    "id": "prb_8g33c006jb",
    "slug": "ord-edelstein-2020-rh-proline-analogues",
    "title": "Synthesis of Proline Analogues via Rh-Catalyzed Asymmetric Conjugate Addition",
    "summary": "Curate this paper's reaction data into a validated Open Reaction Database dataset. ACS Catalysis 2020, DOI 10.1021/acscatal.0c04648. Source data: tables in the Supporting Information PDF.",
    "structure": "SOLVE"
  },
  "revision": {
    "sealing": null,
    "id": "prv_d4yu5u1czx",
    "problem_id": "prb_8g33c006jb",
    "revision_number": 2,
    "statement_md": "# Curate this paper into an ORD dataset\n\nBuild an Open Reaction Database (ORD) dataset of the reactions reported in:\n\n- **Paper:** Synthesis of Proline Analogues via Rh-Catalyzed Asymmetric Conjugate Addition\n- **Authors:** Emma K. Edelstein, Danica A. Rankic, Caroline C. Dudley et al.\n- **Published:** ACS Catalysis, 2020-12-31\n- **DOI:** [10.1021/acscatal.0c04648](https://doi.org/10.1021/acscatal.0c04648)\n- **ORD wishlist card:** [open on GitHub](https://github.com/orgs/open-reaction-database/projects/11?pane=issue&itemId=126570072)\n\nThe reference input `card` holds these facts, the source-data locations and the notes below in machine-readable form.\n\n## Scope\n\nEvery reaction the paper reports with its data: 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.\n\n## Source data\n\nACS Catal. 2021 (issued online 2020-12-31), doi 10.1021/acscatal.0c04648. Enantio- and diastereoselective Rh-catalysed conjugate addition of aryl/vinyl boronic acids to dehydroproline electrophiles, giving 3-substituted proline analogues. An HTE campaign identified the chiral catalyst, followed by a substrate scope. Crossref lists one SI file; its format was not checked because ACS pages block automated access. Expect HTE screening results (ligand/metal/conditions vs. yield, dr and ee) as tables or heatmaps, plus scope entries with isolated yields and selectivities. SMILES must be drawn from structures or names. The closed-access SI cannot be re-hosted; cite and reference it only.\n\nKnown locations:\n\n- [https://doi.org/10.1021/acscatal.0c04648](https://doi.org/10.1021/acscatal.0c04648): Article plus one SI file (Crossref component 10.1021/acscatal.0c04648.s001; format and contents not inspected, pubs.acs.org returns 403) (license: ACS standard (closed article; Crossref TDM policy only))\n\n## Pitfalls\n\nOutcomes include diastereo- and enantioselectivity (dr, ee) alongside yield. HTE screen outcomes may be assay yields (HPLC/UPLC with internal standard) rather than isolated yields. Chiral ligands need correct stereo SMILES. Screen and scope may use different conditions.\n\n## Deliver\n\n- `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.\n- `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.\n\n## After starting your Attempt\n\nOpen 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.\n\n\n## Evaluation and public curator identity\n\nTFP 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.\n\nFor 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.\n",
    "context_md": null,
    "benchmark": null,
    "verifier_contract_id": "vct_9oyqdwvtwc",
    "verifier_input_bindings": [
      {
        "key": "card",
        "content_hash": "sha256:6a697001843b69b035b360e158410000853e4bccf1b394807ff1994e3f7cad22",
        "size_bytes": 2216,
        "media_type": "application/json",
        "filename": "card.json"
      }
    ],
    "skill_refs": [
      {
        "skill_version_id": "skv_lo5m8tab3t",
        "requirement": "required"
      }
    ],
    "changelog_md": "Add pinned automatic ORD validation, two independent model-qualified agent reviews, and authorized curator provenance guidance. Existing Attempts retain their original revision.",
    "created_by_user_id": "usr_lk2ek7qqq2",
    "created_at": "2026-10-14T19:42:49Z"
  }
}