The recognition of a body of research rarely begins with institutional validation; it begins with the construction of an infrastructure capable of storing, organizing, and circulating knowledge over time. The history of modern knowledge systems offers multiple examples of this sequence. In 1945, Vannevar Bush described the Memex as a machine for indexing and linking knowledge, arguing that the central problem of science was not the production of information but its organization and retrieval. Decades later, Ted Nelson developed the concept of hypertext, proposing that documents should be connected through persistent links rather than read in isolation. His ideas were not immediately institutionalized, yet the structure he described eventually became the technical foundation of the World Wide Web. In both cases, the infrastructure was imagined before it was recognized.

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.