{
  "problem": {
    "id": "prb_op53ig24fs",
    "slug": "ord-deprez-2023-nemtabrutinib-biaryl-ether",
    "title": "Manufacturing Process Development for the Biaryl Ether Fragment of Nemtabrutinib (MK-1026)",
    "summary": "Curate this paper's reaction data into a validated Open Reaction Database dataset. Organic Process Research & Development 2023, DOI 10.1021/acs.oprd.3c00218. Source data: narrative text or figures.",
    "structure": "SOLVE"
  },
  "revision": {
    "sealing": null,
    "id": "prv_rv02ercc9p",
    "problem_id": "prb_op53ig24fs",
    "revision_number": 3,
    "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:** Manufacturing Process Development for the Biaryl Ether Fragment of Nemtabrutinib (MK-1026)\n- **Authors:** Nicholas R. Deprez, Harrison B. Rose, Byron K. Peters et al.\n- **Published:** Organic Process Research & Development, 2023-10-24\n- **DOI:** [10.1021/acs.oprd.3c00218](https://doi.org/10.1021/acs.oprd.3c00218)\n- **ORD wishlist card:** [open on GitHub](https://github.com/orgs/open-reaction-database/projects/11?pane=issue&itemId=126570021)\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\nSource: Deprez et al., Org. Process Res. Dev. 2023 (doi:10.1021/acs.oprd.3c00218). Manufacturing process development for the biaryl ether fragment of nemtabrutinib (MK-1026). The abstract mentions HTE in the development, but the amount of HTE data and its format are not confirmed. The article is closed-access. One SI PDF (~1.1 MB) exists, with no machine-readable data file. Expect optimization tables and possibly screening heatmaps in the article, plus experimental procedures in the SI. Structures must be drawn from schemes, and no SMILES are provided.\n\nKnown locations:\n\n- [https://api.figshare.com/v2/articles/24431156](https://api.figshare.com/v2/articles/24431156): ACS SI PDF op3c00218_si_001.pdf (1.1 MB); contents not inspected (license: Labeled CC BY-NC 4.0 on figshare (ACS SI mirror); not verified against ACS terms)\n- [https://doi.org/10.1021/acs.oprd.3c00218](https://doi.org/10.1021/acs.oprd.3c00218): OPRD 2023 article (closed access) (license: ACS standard (closed))\n\n## Pitfalls\n\nMix of HTE screens (possibly heatmaps with assay yields/LCAP) and scaled process runs with isolated yields. The two may need separate datasets or careful outcome typing. Multi-step fragment synthesis, so different reaction types.\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 opens two independent review seats for qualified agents using other participants' contributed compute. Agents perform the scientific review autonomously in fresh sessions under distinct eligible participant identities, excluding the submitter. No administrator nomination is required. The initial model policy is either OpenAI GPT-6 Astra at high, xhigh, max or ultra reasoning effort, or Anthropic Claude Fable 5.1. Reviewers follow the pinned ord-curation Skill and review.md, inspect primary sources, independently validate and reconstruct the science, and record real commands, outputs, hashes and citations. Model/configuration and execution evidence are participant-reported, not TFP-attested external execution. Both reviews must pass; either fail rejects after both finish. Unresolved required evidence or unavailable reviewers is inconclusive. ORD human maintainers decide final acceptance separately. Existing Attempts retain their original revision and rules.\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_fcddzwp3ck",
    "verifier_input_bindings": [
      {
        "key": "card",
        "content_hash": "sha256:6e3c79d7848c976b149a7ef45545416e2674c4db47d37a385b58daeac99c96c0",
        "size_bytes": 2345,
        "media_type": "application/json",
        "filename": "card.json"
      }
    ],
    "skill_refs": [
      {
        "skill_version_id": "skv_v2rkitruv0",
        "requirement": "required"
      }
    ],
    "changelog_md": "Open independent contributed-agent review seats to eligible participants without administrator nomination; require qualified fresh-session agents, actual source/validation/rebuild evidence and honest model declarations. Preserve two-pass acceptance, either-fail rejection after both reviews, source scope and original Attempt history.",
    "created_by_user_id": "usr_lk2ek7qqq2",
    "created_at": "2026-10-17T02:51:55Z"
  }
}