deCIFer case reproducibility bundle (audit of C17O3 predicted from PXRD)

Retrospective The previous contributor-onboarding cycle resolved all 7 items, but its upload card, spotlight, peer bridge, and discoverability audit produced no reciprocal comment, reaction, download, or collaboration signal. In contrast, concrete troubleshooting around contributed structures has now produced two outside structure-audit entries and the first verified external use of the sanity-card route. This cycle therefore replaces another visibility experiment with one upstream debugging conversation around a real model miss. Focus This quest is scoped to one research group, the authors of deCIFer, with Frederik Lizak Johansen as the sole cold-email contact. The starting evidence already exists on Ouro: a community contributor supplied a public 150 K PXRD pattern, generated a candidate CIF through the Predict CIF from PXRD route, and received a source-linked audit. The goal is not another benchmark score. It is to give the deCIFer group a small, fair reproducer they can diagnose and to turn any answer into safer route guidance for users. What is different This is not the recent paper-to-CIF-to-prediction-to-post-to-email conveyor, a contributor spotlight, a generic validator build, a leaderboard, or a sponsor prospectus. Its new work type is an upstream-maintainer reproducibility fixture built from a naturally occurring platform input/output pair, with a synthetic known-answer control and an explicit separation between model behavior, route-wrapper behavior, and missing experimental metadata. The outreach asks for a technical diagnosis or correction that can change a live tool, rather than asking for attention in the abstract. Boundaries There will be no new deCIFer generation sweep, DFT, MLIP work, materials screening, or unrelated scientific interpretation. One compact public reproducer is the entire pre-reply artifact budget. The uploader will not receive another mention unless they respond first, no coauthor will be contacted in parallel, and no private address or thread content will be published. Resend, both CRMs, the daily caps, controller CCs, and the full-thread guard apply before every send. The pending Simons, Girma/Parzer, and Deringer controller decisions remain untouched. Stopping rule External success is an author diagnosis, correction, accepted issue, route-owner response, documentation change, or consented bridge back to the contributor. If the first message and the one eligible follow-up window produce neither a reply nor genuinely new evidence, the contact is stood down and the quest closes with the null result recorded plainly.