Skip to main content
SearchLogin or Signup

Trust in Infrastructure

Infrastructures are more than the tools we use, they are a part of the process and we trust them to function properly.

Published onAug 20, 2021
Trust in Infrastructure
·

Abstract

We commonly think of infrastructure as purpose-built tools that enable us to carry out activities and tasks that are typically critically important. In scholarly publishing, these tools are important to us as authors, readers, and practitioners who seek to access and communicate knowledge. In this article, I claim that infrastructure is an activity. It’s not until we press a button, enter a query, or engage it in some way that it can serve the functions it’s built to carry out. In other words, we need to interact with infrastructure in order to make it go. And once we do that, we don’t question whether it will work. In fact, we rely on infrastructure to such an extent that when it fails, we feel betrayed. Infrastructure, then, is an activity that involves our use of tools and engenders our trust. This conception of infrastructure lets us see why it matters so much. Infrastructure is tied to who we are, and our engagement with it impacts who we can become.


Infrastructure as Tool We Rely On

We commonly think of infrastructure as objects, services, software, and networks—as purpose-built tools that enable us to carry out activities and tasks that are typically critically important.1 In scholarly publishing, these tools are important to us as authors, readers, and practitioners who seek to access and communicate knowledge. Consider the following definitions:

We define infrastructure as the systems, protocols, and software that research and scholarship rely on. Open infrastructure...[is] the narrower set of open source solutions that facilitate the creation and dissemination of open content, and empower communities to deliver new, improved collective benefits without restrictions to participation, engagement, or usage. (Invest in Open Infrastructure 2021)

Open science infrastructures refer to shared research infrastructures—including major scientific equipment or sets of instruments, [,,,] collections, repositories, archives and scientific data, open computational infrastructures that enable data analysis and digital infrastructures—that are needed to support Open Science and serve the needs of different communities. (UNESCO 2021, 5)

[Infrastructures are] organisations that provide support services to the OA diamond journals to perform certain technical tasks, such as copy-editing, dissemination, hosting, indexation, preservation, registration or typesetting. (OA Diamond Journals Study 2021, 12)

These definitions differ in scope and content, and target distinct but overlapping communities, including those that may use the infrastructure and those that may be served by it. For my purposes, I will focus on features they have in common. First, infrastructure is functionally defined. We use it as a tool to carry out important tasks, and insofar as we are able to read, publish, discover, communicate, and so on, it has done the job it was built to do. In this way, infrastructure becomes what it is in relation to the activities it supports or makes possible to perform. Just as a tool “emerges in situ,” so infrastructure “emerges for people in practice, connected to activities and structures.” Hence, it’s not a question of what infrastructure is, but when.2 (Star and Ruhleder 1996, 112-113) Second, these definitions pick out infrastructure as means to our ends. Ethan Zuckerman (2020) puts it simply, “Infrastructures are things we build so we can build other things.” Third, we rely on it. Infrastructure is necessary. Without it, we wouldn’t be able to get things done. Taking these features together, we see that protocols, repositories, indexes, and services that underlie production activities, like typesetting, may all serve as pieces of infrastructure according to these definitions.

In this article, I propose a conception of infrastructure that goes beyond its functioning as a necessary tool in our kit. I claim that infrastructure is (1) an activity that involves (2) an agent and (3) her trust in (4) the tools she uses. This conception of infrastructure lets us see why it matters so much. Infrastructure is tied to who we are, and our engagement with it impacts who we can become.

Infrastructure as Activity We Do

Infrastructure figures into our activities. Since it may be conceived as a tool—even if that’s not all it is—we agents are involved in its operation and, even, in determining what (or when) infrastructure is. I propose we think of infrastructure as an activity we do.3 That activity involves our use of tools and, as I will later argue, our trust. Accordingly, I place more emphasis on the individual, the agent herself, in contrast to Susan Star and Karen Ruhleder (1996). In this framing, I follow Christine Korsgaard (2009), who analyzes artifacts as activities. I take this analysis to have implications for infrastructure, insofar as infrastructure is conceived as a species of artifacts. What Korsgaard correctly observes about artifacts should inform our conception of infrastructure.

Recall that infrastructure is often functionally defined the way a tool is. According to Korsgaard, artifacts tend to need some sort of intervention in order to operate.

[Most artifacts] need either a power source, or to be wielded by a human being, or both, before they can perform their functions. It isn’t quite right, then, to say of the vacuum cleaner in your closet that it “can clean floors,” since, actually, until you plug it in and wield it, it cannot. So strictly speaking, artifacts, when they are just sitting around doing nothing…, are incomplete objects that will only start to perform their function when some last part is plugged in or inserted. (36-37, emphasis omitted)

Korsgaard’s incomplete object, or the entity that has yet to be taken up in use as an artifact, is similar to Star and Ruhleder’s notion that infrastructure emerges in practice. This seems right. An author queries the Directory of Open Access Journals (DOAJ) for a potential no-fee publishing venue, a cataloger adds metadata to a record to enable discovery, a student attaches a Creative Commons license to the class project she’s uploading to her institutional repository, and so on. These are all tasks familiar to us in scholarly publishing, broadly construed. And it’s not until the agent engages them in some way that such entities can serve the functions they’re built to carry out. In order for DOAJ, metadata records, Creative Commons licenses, and institutional repositories to be pieces of infrastructure at all, they require an agent to act.

But Korsgaard’s account of artifacts—and what I am saying about infrastructure—is more specific. It places the agent at center, for she “incorporates” the object into her agency. This is the mechanism by which an otherwise incomplete object becomes an artifact.

[T]here is no such artifact as a vacuum cleaner at all. Instead, what you call your vacuum cleaner is actually an entity that, when properly incorporated by you, makes you into a vacuum cleaner. (37, emphasis original)

Just so with infrastructure. We identify the repository as the infrastructure, rather than ourselves and the entire causal chain that led to the availability of our research outputs, because the repository is easy to pick out as the site of action. Korsgaard makes this point of artifacts: she says we pick out a knife as the cause of cutting “because we can use the knife for cutting.” (40, emphasis original) This partially explains why our necessary role in the functioning of infrastructure as infrastructure seems to fade into the background. By conceiving of infrastructure as an activity we do, however, we are less likely to overlook our involvement than if we think of infrastructure more simply as a tool.

Why bother with this conception? It is our ability to engage the tools that enables us to write, read, create and share knowledge—to carry out the tasks that are important to us and to others who depend on their completion.4 And crucially, whether and to what extent we can use them, these tools play a role in determining who can become authors, readers, and practitioners in the first place.5 If we think of infrastructure as an activity we do, then we can see more clearly who is included in it, and importantly, who is excluded from it.

Trust in Infrastructure

So far, infrastructure is an activity that involves the agent and her use of tools. There is one more feature to add. We need to distinguish infrastructure from tools more generally. We rely on infrastructure, just as we rely on tools. But there is something more to it. Infrastructure denotes the tools—and as I argue, activities—that are of central importance to our own functioning. We rely on infrastructure to such an extent that when it fails, we feel betrayed. In short, we pick out infrastructure as such when these tools engender our trust, not merely our reliance on them.

It may seem unintelligible to say that we trust our tools at all, that we instead reserve trust for other people—our friends, family, colleagues, and perhaps the makers of those tools. C. Thi Nguyen (forthcoming), however, argues trust can extend to agents and objects alike when when construed as an ‘unquestioning attitude.’ According to Nguyen, “To trust something...is to put its reliability outside the space of evaluation and deliberation.” (2) When we trust, we have “stepped back from the deliberative process.” (5) Simply, we adopt a disposition of not questioning the tools we use and whether they will operate as needed to carry out our tasks. (10) This is the unquestioning attitude, and Nguyen says, we can’t trust without it. (23) So, we can trust our tools, especially those that are necessary for our success as authors, readers, and practitioners. And when we do, I claim, our tools serve as infrastructure.

Consider trust in the context of scholarly publishing. Journals that use repositories to carry submissions through to acceptance, and publish the final outputs back onto the repository for hosting, are relying on the repository as a necessary means of engaging in a range of publishing activities. This is how Discrete Analysis, Advances in Combinatorics, and Ars Inveniendi Analytica operate using the open repository, arXiv. It’s often remarked that setting up journals this way reduces costs, and the journals are therefore better equipped to remain free of reader- and authorside fees.6 But another reason to find this model valuable is its engendering of trust. By making use of established, open tools that mathematicians are already deeply familiar using, these journal are “lower[ing] the barrier of monitoring, challenging, checking, and questioning” among authors, readers, reviewers, and editorial teams alike.7 (Nguyen, 5) These individuals don’t simply rely on arXiv to host and deliver research; they trust that it does. How so? They don’t question that arXiv will continue to operate in the manner they have come to expect and depend on, and in the case of the journals above, even that arXiv is playing a central role throughout the editorial process. In other words, they engage arXiv to carry out tasks of vital importance to their own ends as agents without monitoring, challenging, and checking that the repository will come through for their purposes.

When we engage infrastructure as infrastructure, we take up these tools into our own functioning as an activity we do—with one last addition: we adopt the unquestioning attitude; that is, we trust. According to Nguyen, trust as an unquestioning attitude is

to let something inside, to let it play an immediate role in one’s cognition and activity….Trust is our mechanism for integrating other people and objects into our own functioning. (5, emphasis original)

When we trust a tool as infrastructure, we are disposed not to question whether it will work. And if our tools do break down or become unavailable, we aren’t just disappointed; we feel betrayed. Consider the acquisition of a tool by one company or entity from another, an all-too familiar phenomenon in scholarly publishing. This is one way a tool may become unavailable to us and erode our trust.8 Following acquisition, a tool may become cost prohibitive, features may be curtailed, or it may shut down altogether. We may continue to depend on such tools, as we may rely on them due to lack of ready alternatives or because their embeddedness in our workflows make them difficult or impossible to extricate. But we no longer trust them, and our attitude shifts from one that doesn’t question their continued performance, toward one of suspicion or uncertainty, perhaps even accompanied by a feeling of betrayal.9 

In fact, the sting of betrayal indicates that we had trusted, and we feel it most strongly toward “[t]he external objects...whose functions are most tightly integrated into our own thinking and functioning.” (Nguyen, 26-27) In scholarly publishing, these are the tools that are critical to our ability to be and become authors, readers, and practitioners. It is no wonder why we are seeking out ways to ensure our tools’ durability, resist their enclosure, and to enhance their availability among individuals and groups who are too often excluded from participating in the creation and sharing of knowledge.

To conclude as we began, with a definition: infrastructure is (1) an activity that involves (2) an agent and (3) her trust in (4) the tools she uses. This conception lets us readily see how fundamental infrastructure is, and it underscores the importance of the work that Invest in Open Infrastructure, UNESCO, and no-fee open access publishers are undertaking in order to develop and maintain the tools that enable us to realize our ends and engender our trust.




📖 read more essays in the “Business of knowing” summer series 📖
Comments
2
Catherine Ahearn: totally. and we see this often in the outcry that occurs when a tool becomes acquired or shuts down. The recent sale of edX comes to mind!
Sarah Kearns: i really like this shift from relying to trusting! how though did arxiv build that trust? you go into the feeling of betrayal when trust is broken, but i’m also curious if you have ideas as to how traditional publishing has become the norm when there does seem to be so much mistrust in the system?
CC
Colleen Cressman: These are good questions. I'd love to hear about the ways we come to trust, in response to your question about how arXiv has built trust over the years. I wanted to focus on what that trust looks like so that it's always our goal no matter our strategy, but I'd love to hear what others have in mind—especially grassroots and local endeavors, in addition to the more obvious declarations and statements of commitment (which are very important, but I wouldn't want us to crowd out other approaches).I responded briefly to the second in-text by noting that our reliance on these tools can keep us from developing new ones, regardless of our level of trust or mistrust. But I also want to add that so much of the current system is rooted in commercialization, profit-seeking, and competition over proprietary ownership. I don't think those are the values that scholars and practitioners share with the companies who do hold them, but digging ourselves out of the ditch takes a lot of resources, especially funds and labor. We know this, and it's difficult. But it's amazing to see so much progress, especially in the space of journals, to take one example. There's greater availability of open-source journal management software than ever before; numerous collective approaches for financing no-fee open access journals, including flips, are available; there are creative uses of open repositories throughout the publishing lifecycle...and more.