Backend
PegasusAI Studio: Legible Cyberinfrastructure and Accountable AI Agents for Scientific Workflows
arXiv cs.DC0 views
arXiv:2611.13309v1 Announce Type: new Abstract: AI coding agents can now construct scientific workflows, but operating them on shared cyberinfrastructure (CI) raises problems that code generation does not solve. Agents need current knowledge of the workflow system and its execution sites and access to the runtime state of distributed executions, while facilities need to attribute every agent action to a user and bound it by that user's privileges. We present PegasusAI Studio, an AI-assisted science gateway built on the Pegasus and HTCondor stack. Studio makes CI legible to agents by projecting one facility-curated knowledge base into the native configuration of several coding agents, by introspecting workflow interfaces and execution sites, and by grounding diagnosis in workflow and scheduler telemetry. Agent actions operate within a trust envelope that combines federated authentication, per-user execution environments and scheduler credentials, provider-neutral model access, observability, and approval controls for state-changing actions. The same application runs as a JupyterHub-based gateway on a research cloud and as an Open OnDemand application on HPC systems. We evaluate Studio through case studies of legacy CASA weather workflow modernization, a gravitational-wave reanalysis, an EEG analysis built with an open-weight model, and an Event Horizon Telescope (EHT) M87 image reconstruction that recovered from two failed runs to a zero-failure execution. The evaluation establishes that these mechanisms operate as designed.
Source:https://arxiv.org/abs/2611.13309PreviousDecode Token Parallelism: Memory-Efficient Distributed Attention Parallelism for Scalable LLM DecodingNextPlumbline: When the Loss Lies, Validating LLM Training Correctly
Related posts

How Does AWS Protect Sensitive Data? Understanding AWS KMS, Encryption & Key Management
0dev.to AWS
How Conditional Email Routing Rules Work
0dev.to Security
SOC 2 Readiness for SaaS Companies: A Developer's Guide to Security Controls and Audit Preparation
0dev.to Security
CRA Annex I for mobile apps: a practical checklist mapped to OWASP MASVS
0dev.to Security

Your SOC 2 report doesn't answer a single AI question
0dev.to Security
The Second App Problem: Every Hosted Health MCP Is Also an App You Have to Keep Installed
0dev.to Security