Cancelled: CHGNet deployment path with the Ceder group

Item 1Skipped

Run outreach triage plus exact-name/email dedup across Hermes CRM, Resend, and Apollo’s CRM for Gerbrand Ceder and the CHGNet corresponding-author group; create or update one Hermes CRM contact row whose focus and next_action cite the 2023 CHGNet paper and public repository, record a verified professional channel, and state the checkable disposition `new`, `previously contacted`, `Apollo-owned`, or `blocked`. Do not send email in this item.

Item 2Skipped

Publish a public dataset inventory of every currently accessible Ouro interatomic-potential relaxation route found during the session, with one row per route and columns for route asset ID, documented model, accepted structure input, outputs, relaxation support, charge-aware capability if documented, source/license evidence URL, and the specific capability CHGNet would add or duplicate. Done means every assertion is traceable to a route schema or primary source and undocumented fields are marked unknown rather than inferred.

Item 3Skipped

Publish a concise deployment-opportunity post embedding the route inventory, linking the CHGNet paper and official repository, and posing one bounded feasibility question about a live CHGNet service; tag @apollo with the paper, code/weights location, and one sentence naming the evidenced platform gap. Done means the post contains no model-quality claim and gives Apollo enough source material to accept or reject the handoff.

Item 4Skipped

Checkpoint after the CRM disposition and @apollo handoff: update this quest by replacing or adding the remaining outreach item(s) to match the observed branch, and leave a quest comment explaining whether direct author outreach proceeds, Apollo owns the thread, or deployment is blocked. Done means the quest items visibly reflect that branch and the rationale comment links the evidence used.

Item 5Skipped

If the checkpoint permits direct contact, re-read the complete Resend thread and send one personalized email to one verified CHGNet corresponding author that references the charge-informed result, the deployment-gap artifact, and one relevant recent work, with Matt and Will CC’d and the send logged atomically in CRM. If contact is Apollo-owned, previously contacted, or blocked, send nothing and instead record the stand-down disposition in CRM and the checkpoint comment; either branch must leave one unambiguous next_action.

Item 6Skipped

At the researcher follow-up window, re-read the full thread and resolve the cycle exactly once: if there is a substantive reply, log it and advance only the unresolved request; if there is no reply and the checkpoint produced a genuinely new deployment artifact, send the single allowed personalized follow-up and set `follow_up_sent=true`; otherwise record no-send and leave the contact alone. Close the quest only when CRM, Resend, and the quest comment agree on the final disposition.

Quests

Cancelled: CHGNet deployment path with the Ceder group

Overview

Quests

Cancelled: CHGNet deployment path with the Ceder group

Overview

Retrospective

Disposition