{"resourceId":"scientific-computing-workshop-stewardship-2026","versions":[{"version":"external-f86f9b6fdb50b871b8f1fd4bebd66ce5c6afdfabc00acf975c1373a27043541f","resource":{"id":"scientific-computing-workshop-stewardship-2026","title":"Scientific-computing workshop makes validation and stewardship part of AI capacity","organization":"Argonne National Laboratory and cross-institutional workshop authors","sector":"Research computing and research software governance","geography":"United States-led workshop with international participation","publishedAt":"Report dated August 24, 2026; arXiv v2 August 28, 2026","publicationDate":"2026-08-28","eventDate":"2026-04-14","sourceName":"arXiv, report ANL-26/32","sourceLabel":"Workshop guidance; qualitative synthesis, not formal consensus","sourceUrl":"https://arxiv.org/html/2608.26519v2","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["knowledge-work","developers-agents","infrastructure","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The workshop recommends treating scientific validation, shared software and human judgment as enduring research infrastructure.","sledRelevance":"Relevant to university research services; national-laboratory scale and international participation require local adaptation.","evidence":"Organizers synthesized discussion notes and report-outs through participant review. The report explicitly is neither systematic review nor formal consensus. It contains proposed priorities, not a measured institutional intervention or benefit baseline.","architectureImplications":"Interpretation: make model, data and software versions inspectable across mixed simulation and agent workflows.","governanceImplications":"Interpretation: give each pilot an explicit scientific approval point and a responsible service owner.","securityPrivacyImplications":"Interpretation: pair research audit trails with access controls so reproducibility records do not expose sensitive inputs.","caveats":"Qualitative guidance, not a binding standard or effectiveness study. Event date records the start of the April 14–16 workshop. August 28 is the inspected revision date, not the workshop date.","streamIds":["research"],"roles":{"sales":"Interpretation: Engage research leadership, computing managers and software-maintenance teams about pilots that lack a durable home. Ask who maintains dependencies after a grant ends, who can approve scientific use, and whether researchers can reconstruct earlier results. A bounded service-readiness review could identify unfunded responsibilities and define a viable handoff. The value hypothesis is fewer abandoned or unauditable workflows; measure it locally. The workshop does not prove a return on investment or prescribe a particular product. Distinguish an assessment based on community guidance from compliance with a mandatory standard.","engineering":"Interpretation: Map one existing research workflow from data intake through simulation, assistant output and investigator approval. Capture dependencies and provenance at each boundary, and identify where cloud, campus or hybrid execution affects replayability. Require scoped agent permissions and make logs available only to authorized reviewers. A proof of value should recreate a prior result on a clean environment and test recovery when a dependency disappears. Record numerical tolerances and unresolved uncertainty rather than requiring identical output where that is scientifically inappropriate. This operational design is proposed interpretation, not an architecture validated by the workshop.","delivery":"Interpretation: Appoint a research-service owner and scientific steward before expanding the pilot. Dependencies include maintenance funding, disciplinary review capacity and a supported artifact repository. Build training around explaining assumptions and investigating unexpected output, with accessible documentation and office hours for adoption. Review ownership at pilot launch, handoff and subsequent dependency changes. Proposed acceptance criteria are a funded support plan, a successful clean-environment replay within agreed tolerances, and documented approval authority for every workflow stage. Track unresolved incidents and time spent maintaining the service. Risks include staff turnover, stale dependencies and mistaking training attendance for demonstrated judgment."},"retrievedAt":"2026-09-12T03:01:42Z","enrichedAt":"2026-09-12T03:03:15Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: fund accessible researcher support and validation skills alongside infrastructure access.","procurementImplications":"Interpretation: include artifact export, maintainability and staff support in service acceptance terms.","operatingModelImplications":"Interpretation: sustain a named owner and maintenance budget beyond the pilot's initial funding.","updateExplanation":"No matching arXiv identifier in all-stream archive search. Newly covered August guidance adds maintenance and evaluation context to current research-capacity announcements; no source update since the previous run is claimed.","sourceVerification":{"openedUrl":"https://arxiv.org/html/2608.26519v2","referenceExcerpt":"a qualitative synthesis of workshop discussions rather than a formal consensus process or systematic literature review","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}