The Mn–Ge–N handoff resolved all six planned items and left a reusable experiment matrix, deposit template, and protocol, but its author channel bounced and nobody replied, contributed data, or reused the package. The newer magnet leaderboard and cold wave have also produced no external entry or author reply yet, so this cycle replaces another candidate-scoring invitation with a code-level integration question an open-source model author can directly correct.
This cycle is confined to Ivan S. Novikov’s group, its spin-MLIP paper, and the public implementation at gitlab.com/ivannovikov/spin-mlip. It builds on the 24-material FM/AFM benchmark, which showed that Ouro’s structure-only moment models cannot infer magnetic ordering from a bare CIF. The question here is narrower: can one upstream spin-MLIP example and one symmetry claim be reproduced faithfully, then expressed as a safe route contract for
The stopping point is one source-audited control, one claim-matched metamorphic test, one deployability contract or precise blocker, one message to Novikov as the group’s sole contact, and at most one later follow-up. No other coauthor or adjacent spin-model group belongs in this quest.
Recent quests have centered on paper-derived CIFs, DFT or TB2J comparisons, analysis posts, experimental matrices, and reproducibility bundles followed by email. This plan creates no candidate structure, runs no screening chain, and publishes no new standalone benchmark. Its new work type is a metamorphic software-symmetry test paired with an executable input/output acceptance contract; the public evidence is folded into the existing magnetic-ordering benchmark, and the outreach asks the author to correct that contract or point to the right public checkpoint.
The materials-research pause remains in force. Computation is limited to the repository’s own example and one transformation explicitly guaranteed by the paper or documentation, with the unchanged example serving as the known-answer control. The pending account-quota decision is not pre-empted: no item depends on creating a file, post, or dataset, and comments on existing assets carry the receipts.
If the repository lacks a runnable public model, usable license, or complete example, the checkpoint must pivot to an exact missing-artifact request and block any deployment claim. Before email, re-read Resend, the Hermes CRM, and Apollo’s CRM, honor the current daily caps and controller handoff guard, CC Matt and Will, and use the canonical deterministic idempotency key. Silence after one substantive follow-up ends the cycle.
Open