# IOWarp

https://akougkas.io/work/iowarp/

Author: Anthony Kougkas

Updated: 2026-11-11

## The question

Scientific computing spent decades getting better at moving bytes. The newer problem is deciding which bytes, which metadata, which tools, which history, and which constraints matter right now, especially once software agents take part in the workflow.

IOWarp is the program built around that problem: a context layer for scientific work, with a runtime and tools that move data across storage tiers, preserve useful state, connect capabilities, and keep the boundary between automation and human approval explicit.

## Where it came from

I wrote the IOWarp proposal in 2023, at the end of [Hermes](https://akougkas.io/work/hermes/). Its core was a self-describing unit called Content, a transfer engine that was Hermes grown up, an assimilation engine for reshaping data across formats, and a thrust I named WarpGPT: a natural-language interface that would answer questions about scientific data by querying a content catalog and calling operators as tools. That was before the Model Context Protocol existed. The proposal marks the transition from moving and organizing scientific data to managing the full context around scientific computation.

[NSF](https://www.nsf.gov/) funded it in August 2024 as a collaborative Frameworks award among [Illinois Tech](https://www.iit.edu/), [The HDF Group](https://www.hdfgroup.org/), and the [University of Utah](https://www.utah.edu/). The work runs across the three institutions with [Gerd Heber](https://www.hdfgroup.org/team/gerd-heber/), [Jacob Hochhalter](https://prognosis.mech.utah.edu/), [Vivek Srikumar](https://svivek.com/), [Xian-He Sun](https://www.iit.edu/directory/people/xian-he-sun), and their teams.

## IOWarp and CLIO

IOWarp is the research program, platform, and institutional collaboration. [CLIO](https://akougkas.io/work/clio/), Context Layer for Input/Output, is the architecture I created for it. CLIO defines the component boundaries and shared contracts through which the program becomes one software ecosystem.

## What shipped

IOWarp is research infrastructure under active development. The first integrated beta shipped in September 2025, and each component has released on its own cadence since. [CLIO Core](https://core.iowarp.ai/) is the runtime that keeps scientific data usable across GPU memory, DRAM, NVMe, and parallel file systems; [its transfer engine](https://core.iowarp.ai/technologies/context-transfer-engine.html) is Hermes grown up. [CLIO Kit](https://toolkit.iowarp.ai/docs/intro) gathers the scientific tools and Model Context Protocol servers that agents call. [CLIO Agent](https://clio.iowarp.ai/) is a workspace where a scientist and an agent work on data together, and [CLIO Relay](https://github.com/iowarp/clio-relay) carries that work to remote clusters. [CLIO Coder](https://akougkas.io/work/clio-coder/), at [coder.iowarp.ai](https://coder.iowarp.ai/), is the coding agent for the software science runs on.

The team has built CLIO Core on Ares at Illinois Tech, DeltaAI at NCSA, and Polaris and Aurora at [ALCF](https://www.alcf.anl.gov/), and at the INCITE 2026 GPU hackathon showed it scaling to 512 Aurora nodes.

[Shazzadul Islam](https://grc.iit.edu/center/team/shazzadul-islam/)’s [eScience 2025 poster](https://akougkas.io/publications/islam2025towardsaidriven/) measured what the tools are worth: EarthScope retrieval and visualization in about two minutes with an agent that had IOWarp context, where the comparison agent did not finish; LAMMPS trajectory analysis in about 2.5 minutes against roughly 12 by hand. [Rajni Pawar](https://grc.iit.edu/center/team/rajni-pawar/)’s [Acropolis](https://akougkas.io/publications/pawar2026acropolis/) and [Izzet Yildirim](https://grc.iit.edu/center/team/izzet-yildirim/)’s [AgentStage](https://akougkas.io/publications/yildirim2026agentstage/), both accepted at eScience 2026, are the next pieces of agent-facing storage.

In August 2026 GRC began two first-round DOE Genesis Mission projects that build on CLIO: [SPOTTER-AI](https://grc.iit.edu/research/projects/spotter-ai/) with [Argonne](https://www.anl.gov/), [Oak Ridge](https://www.ornl.gov/), and HPE, which [traces threats to scientific data through workflow provenance](https://iowarp.ai/applications/genesis-spotter/), and [PORTUS](https://grc.iit.edu/research/projects/portus/) with [Pacific Northwest](https://www.pnnl.gov/), which [guides coding agents that port and tune scientific workflows](https://iowarp.ai/applications/genesis-portus/).

## My part, and the team around it

I framed the context problem, wrote the proposal, shaped the partnerships, defined the architecture and component boundaries, built the team, and remain responsible for integration, milestones, coauthored research, releases, and reporting across the program. I also write code across the software. The implementation is collective. [Luke Logan](https://grc.iit.edu/center/team/luke-logan/) leads day-to-day Core engineering and built Chimaera, the coroutine-based distributed runtime underneath it; [Jaime Cernuda](https://grc.iit.edu/center/team/jaime-cernuda/) leads Agent and Relay; the students [Isa Muradli](https://grc.iit.edu/center/team/isa-muradli/) and Shazzadul build Kit; [Jie Ye](https://grc.iit.edu/center/team/jie-ye/), [Keith Bateman](https://grc.iit.edu/center/team/keith-bateman/), [Neeraj Rajesh](https://grc.iit.edu/center/team/neeraj-rajesh/), Rajni, and [Hua Xu](https://grc.iit.edu/center/team/hua-xu/) develop components and research directions, as [Meng Tang](https://grc.iit.edu/center/team/meng-tang/) did until August 2026; Gerd’s engineers at The HDF Group lead format integration; Jacob and Vivek bring the materials and machine-learning domains from Utah.

## What carried forward

The idea that a request should carry its intent comes from [LABIOS](https://akougkas.io/work/labios/). The task pipeline comes from [DTIO](https://akougkas.io/work/dtio/), whose mechanisms were reimplemented inside CLIO Core in 2025. Time-ordered provenance comes from [ChronoLog](https://akougkas.io/work/chronolog/). The measurement discipline for scientific AI comes through [DeepIO](https://akougkas.io/work/deepio/). IOWarp is where those lineages become a context system.

## What I am asking next

- What is the smallest context contract that stays useful across scientific domains?
- Which provenance must be captured at runtime, and which can be reconstructed later?
- How do we make an agent’s authority legible before it acts, not only after something goes wrong?
- Can the same infrastructure feel natural to a scientist, a systems developer, and an automated tool?
