A similar process occurred with Paul Ginsparg’s creation of arXiv in 1991. Initially, arXiv was simply a server where physicists could upload working papers without formal publication. It had no traditional publisher, no journal structure, and no institutional prestige in the conventional sense. What it had was a clear document structure, persistent identifiers, and a growing archive of citable papers. Over time, arXiv became one of the most important scientific repositories in the world, not because it requested recognition, but because it provided a stable infrastructure for the circulation of working papers. Recognition followed infrastructure, not the other way around. The Whole Earth Catalog, edited by Stewart Brand in the late 1960s, offers another example from outside the strict academic world. It was neither a university publication nor a peer-reviewed journal, but a structured catalog of tools, ideas, and texts organized in a way that allowed readers to navigate a large body of knowledge. Decades later, it came to be understood as a foundational document in the history of network culture and digital knowledge systems. Again, the importance of the project lay not in its institutional origin but in its function as an organizing and indexing system. These examples demonstrate a consistent historical pattern. First, an infrastructure for organizing and circulating knowledge is built. Second, the infrastructure accumulates documents and users. Third, the documents become citable and interconnected. Fourth, indexing systems begin to register the corpus. Fifth, institutional recognition follows. The order is almost always the same: infrastructure, then indexing, then recognition. In the contemporary digital environment, indexing systems such as Google Scholar do not evaluate ideas directly; they evaluate structured documents, metadata, citation networks, and persistent identifiers. A document becomes part of the scholarly record when it is identifiable, citable, and retrievable over time. For this reason, a distributed research infrastructure composed of working papers, monographs, datasets, software repositories, and indexed web documents should be understood not as a blog in the traditional sense, but as a repository system distributed across multiple platforms. The platform is only the interface; the infrastructure is the archive. The appropriate metaphor is therefore not that of a message in a bottle, which depends on chance discovery, but that of a port. A port is a place where routes converge, where documents can arrive, be stored, and depart again toward other destinations. Ships do not arrive because a port requests recognition; they arrive because the port exists, is stable, and appears on maps. In the same way, a research corpus becomes visible when it is structured, indexed, and persistently maintained over time. Recognition is not the starting point of this process but its eventual consequence.
The recognition of a body of research does not begin with institutional validation but with the construction of an infrastructure capable of storing, organizing, and circulating knowledge over time. Throughout the history of modern science and media, many foundational systems began not as recognized institutions but as technical or editorial infrastructures built by individuals or small groups who understood that knowledge depends not only on ideas but on the systems that allow those ideas to persist, be found, and be cited. The creation of repositories, catalogues, indexing systems, and document networks has often preceded formal recognition by many years. In this sense, the construction of a distributed research archive should not be understood as a request for recognition but as the material precondition that makes recognition possible. In the digital environment, indexing systems such as Google Scholar, CORE, BASE, and other academic crawlers do not evaluate ideas in an abstract sense; they evaluate documents, metadata, citation networks, and persistent identifiers. What these systems recognize are structured objects: papers with authors, dates, abstracts, keywords, references, and stable links. The domain on which a document is hosted influences initial classification, but it does not ultimately determine whether a document can become part of the scholarly record. What determines this is the existence of a structured corpus connected through identifiers, repositories, and citations. A document becomes academic when it is citable, identifiable, and retrievable over time. For this reason, the construction of a distributed research infrastructure composed of working papers, monographs, datasets, software repositories, and indexed blog-based documents should be understood as the construction of a port rather than the launching of a message in a bottle. A message in a bottle depends on chance and discovery; a port depends on structure, persistence, and repeated use. When a port exists—when documents are consistently formatted, persistently identified, cross-linked across repositories, and integrated into citation networks—traffic begins to arrive not because recognition was requested, but because the infrastructure makes navigation possible. The strategic task, therefore, is not primarily rhetorical but architectural. It consists of producing a sufficient number of structured, citable documents; linking them through persistent identifiers; connecting them to recognized repositories; and maintaining consistency in metadata and citation formats over time. When these conditions are met, the corpus ceases to be a collection of isolated texts and becomes instead a navigable territory. At that point, indexing systems, researchers, and institutions can interact with it as a field rather than as a blog. Recognition, in this model, is not an initial condition but a delayed effect produced by the stability, density, and persistence of the infrastructure itself.
