Thoughts

July Newsletter

July 2, 2026

We skipped June; we've been busy. Here's everything since May.

In this issue:

  1. What We Led — MIRA in Ireland, core-satellite in New York
  2. What We Built — A Resilient Data Future, GREP, Lettuce Compute, SciOS Compute, SciOS Graph, and the MCP ecosystem into PRSM
  3. What We Wrote — The Core-Satellite Model
  4. Where We're Going — DWeb Camp July 07–13, a DOE open source keynote August 4
  5. What We've Seen
  6. IOSP 2026 — Leiden, October 12–15
What We Led

MIRA 2026 Workshop

MIRA is a shared schema for research artifacts. Questions, claims, evidence, sources, and the relationships between them get one common structure that any platform can inherit, rather than each tool maintaining its own. In June we ran a 23-person MIRA workshop with Matt Akamatsu and Discourse Graphs in Ireland. The output (including the landing page) is being uploaded to GitHub as each item is buttoned up. The schema itself is there, alongside an extractor that turns papers into MIRA graphs, an extension that adds MIRA directives to MyST Markdown, and prototypes for exchanging results and requests between labs and for tracing the impact of scientific investment.

The schema is already in use twice more in this issue. GREP is testing MIRA object extraction from any PDF, and SciOS Graph runs collaborative workshops on it; both are under What We Built.

The continuing work will be presented at IOSP 2026. Expect a trickle of updates over the summer. Get involved by joining the Modular Research lab.

Sustainable Open Source Funding Infrastructure: A Core & Satellite Model for OSS Funding in the Age of AI

We also ran a 23-person workshop in New York City around the core-satellite model, our commons framework for open source and open science (more under What We Wrote). Yes, also exactly 23 people; we didn't plan that. The group is producing at least one pilot core by IOSP 2026. Get involved by joining the Funding Open lab.


What We Built

A Resilient Data Future — graph.scios.tech

Our Resilient Data Futures narrative argues that research data loss is architectural, and that the fix is what it calls Tier 3 infrastructure, protocol-level distribution where redundancy arises as a byproduct of use instead of depending on any single organization. graph.scios.tech is a working implementation. Scientific records live on IPFS under content identifiers (CIDs), signed by their authors' decentralized identifiers (DIDs), and every link carries both a location and a content hash, so references don't rot and attribution can't be stripped. The whole stack runs on four small servers for $24 a month, and is easily replicated and scaled. Reach out if you'd like to help scale it.

We're expanding it in a workshop at IOSP 2026. Get involved by joining the Resilient Data Futures lab.

GREP — The Great Research Extraction Project

GREP ports the existing literature into frontier infrastructure. In production today, it extracts software mentions from any domain PDF as objects and relationships, and classifies how each piece of software figured in the work (used, created, deposited, or merely mentioned). A voting ensemble of five DeBERTa-based models does the extraction at 85% F1 on our benchmark, and 92% on span identification across a fifteen-domain test set. None of the five is sacred; each slot in the ensemble takes a replacement the day something better exists. The whole thing needs about 32 GB of memory and 45 GB of disk, no GPU, which is what lets volunteer hardware do the work (see Lettuce Compute, below). Expect a less heavy (and slightly less accurate) version in the coming weeks.

We're actively testing extensions of GREP into open science monitoring and MIRA object extraction. The monitoring work currently detects data availability statements and then checks whether data an author claims is open actually resolves; across a corpus of roughly 5,700 papers, 44% carried a statement, 26% claimed the data was openly available, and 16% pointed at data we could confirm was public, matching the claims made in our Resilient Data Futures narrative. The MIRA work turns any PDF into MIRA objects, which you can try at mira-extraction.vercel.app.

Get involved by joining the Modular Research lab.

Lettuce Compute — distributed computing, entering beta

Lettuce Compute is a permissionless distributed computing infrastructure for science. Researchers run a head server and define computations; volunteers run a small client, attach to any head they choose, select a leaf, and crunch on work units. Results are validated through redundancy, and contribution credit is cryptographically signed. There is no approval step and no whitelist; a volunteer generates a key and attaches. The scheduler matches work to machines that can actually run it, whether the task ships as a native binary, a container, or WebAssembly.

Well over 6,000 exaflops of processing power sits idle in the world's existing hardware. Lettuce Compute is how we connect it to scientific work, and we consider it core infrastructure for a reimagined scientific compact. It has spent the last month in alpha with several critical testers (to whom we are eternally grateful); beta opens this month.

Get involved by joining any SciOS Lab.

SciOS Compute — compute.scios.tech

SciOS Compute is Lettuce Compute with the setup done for you. Describe your computation and we stand up the project in under an hour, with distribution, validation, and volunteer onboarding handled. GREP already runs on it. It launches in earnest during the Lettuce Compute beta.

Get involved by joining the Resilient Data Futures lab.

SciOS Graph — workshop.scios.tech

SciOS Graph is a collaborative tool for building shared understanding, running on MIRA and open for anyone to use. It comes in two modes. Mini-MIRA condenses the schema to four node types so a room of newcomers can start thinking in graphs immediately; Full MIRA carries the complete schema for researchers who want the whole medium. We built it for live workshops, where participants add questions, thoughts, and connections from their own devices while a shared projector view updates in real time.

Get involved by joining the Modular Research lab.

PRSM — the MCP ecosystem in one graph

PRSM now crawls the MCP registries and assembles them into a single deduplicated graph. Seven registries feed it (the Official registry, Smithery, Glama, PulseMCP, mcp.so, Nerq, and BioContextAI for biomedicine). As of this writing it holds over 58,000 servers, 74,000 tools, and 26,000 confidence-scored "wrap" edges, each one recording that a specific MCP server lets an AI use a specific dataset, service, or piece of software.

The wrap edges make reverse lookup possible. Pick a dataset and ask what an AI can plug into today. NASA's open APIs are wrapped by 1,186 servers; SQLite by 735, PostgreSQL by 559, arXiv by 198, PubMed's E-utilities by 126, Crossref by 49, OpenAlex by 48.

Run the same question across the NumFOCUS-sponsored projects and the answer gets thin. pandas has 9 servers, SymPy 9, Matplotlib 8, NumPy 6, scikit-learn 2, SciPy 1, and Astropy, xarray, PyMC, seaborn, and GeoPandas sit at zero. (These are confirmed wraps, where the server declares the package as a dependency and names it, so read them as floors; many wrapper repositories haven't been analyzed yet.) The zeros are widely used scientific tools that nobody has wrapped in an MCP server. If you're looking for a way to help research software, that is a very good place to start.

The graph reaches specialist registries too. It carries 62 biomedical servers from BioContextAI (UniProt, Ensembl, PubChem, Open Targets, single-cell tools) and about a dozen Bioconductor community servers pulled straight from GitHub. Know a registry we're missing? There's a suggest-a-source form on the site.

All of it runs on PRSM's existing data layer, the graph that already links publications, repositories, packages, dependencies (declared and hidden), and contributors. Explore it, no login required: prsm.network/demo/mcp.

Get involved by joining the VOWELS lab.


What We Wrote

The Core-Satellite Model

We published The Core-Satellite Model, a commons framework for open source and open science built on human judgment. A core is a group of people who scope themselves within a domain and wrap around its artifacts. They decide what is canonical, hold the knowledge agents cannot read, and direct the agents that do the work. Satellites are the experimental artifacts that orbit them, independent but discoverable. As AI takes over more of the execution of science, expert judgment becomes the scarce resource, and cores are how a commons organizes it.

The New York workshop above is the first group putting the model into practice.


Where We're Going

DWeb Camp. Ellie is organizing the Anti-Authoritarian Stack Tent, and Jon is hosting two sessions. Friday, July 10 at 9:30am, A Seat at the Table, on the Open Source Endowment, a live experiment in community-owned funding for open infrastructure. Saturday, July 11 from 9:30 to 11:00, Break This Stack, a working session that decomposes a real paper into a sovereign, composable scientific record on ATProto and IPFS, then invites the room to break it at five identified failure points.

The 2nd Open Source Software Summit, August 4, Albuquerque. The U.S. DOE Integrated Energy Systems Office is gathering the open source projects it sponsors for a day on contributor engagement, maintaining open source in the age of AI coding tools, and collaboration among projects. Jon is giving a keynote. Agenda and details.


What We've Seen

Ellie was in Vancouver this spring for AtmosphereConf, where a workshop explored AT Protocol, the protocol underneath Bluesky, as a home for scholarly work; the keynote described research as a continuous, federated, computable graph of knowledge, and the demos ran discourse graphs and contribution attribution over decentralized identity. The Continuous Science Foundation's working group on modular peer review has met monthly all spring, asking how review and credit can attach to data, methods, code, and figures independently. The Knowledge Graph Conference drew more than a thousand people to Cornell Tech in May, including a symposium track on evidence graphs derived from the literature. People are converging.

Germany's DFG opened a funding line to safeguard endangered data repositories, citing roughly 200 repository closures over the past 25 years, more than half since 2018. A study in Nature Genetics traced the single points of failure in centralized biomedical databases (cyberattacks, funding cuts, political disruption) and held up ELIXIR, the 25-node federation behind Europe's life science data, as the working alternative. EOSC, Europe's open science cloud, added 14 nodes in April and now federates 28.

ICLR, one of the big machine learning conferences, collected just over 76,000 peer reviews for its 2026 cycle, and the AI-text detection firm Pangram Labs flagged about a fifth of them as fully AI-generated. Kubernetes shipped contributor policy in June that requires AI use to be disclosed, bars AI as a co-author, and promises reviewers they are talking to humans. Jazzband, the collective that maintained 84 Python packages serving 150 million monthly downloads, shut down in March; its founder named AI-generated spam contributions among the causes. In every one of these stories, the scarce resource is a person with the judgment to evaluate the work.

The UN held Open Source Week in New York in June, 2,600 participants from more than 120 countries, and UNESCO launched its Open Science Platform there, built on CERN's open repository framework InvenioRDM. We were there, and the appetite for radical change is even stronger in person than it reads in the announcements. Renaissance Philanthropy opened a $20 million fund for open source in the life sciences. Germany's Sovereign Tech Agency began paying open source maintainers a stipend to represent their projects in standards bodies. Wiley booked $49 million in AI licensing revenue this fiscal year, and arXiv and Semantic Scholar both gained MCP servers. Publishers and protocol builders are working out machine access to the scientific record right now, one licensing contract at a time on one path, one open server at a time on the other.


IOSP 2026 — Leiden, October 12–15

IOSP 2026 runs October 12, 13, and 15 at the Poortgebouw, University of Leiden, with a field trip to the National Open Science Festival in Delft on the 14th. Most of what's in this issue lands in Leiden. MIRA and the core-satellite pilots present there, the resilient-data stack expands in an on-site workshop, and GREP, Lettuce, and PRSM will be on the floor along with many other open science tools developed from the ecosystem!

Register interest (subscribers get priority if we're oversubscribed again), submit to the showcase, or sponsor. IOSP is free to attend, and every sponsorship dollar goes to travel grants that get people there.


That's it for July. See you at DWeb.

— Jon & Ellie, SciOS

contact@scios.tech

A Case for Resilient Research Data Infrastructure

May 6, 2026

A blog summary of the SciOS Resilient Data Futures whitepaper. The full paper is at rdf.scios.tech/narratives, and the underlying discourse graph and contribution model are at github.com/jring-o/rdf.

The Architecture Problem in Research Data

73 to 93 percent of papers fail to deliver their underlying data on request. This lost data, endemic across all research institutions as a byproduct of architectural decisions baked into daily operations, represents a $1.1 billion liability for an average R-1 institution. The architectural solution that hedges this liability is simple to implement, has been proven over four decades, and provides the exact properties AI-ready data policies are asking for.

And as for the 20% of data that is retrievable? Don't worry. It's often one organizational decision — an acquisition, a defunding, a jurisdictional change — away from oblivion.

Training, data management plans, researcher discipline, better staffed libraries — these address real problems and produce real, but bounded improvements. None of them addresses the property that makes such volumes of loss possible in the first place: research data typically exists in a single copy, held by a single organization, funded by a single grant, maintained by a single person who is expected to leave in several years.

This flawed architecture operationalizes loss in ways familiar to any institution. A graduate student leaves and the operational knowledge of where the data lives leaves with them. A laptop is stolen. A grant ends and the server it funded ends with it. A repository shuts down (191 of them have since 2012, at a median operating age of twelve years). A platform changes its access terms (the Twitter API in 2023, GitHub blocking developers in Iran in 2019, GISAID's account suspensions, CNKI's foreign-access cutoff). A backup script runs sideways and erases 77 terabytes of supercomputer data in an afternoon.

These look like different problems, but they're not. They are manifestations of the same core problem eating away at our ability to maintain scientific and technological advancement: research data infrastructure emerged to serve a reality that no longer exists.

Four kinds of preservation, only one of which scales

There's a four-tier framework to research data storage.

Tier 0 is local storage — one copy on one system. Most research data lives here, and the default outcome is the 17-percent annual availability decay the literature has been documenting for over a decade.

Tier 1 is hosted storage with one provider — an institutional repository, a domain repository, a cloud bucket. This is the architecture most data management plans describe and most mandates produce. It absorbs local failure. It does not absorb provider failure, which arrives through hardware failure, bankruptcy, acquisition, defunding, jurisdictional change, or terms-of-service shift on a timeline the institution does not control.

Tier 2 is coordinated preservation across institutional agreements. INSDC mirrors GenBank across three continents; the Worldwide Protein Data Bank synchronizes four sites weekly; CLOCKSS preserves 63 million articles across 12 nodes. These are the most sophisticated preservation systems ever built, and they work until the coordination doesn't.

Tier 3 is protocol-level distribution. Redundancy is a byproduct of use rather than the output of an organization's continued commitment. The architecture is visible in the longest-running information systems on the internet — DNS for 43 years, email for 44, BitTorrent for 25, Git for 21. These systems have outlived the companies, the operating systems, and in some cases the institutional structures that designed them. None of them lives or dies with any single organization.

Most research data sits at Tier 0 or Tier 1. Tier 2 is reserved for data whose value justifies the financial and operational costs. Tier 3 is the only architecture in the field that produces scalable, accessible preservation, verification, and audit evidence as structural byproducts of operation.

Verification falls out of the architecture

The funder regime is shifting from "did you write a plan?" to "did you do it, and can you prove it?" The NIH's May 2026 standardized DMSP format, the Gates Foundation's transition to programmatic compliance checking, and the False Claims Act's implied-certification doctrine are converging on a single question: can the institution surface, on inspection, evidence that the data exists where the plan said it would, intact, with the access controls it claimed?

At Tiers 0 and 1, the institution cannot answer the question by inspection. Every property is an assertion the provider made and the institution cannot independently verify. At Tier 2, the consortium often runs verification on members' behalf, but it remains an assertion the consortium makes about its own protocols rather than one the institution can independently re-run — and MetaArchive's sunset audit showed those internal protocols can silently fail with no external party positioned to catch it. At Tier 3, all of those properties fall out of a single cryptographic query against the distributed network. Audit becomes inspection rather than forensic reconstruction.

The $1.1 billion liability is a carrying cost, not a realized loss — a four-term formula (sunk grant value, irreplaceable-dataset replacement, foregone reuse, and False Claims Act exposure on data the institution can't independently verify) applied to a representative R-1. The full math is in the paper. The probability of latent exposure converting to realized cost is rising while the architecture that produces verification by inspection is the architecture that hedges the liability, on the same deployment.

AI runs on the same architecture

Provenance, reproducibility, federation, and verification — the data properties any defensible AI program needs in order to train, document, and deploy a model — are the same architectural properties Tier 3 produces by default. Content addressing produces provenance. Persistence across the lifetime of any model trained on the corpus is exactly what Tier 3 delivers. Permissioned distribution networks produce federation without consolidating sensitive data into a single trust domain. A single cryptographic query produces verification any third party can independently re-run.

The infrastructure that hedges an institution's data-loss exposure is the infrastructure that produces its AI-ready substrate. The same investment holds both positions on the same deployment.

The infrastructure already exists

A standalone Tier 3 node — a BitTorrent seeder, a Forgejo instance, an IPFS pinning node, a Matrix homeserver, an AT Protocol PDS, a Tor relay, an Academic Torrents seeder — runs $42 to $360 a year on commodity hosting. Meanwhile, typical on-premises servers run at 12 to 18 percent of capacity, networks at 26 percent, on bandwidth contracted at flat rates regardless of traffic. The marginal cost of adding a protocol node to existing institutional infrastructure approaches zero. TU Dortmund, TU Dresden, MIT, and the forty-five-plus universities running Tor relays already do it.

What you need to do

  • An architectural audit of every research dataset against the four tiers. Record the number of independent copies, the failure domains they occupy, and the verification capability available.
  • At least one Tier 3 node on existing institutional infrastructure within twelve months. The reference deployments exist. The operational overhead fits inside a student-volunteer team.
  • Compliance evidence generated at the point of deposit. Produce content addresses, hashes, and signed attestations as the data lands, instead of reconstructing them under audit.
  • Verifiable evidence of preservation required of grantees, not self-reported plans. Replace the human-readable plan with the inspectable artifact.
  • F&A funding for preservation, not project funding. Three-year grants cannot underwrite multi-decade obligations.
  • Local clones of everything that matters, as standard practice at the lab level. A single local clone is the difference between a Tier 1 access restriction producing permanent loss and producing temporary inconvenience.

How

The infrastructure exists, and it's fairly straight-forward to deploy. The economics favor deployment by more than an order of magnitude while the compliance regime appears to be closing the window in which the decision is voluntary. And that same deployment positions the institution for the emerging AI-data-readiness funding cycle.

For institutions: SciOS's Resilient Data Futures Lab is coordinating reference deployments, audit templates, and cost models across institutions via the RDF working group out of the lab. If you'd like our help directly implementing a Tier 3 solution for your data, we're ready to embed with your team, identify the solutions that best fit your processes, and to get it running. Reach out at contact@scios.tech to scope the engagement. If you'd like to move forward on your own, ask your faculty and students. Someone at your institution almost certainly wants to implement Tier 3 infrastructure (or already has).

For faculty/students/contributors: If research data, distributed systems, and AI-ready data, are in your native vocabulary, the next decade of scientific infrastructure is yours to architect. The RDF working group out of the Resilient Data Futures Lab meets monthly (next call on May 7th). Join the Resilient Data Futures Lab for an invitation to the calls where we discuss various solutions and our progress implementing them.

For builders: If the need to implement solutions is in your blood, whether at your own institution or on a laptop in your basement, SciOS builds daily. Reach out to join us: contact@scios.tech.

"Publishing" Method — 43 questions, 53 claims, 112 pieces of evidence, 6 methods, and 135 sources

The full paper is at rdf.scios.tech/narratives.

Beneath the paper, we structured our work as a discourse graph, a communication method designed to make every claim, evidence item, question, source, and method individually addressable and individually contributable. A separate post on what this publishing form changes about scientific communication is on the way, or you can read more about Discourse Graphs now.

To engage with this paper — provide evidence that counters a claim, pose a new question, discuss the details of a claim or node, and so on — the discourse graph and contribution model live at github.com/jring-o/rdf, and the rendered narrative, narrative generator, node browser, and node creator are at rdf.scios.tech.

As always, feel free to reach out for questions, comments, engagements, or just to say hello.

contact@scios.tech

The Future of Science Depends on Open Source Engineers

April 7, 2026

The processes of modern science, from how research gets funded and conducted to how it gets published, evaluated, and preserved, were never engineered. They emerged over hundreds of years, built by researchers and institutions one workaround at a time. What we call "the scientific system" is really a patchwork of customs, formats, and platforms that were never designed to work together, never stress-tested at scale, and never designed to evolve.

And now that system is failing in ways that matter.

What's actually broken

A published paper gets a DOI, a semi-persistent, citable address. But the dataset underneath it? The code that produced the analysis? The protocol that generated the data? The peer reviews that shaped the conclusions? Those get nothing. They live on a grad student's laptop, in an institutional server with no preservation guarantee, or nowhere at all. The paper is the only artifact the system treats as real. Everything that actually produced the result, everything you'd need to verify it, reproduce it, or build on it, is structurally invisible.

Worse, that published paper is treated as a product, not an artifact of a research process in which you engage. A team spends three years refining a method, generating data, and iterating on analysis. The world sees none of it until a paper drops at the end. A methodological breakthrough in month four that could save another lab six months of dead ends stays locked in a single group's workflow. Intermediate datasets that could anchor entirely new studies sit on local drives until the "final" version gets published, if it ever does. The infrastructure has no concept of work-in-progress. There is no mechanism to share a partial or null result, get credit for it, and let others build on it. So science's most valuable outputs, the accumulating work of the research process itself (all the way down to the discussion and notes level), are simply lost.

The data and artifacts that do get shared are shockingly fragile. When a single agency loses funding, entire repositories go dark, and the datasets inside them vanish. We're watching this happen in real time. Across U.S. federal agencies right now, research data that took decades and hundreds of millions of dollars to collect is disappearing because the preservation model was centralized, underfunded, and architecturally brittle. One budget decision, one political shift, and years of scientific work ceases to exist. There is no redundancy. There is no fallback.

Then there are the invisible dependencies. Modern research runs on open source software, like the rest of digital society. NumPy, R, and the deeper software infrastructure and domain-specific packages are often maintained by one or two people in their spare time. And, in a cruel twist worth its own discussion, research grants do not fund software maintenance or practices.

Perhaps most fundamentally: there is no infrastructure for coordination. Researchers working on related problems across labs, institutions, and disciplines have no way to find each other. Pipelines, methodologies, and practices in one field that could transform multiple adjacent fields never propagate while the technological infrastructure they utilize is built independently for immediate, one-off uses; FAIR workflows, storage solutions, and other technical systems are created from scratch again and again, solving the same engineering problems over and over simply because nothing connects the needs and efforts of and from various research endeavors. Each of these individual, entity-centric systems is desperately incompatible and adds to the fog, choking the necessary shared solutions behind technical debt and sunk cost fallacies.

Infrastructure shapes practice

Infrastructure doesn't fail passively. When the only thing that gets a persistent identifier is a paper, publishing papers becomes the only thing that matters. When there's no infrastructure for sharing incremental results, researchers have no choice but to sit on their work until it's "complete." When there's no technical substrate for collaboration, the same problems get solved independently in lab after lab.

Even researchers who want to work more openly by sharing data, releasing code, and publishing in progress struggle to do so. The infrastructure exists for finished products, not ongoing processes, and the will to work openly can't overcome that alone.

Our scientific system isn't failing due to a failure of scientific thinking or culture. It's failing due to compounding failures of engineering.

Open source already solved this

This should sound familiar to anyone in open source, because open source was built by distributed communities precisely to coordinate living, evolving systems. Version control. CI/CD. Dependency management. Package registries. Distributed architecture. Governance models. These are tools for managing software development, an ongoing, collaborative, cumulative process, and science, fundamentally, is exactly the same. A hypothesis evolves. Data accumulates. Code gets revised. Results build on each other. Open source built infrastructure for a system you operate and improve. Science built infrastructure for a product.

AI makes this urgent

Now layer on AI. The research apparatus is generating results, datasets, analyses, and code at volumes the current infrastructure never imagined. Every AI-assisted study produces more artifacts, more dependencies, and more downstream connections that need to be tracked, identified, and preserved. The infrastructure that was already failing at human speed is about to face machine speed and machine volume. Without intervention, the next decade of research will produce unprecedented volumes of work that can't be reproduced, verified, or preserved.

What needs to be built

The next generation of scientific infrastructure is an engineering challenge. Here's what it requires:

  • Cryptographically permanent, free, hyper-granular identifiers for every research artifact. Not just papers, but datasets, code, protocols, reviews, claims, figures, and so much more. Every component, line, and symbol must be independently findable, verifiable, reproducible, and citable.
  • Modular, independently reviewable components. Research broken into pieces that can be executed, reviewed, funded, and attributed separately.
  • Interoperable, flexible, on-the-fly adaptable schemas and tooling. Labs working on the same problem must be able to combine their data without losing meaning, and cross-domain use must be possible when the opportunity arises.
  • Integrated provenance tracking. An automatically generated audit trail from funding to published claim, supported by rigorous evidence.
  • Reproducible execution environments. Anyone must be able to re-run an analysis and get the same result.
  • Distributed preservation and compute. No single point of failure, no single funding cut that wipes out a field's data, and compute access for researchers that scales with the compute potential of society.
  • Large-network governance models. Community governance that works across disciplines, institutions, and borders.

The opportunity

Governments and funding agencies worldwide are mandating open access, FAIR data, and reproducibility. Billions in research funding now come with these requirements attached. But the infrastructure to actually comply doesn't exist. The engineering brilliance to build it does… in the open source community.

This is a once-in-a-generation infrastructure buildout. Building the next generation of scientific infrastructure requires software architects, maintainers, DevOps practitioners, OSPO leads, community builders, and governance designers. Everyone who knows how to build and sustain systems that work as ongoing processes.

The field is growing. The funding is there. The mandates are real. And the open source community is uniquely positioned to help build the infrastructure that will power science for the next century.

If you've ever thought science wasn't your domain of expertise, think again. It might be the single domain that needs you the most.

Get involved.