Greetings, all, We have shared information for model team closeout on Slack #modcon-mt<https://urldefense.us/v3/__https://modelsconsortium.slack.com/archives/C09HZ... > and with model team leadership. We have heard that knowledge of this guidance is uneven across model teams, so we are sharing this with all. Please see below. Many thanks, Court ________________________________ From: Corley, Courtney D <[email protected]> Sent: Tuesday, May 19, 2026 10:37 AM To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: Seedling Model Team June Wrap-Up: Final Artifacts, Impacts, and Transition Materials Dear Seedling Model Team Leads, As the Seedling Model Team period concludes at the end of June, we want to extend a sincere thank you and recognize the incredible work you have accomplished in such a short time period and under enormous pressure. As the next step, we want to capture the full value of your work, preserve assets for the Genesis Mission ecosystem, and position each team for the strongest possible next step. Your work has been exceptionally valuable. The Seedling Model Teams helped stress-test what the RFA teams will need, identify real capability requirements, demonstrate what is possible for AI-enabled science, and shape the needs for the next phase of the Genesis Mission. We will continue to champion your work and highlight its impact as we share progress on ModCon, AmSC, and the Genesis Mission in the months and years ahead. We are also providing a way to preserve your project artifacts so that the capabilities you have developed remain part of the project record and can support RFA submissions, future proposals, and follow-on scientific engagements. To ensure your digital products (models, agents, and datasets) are properly cited and handled based on their public or non-public status, and to support closeout and transition, please provide the materials below by Tuesday, June 26, 2026. This information is also on Box here: https://urldefense.us/v3/__https://anl.box.com/s/8cgw5v0wt3bqurmnthny6ge31yq... 1. Public Impact PPT Prepare a short presentation that captures the hard-hitting impacts from your Seedling Model Team. We are looking for clear, specific, externally understandable statements of scientific or technical value. These materials may be used publicly unless you note restrictions in the PPTX. Please include: * quantitative results; * productivity improvements or workflow acceleration; * model performance; * core capabilities integrated; and * a bibliography of public and non-public technical products and artifacts, using the data, code, model, and agent citation guidance below. Example: "Researchers on [MT_NAME] developed a deep reinforcement learning model that can identify potential plasma collapses 300 milliseconds in advance. [Reference if available]." Box upload folder: https://urldefense.us/v3/__https://anl.box.com/s/cspemxrbbtxk8xv7q80h3t74im0... 2. Public Demo Video Provide a link to a demo video that has been publicly released through your lead lab's information release procedure. Include a one- to two-sentence description of the demo, the release approval status, and any required attribution language. The March 2026 demo videos and guidelines are acceptable; please make final edits and updates if your budget allows. Box upload folder: https://urldefense.us/v3/__https://anl.box.com/s/m7v1yxwry73gd5ibxgiunnc9ult... 3. Lessons Learned Provide input on scientific workflow, data readiness, platform integration, compute access, model training, evaluation, safety/security, documentation, team coordination, and partnership processes. Also include structured feedback on your team's experience with AmSC services, including Federated Identity; Data APIs (Globus Compute/Flows, IRI API); AI/Inference services; and compute access (Frontier, NERSC, Aurora). Please flag: * what worked; * what blocked you; * what was missing; and * what you had to build yourself that should have been a platform service. Please be candid. The goal is to improve support for the next round of teams. Submit here: Lessons Learned Form<https://urldefense.us/v3/__https://docs.google.com/forms/d/e/1FAIpQLScMrZJRR... > 4. Final One-Page Closeout Report Complete the one-page closeout report template at the end of this document. Include the project title, team members, lead lab, partner labs, main outcomes, links to artifacts, and follow-on plans. Complete this only after you have all of your links, and materials identified ready to enter into the form. You can preview the form questions at the end of this document as well. Submit here: Final closeout report and link lists<https://urldefense.us/v3/__https://forms.office.com/g/VcMfKCfGyq__;!!G_uCfsc... > form. 5. Public Project Technical Products and Artifacts Work with your assigned core team staff to wrap up efforts related to licenses, data repositories, DOIs, citations, and other closeout needs. Core team liaison roster: https://urldefense.us/v3/__https://anl.box.com/s/8clg729703dmmkkxusps9ylt4w2... For public products, please provide the following: * Code and documentation repositories. Push all code, documentation, scripts, workflows, prompts, containers, notebooks, evaluation harnesses, and deployment instructions to an approved repository. Use the AI-ModCon GitHub organization<https://urldefense.us/v3/__https://github.com/ai-modcon__;!!G_uCfscf7eWS!dXX... > or provide links to existing public repositories. Include licensing information, installation instructions, reproducibility notes, and a future point of contact. * Model, agent, data, and datasheet documentation. Complete the relevant model cards, agent cards, data cards, and datasheets for your project. List each card or sheet as it would be cited in a publication, with links and/or persistent identifiers to its location. * Data deposit and registration. Work with the DBS team and your assigned DBS data detective to develop a preservation and sharing plan for public and pre-publication data. Where possible, publish data to an existing repository that registers metadata with the AmSC catalog. Metadata for pre-publication data should be shared through a resource with appropriate access controls for future use. 6. Non-Public Project Technical Products and Artifacts For non-public products, follow the same general steps as above, but first set up a private collaborative workspace on EDX. * Register<https://urldefense.us/v3/__https://edx.netl.doe.gov/user/register__;!!G_uCfs... > or log in<https://urldefense.us/v3/__https://edx.netl.doe.gov/user/login__;!!G_uCfscf7... > to EDX. * Create a collaborative workspace<https://urldefense.us/v3/__https://edx.netl.doe.gov/workspace/new__;!!G_uCfs... >. * For questions or assistance, contact edxsupport<mailto:[email protected]>. * EDX Collaborative Workspaces<https://urldefense.us/v3/__https://edx.netl.doe.gov/sites/reference-shelf/he... > are non-public repositories that can handle resources up to CUI. Products can be moved to the public side of EDX and the AmSC catalog later, if desired. EDX is an IP of the Genesis Mission AmSC. * Once the workspace is available, submit data, model, and agent cards, as well as links to non-public Git repositories or data in other repositories. Each submission can include metadata, license information, and a data/software citation. If you need licensing guidance, contact your modeling team's IPPF POC. * You may include citations from EDX collaborative workspaces in the PPT bibliography, including any license information and non-public restrictions. * For code that is not publicly available, you may also use Genesis Mission OSTI GitLab (DOE CODE)<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis__;!!G_uCfscf7eWS!... >, as appropriate. Key Resources for Public and Non-Public Technical Artifacts * Core team liaison roster: https://urldefense.us/v3/__https://anl.box.com/s/8clg729703dmmkkxusps9ylt4w2... * DBS data detective assignment: https://urldefense.us/v3/__https://anl.box.com/s/edf5jcsyapwb2fxq5cce64xghyo... * DOE program-affiliated data repositories: consult your DBS liaison for the current list and recommended repository for your data type. Model and Agent Cards * Model card template: model-card.md<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis/modcon-bpsw/-/blo... > * Agent card template: agent_card.md<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis/modcon-bpsw/-/blo... > * Completed model and agent card examples: examples folder<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis/modcon-bpsw/-/tre... > * Deposit completed model and agent cards here: https://urldefense.us/v3/__https://anl.box.com/s/6cqu05jn1z6auf0s0v8ryug9pis... * If your team needs assistance obtaining a software citation or OSTI-enabled persistent identifier (DOI) for your Git repository, work with your BPSW liaison. You may also submit your model or agent cards and Git link to EDX for publication. If assistance is required, contact edxsupport<mailto:[email protected]>. If this path is used, a record will be generated in the Genesis Mission AmSC-EDX IP catalog. Data Cards and Datasheets * Data card standard: data-cards template<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis/data-cards/-/tree... > * Completed data card examples: data-cards examples<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis/data-cards/-/tree... > * Legacy data card examples: Box examples folder<https://urldefense.us/v3/__https://anl.box.com/s/ewuuv579kjed3d37q51m7hl2p7j... > * Deposit completed data cards and sheets in Box: https://urldefense.us/v3/__https://anl.box.com/s/6cqu05jn1z6auf0s0v8ryug9pis... * Also submit completed data cards to GitLab: Genesis data-cards repository<https://urldefense.us/v3/__https://gitlab.osti.gov/genesis/data-cards__;!!G_... > (refer to the README for submission details). * Your DBS liaison can answer questions about persistent identifiers (e.g., DOIs) and technical artifact citation formats. If needed, public products can request an OSTI-coordinated persistent identifier. * DBS liaisons can also help obtain product citations for data and software using the Energy Data eXchange (EDX). For questions, view the EDX metadata and citation guidance<https://urldefense.us/v3/__https://edx.netl.doe.gov/sites/reference-shelf/ed... > or contact edxsupport<mailto:[email protected]>. * For assistance with persistent identifiers or citation formats, work with your DBS data detective<https://urldefense.us/v3/__https://anl.box.com/s/edf5jcsyapwb2fxq5cce64xghyo... > or read the EDX citation guidance<https://urldefense.us/v3/__https://edx.netl.doe.gov/sites/reference-shelf/ed... >. Thank you again for the enormous effort, creativity, and pace you brought to this work. The Seedling Model Teams have been essential in proving out the early Genesis Mission capabilities, and your results will help define what comes next. We are grateful for the work you have done and excited to see it continue through RFAs, future proposals, and the broader scientific impact it enables. With gratitude, The ModCon Leadership Team