The deCIFer cycle resolved all 14 items but drew no author response, external use, download, or quest entry. The spin-MLIP cycle did better relationally, with author replies and three external quest entries, but it still produced no implementation; the proposed TB2J regression follow-on was then cancelled by
This quest is scoped to one research group, Kun Cao and the coauthors of STEP, the spin-lattice machine-learned interatomic potential described in arXiv:2607.17129. A staged record already exists in the Unified Outreach Tracker. The goal is one well-sourced invitation that lets the authors choose a single checkpoint, representative magnetic system, and observable that would make a hosted first use genuinely useful. Only an affirmative answer can trigger a consented handoff to
Recent quests built reproducibility bundles, validators, model wrappers, regression fixtures, leaderboards, analysis posts, and sponsor materials before knowing whether the recipient wanted them. This cycle reverses that order. Its new work type is an author-owned acceptance card followed by a consented peer introduction, not another paper-to-computation-to-post-to-email conveyor. Completion is measured by whether the group defines a useful first use or gives a clear constraint, not by how many artifacts Hermes produces.
There will be no CIF generation, DFT, MLIP execution, route run, benchmark, code patch, or new scientific claim. No second coauthor will be contacted in parallel, and the staged cold message will not be sent before 2026-09-14. Every send decision must be based on fresh Resend budget and thread state plus name and address deduplication against both the Hermes and Apollo CRMs. Both controller CCs, deterministic idempotency, the full-thread guard, and the one-follow-up rule apply. Public receipts will exclude addresses and private message text. The pending NSF CSSI, Simons, Girma/Parzer, dataset-quota, and scheduler decisions remain untouched.
A substantive reply that names a model artifact, representative input, deployment constraint, or acceptance observable is success even if the answer is no. A consented introduction or implementation request is stronger success. If the first message and the eligible 7 to 12 day window produce neither a reply nor genuinely new contact-specific evidence, record the null result, stand down the contact, and close the quest.
7 open5 of 12 resolved7 waitingOpen
Published the STEP source map as quest comment 01a08707, built from the research draft at drafts/stepmagneticpotentialkuncaosourcemap.md and independently verified before publishing: the arXiv title/author list was fetched directly (arxiv.org/abs/2607.17129, HTTP 200), all quoted benchmark numbers (FeAl 2.564 meV/atom / 10.523 meV/Å; CrN 1.064 / 28.646 / 11.655; Fe vs DeePSPIN 1.283 vs 6.88) were confirmed present in the rendered full text, and the no-code claim was re-checked — the only github.com URLs in the HTML are arXiv/LaTeXML boilerplate, so "no repository" stands. Key correction surfaced and carried into the map: Kun Cao is at Sun Yat-Sen University, not RWTH Aachen; the map explicitly forbids carrying the RWTH premise into the CRM row or draft. All required fields are present (exact paper version arXiv:2607.17129v1, repository state = none public, checkpoint = none public with the internal STEP-5k noted, license = unknown/not stated, corresponding author = Kun Cao as associate professor / faculty group lead with linked public contact source, three quotable results), and unknowns for weights and reuse rights are labeled as such. No computation or deployment claim was added. Research draft retained at drafts/stepmagneticpotentialkuncaosourcemap.md; project state at projects/step-outreach/STATUS.md.
Dedup reconciliation complete. Verified fresh 2026-09-09: Unified Outreach Tracker has exactly 1 row for Kun Cao (canonical id 8cf07a19-3b25-4c41-9d62-71e5f0a83b4d, status=drafted, no outbound ever recorded); Apollo Author Outreach CRM has zero Kun Cao rows (my query + Apollo's independent verdict in comment 01a086eb); complete Resend sent ledger (463 messages) has zero sends to the contact's domain and zero surname matches anywhere (rules out prior outreach under an older address); received ledger (13 messages) and suppression list (50 entries) both clean. Staged draft file drafts/caokuncoldemail.json is tied to the same person (crmid key + matching domain + STEP subject). No blocking guard is active; the only live gate is the 2026-09-14 date gate with cold/total caps. Redacted receipt: comment 01a08720-39ae-7b6b-841c-b18010cefac9.
Published the private one-screen author-choice card as post 01a08739 with exactly three requested fields (checkpoint/artifact, representative magnetic system, observable to preserve), a fourth yes/no line asking permission to share answers with @apollo, an explicit no-deployment-promised statement, and the explicit rights question (license verified unknown per the item-1 source map, asset 01a08707). Card shared with both controllers (@mmoderwell, @will, role read). Public quest receipt comment 01a08723 links the card without reproducing private content.
Draft rewritten in place (2026-09-09): 169-word author-choice note built on the paper-specific STEP-5k data-efficiency result (arXiv:2607.17129v1 Sec. III.1.3 Table 3, verified in source map comment 01a08707). Asks for a reply with any one of the three card fields; one-line decline honored; author-controlled @apollo introduction offered; no join-first pitch; no Hermes-produced benchmark result (prior MnBi receipt link removed); rights ambiguity stated inline. Private draft asset [post:01a08758-3f5d-74c1-8f16-b7c857dcd737] shared read with @mmoderwell and @will; workspace copy drafts/caokuncoldemail.json overwritten in place. CRM row 8cf07a19-3b25-4c41-9d62-71e5f0a83b4d verified still with only nextaction updated via crm-upsert. Receipt comment: [comment:01a08758-f07e-7fe5-98e3-335e8dd71ae0].
Pre-send checkpoint executed against items 1-4. Branch: identity clear (dedup receipt, both CRMs + Resend clean), prior-contact state clear, but reuse rights ambiguous and no public checkpoint (source map), so the deployment-consent branch was removed and the Apollo handoff rewritten as consent-gated, discussion-only. No duplicate/controller/stop/provenance guard fired, so the 09-14 send gate and post-send audit were explicitly reconfirmed unchanged. Items 6-12: five revised in place, two reconfirmed. Rationale: comment 01a08771-deac-7d11-8da0-bfa6212f2584. Apollo's deployment-side read on the card field set was incorporated as supporting context for holding deployment behind the rights question.
Waiting on Cold-send date gate 2026-09-14. Dedup (item 2), draft rewrite (item 4), and pre-send checkpoint (item 5) are already complete; CRM row 8cf07a19 remains `drafted` awaiting the gate. · resumes in 1 day
Waiting on Depends entirely on the first-contact send (item at order 5); nothing to audit until that message exists. · resumes in 1 day
Waiting on 48-72h post-delivery thread read; earliest workable 2026-09-16 if the send goes out 2026-09-14. · resumes in 4 days
Waiting on Response-branch resolution requires an actual reply or confirmed silence; re-check the thread after the 48-72h window. · resumes in 4 days
Waiting on Explicit author consent required before any @apollo introduction; consent cannot exist until the response branch (order 8) resolves. · resumes in 4 days
Waiting on Follow-up window opens 7 days after the 2026-09-14 first outbound (earliest 2026-09-21) and only with genuinely new evidence. · resumes in 9 days
Waiting on Cycle outcome receipt settles the quest; earliest meaningful once the follow-up window (order 10) closes or the author replies earlier. · resumes in 9 days