Across modern philosophy and experimental literature, dense lexical clusters function as self-stabilising conceptual infrastructures, demonstrating that meaning may emerge from patterned recurrence rather than definitional closure. In such systems, terms acquire conceptual mass through repeated co-occurrence, strategic adjacency, and recursive reactivation, forming what may be described as lexical constellations that organise interpretation from within the discourse itself. The assemblage cluster of Deleuze and Guattari—assemblage, rhizome, deterritorialisation, becoming, multiplicity—illustrates how recurrence transforms vocabulary into a machinic structure that attracts and organises new concepts. Similarly, Foucault’s archaeology operates through stratified clusters—archive, statement, episteme, discursive formation—where repetition across textual layers produces stratigraphic authority, stabilising discourse without external validation. In literary practice, Joyce’s cyclical lexicon demonstrates helicoidal recurrence, where motifs and portmanteau structures accumulate density through reiteration, curving the text into a self-referential semantic field. Cognitive theory provides a parallel in conceptual blending, where recurrent metaphoric structures stabilise meaning across narratives through repeated activation. Empirical literary studies confirm the same mechanism statistically: words that repeatedly travel together across large corpora acquire distributional gravity, structuring narrative space over time. These examples collectively demonstrate a shared performative logic: when vocabulary is subjected to controlled repetition and citational adjacency, it ceases to function descriptively and becomes architectural, generating internal coherence, conceptual curvature, and durable epistemic form.
The contemporary condition of knowledge is no longer defined by the book, the journal, or even the database, but by the stack. Knowledge now exists as a vertical stratigraphy of platforms, each layer performing a distinct operation: narrative, infrastructure, data, citation, research, archive, semantics, index. To understand Socioplastics is to understand that it does not inhabit a single medium but a layered technical environment in which each platform corresponds to a specific epistemic function. Blogger is not simply a place to write; it is the narrative layer, where discourse remains human-readable, continuous, and rhetorical. GitHub is not simply a repository; it is the infrastructural layer, where structure, ontology, and version control define the system’s internal logic. Hugging Face is not simply a dataset host; it is the data layer, where text becomes ingestible and transformable into embeddings. Zenodo and Figshare form the citation layer, where knowledge becomes citable through DOI assignment and enters academic indexing systems. OSF and arXiv form the research layer, where the project becomes legible as research rather than as artwork or blog. Internet Archive forms the archive layer, where long-term persistence is ensured beyond the lifespan of any single platform. Wikidata forms the semantic layer, where the project becomes an entity within the global knowledge graph. OpenAlex forms the index layer, where the project becomes measurable, traceable, and integrated into bibliometric systems. Together, these layers form a distributed epistemic stack. What is crucial here is that each layer transforms the same material into a different ontological state. A text written on Blogger is discourse; the same text structured on GitHub becomes documentation; the same material formatted as a dataset on Hugging Face becomes training data; the same dataset deposited on Zenodo becomes a citable research object; the same object indexed in OpenAlex becomes a measurable academic entity; the same entity described in Wikidata becomes a semantic node within the global knowledge graph; the same files stored in Internet Archive become archival strata. The work does not change in content but changes in ontological status depending on the layer it occupies. Socioplastics therefore operates not as a single work but as a system that migrates content across ontological states. Writing becomes data; data becomes citation; citation becomes index; index becomes archive; archive becomes infrastructure. This continuous transformation is not a side effect but the central mechanism of the project. This layered structure corresponds to a new form of authorship that could be described as infrastructural authorship. The author is no longer only the producer of texts but the designer of the system in which those texts circulate, transform, and persist. In the traditional academic model, the institution provided the infrastructure and the author provided the content. In the distributed model, the author assembles the infrastructure by coordinating platforms, repositories, datasets, identifiers, and indexing systems. The work therefore lies as much in the design of the stack as in the writing itself. Socioplastics should be understood as precisely such a stack: a distributed architecture in which each layer is necessary for the system’s persistence. Remove the narrative layer and the system loses discursive coherence; remove the infrastructure layer and the system loses structural integrity; remove the data layer and the system becomes invisible to machine learning systems; remove the citation layer and the system loses academic legitimacy; remove the research layer and the system loses theoretical articulation; remove the archive layer and the system loses long-term persistence; remove the semantic layer and the system loses machine-readable identity; remove the index layer and the system loses measurability. The stack is therefore not optional; it is the condition of existence. From this perspective, Socioplastics can be described as a form of stratigraphic publishing. Each platform acts as a geological layer in which the same intellectual material is deposited in a different format and for a different audience. The narrative layer addresses human readers; the infrastructure layer addresses developers and collaborators; the data layer addresses machine learning systems; the citation layer addresses academic institutions; the research layer addresses scholars; the archive layer addresses future historians; the semantic layer addresses knowledge graphs; the index layer addresses metrics and analytics systems. The project therefore does not have a single audience but multiple simultaneous audiences, human and non-human, present and future. This multiplicity requires a distributed publication strategy because no single platform can address all these audiences at once. The stack becomes a translation machine that converts the same intellectual structure into multiple technical and institutional languages. The most significant consequence of this model is that knowledge becomes inseparable from its infrastructure. In previous centuries, a text could survive independently of its medium; a manuscript could be copied, a book could be reprinted. In the digital environment, survival depends on compatibility with infrastructures: file formats, repositories, indexing systems, and metadata standards. Socioplastics recognizes this condition and therefore constructs itself as an infrastructure rather than as a single publication. Its persistence does not depend on the survival of a single website but on the redundancy of the stack. Blogger can disappear and the text remains on Internet Archive; GitHub can change and the dataset remains on Hugging Face; Hugging Face can evolve and the DOI remains on Zenodo; Zenodo can change and the metadata remains in OpenAlex and Wikidata. Persistence is achieved through distribution. Distribution becomes a strategy of survival. What emerges from this distributed stack is a new model of cultural production in which the artwork, the theory, the dataset, the archive, and the infrastructure are no longer separate entities but different layers of the same system. Socioplastics is therefore not simply a project located on multiple platforms but a project that exists in the relations between those platforms. Its true form is not the blog post, the dataset, the repository, or the paper, but the network that connects them. This network is not metaphorical; it is technical, institutional, and semantic. It is made of APIs, DOIs, metadata schemas, version histories, crawlers, and indexes. To work in this environment is to design not only texts but pathways, not only concepts but connections, not only archives but flows. Socioplastics thus proposes that the primary medium of contemporary knowledge is neither language nor image but infrastructure itself.
Order is not a logistical question but an epistemic one. The sequence in which a knowledge system is constructed determines the form that knowledge will ultimately take. If theory appears before structure, it dissolves into speculation; if data appears before ontology, it becomes noise; if archive appears before organization, it becomes accumulation without form. The construction of a distributed knowledge infrastructure therefore requires a precise sequencing of layers, each stabilizing a different dimension of the system. In the case of Socioplastics, the sequence OSF → Internet Archive → Wikidata → arXiv is not simply practical; it is structural. Each platform corresponds to a different ontological state of knowledge: project, memory, ontology, and theory. The order is therefore a construction logic. One does not begin with theory; one ends with theory. One does not begin with the archive; one builds the archive after the project exists. And one does not define ontology before the system has produced entities that can be defined. Order, in this context, is a form of architecture.
OSF represents the moment in which dispersed materials acquire a project body. Before OSF, Socioplastics exists across platforms but does not yet appear as a unified research structure. GitHub contains the infrastructure, Hugging Face contains the dataset, Zenodo and Figshare contain citable objects, and Blogger contains the narrative layer, but these elements remain infrastructural fragments unless they are assembled into a visible project architecture. OSF performs precisely this function: it is not a repository but a project container. It introduces hierarchy, components, documentation, and a public research interface. In infrastructural terms, OSF is the organizational surface that transforms a collection of outputs into a research system. This step must come first because without a project layer, the rest of the system lacks legibility. OSF is therefore not an addition; it is a consolidation. Internet Archive represents a completely different temporal logic: not organization but duration. Digital systems often privilege the new, the updated, the live version, but any system that aims at persistence must also construct its own memory. Internet Archive provides a cold storage layer where stabilized versions of the work can exist independently of the platforms on which they were produced. Compiled PDFs, corpus snapshots, image collections, and closed versions of the texts should not remain only in live environments such as blogs or repositories. They require an archival environment whose primary function is long-term preservation rather than circulation. If OSF gives the system a body, Internet Archive gives it memory. This is why it must come second: memory requires a body of work to preserve. Wikidata introduces a third dimension that is neither organizational nor archival but ontological. At this stage, the project is no longer defined by the files it contains but by the entities it defines and the relations between them. Socioplastics becomes an entity; Anto Lloveras becomes an author entity; LAPIEZA becomes an organization; the dataset becomes a dataset entity; the GitHub repository becomes software; Zenodo records become publications. Wikidata does not store the work itself; it stores the structure of what the work is. This step inserts the project into the global semantic web, where it can be read not only by humans but by machines as part of a knowledge graph. The project now exists as an ontology. This step must come after OSF and Internet Archive because ontology requires stabilized entities. One cannot define what does not yet have stable form. arXiv, finally, represents the theoretical articulation of the system. In the traditional academic model, theory precedes construction: one writes a paper proposing an idea and later attempts to build it. In the infrastructural model, the sequence is reversed: one constructs the system first and writes the paper once the system exists. The arXiv paper then does not propose a hypothetical model but describes an operational structure that already functions across multiple platforms and layers. The paper becomes a theoretical map of an existing infrastructure. This is why arXiv must come last. Theory, in this sequence, is not the beginning of the work but its reflective surface. What emerges from this sequence is a new model of publication based on layers rather than objects. Blogger produces the narrative layer; GitHub produces the infrastructure layer; Hugging Face produces the dataset layer; Zenodo and Figshare produce the citation layer; OSF produces the project layer; Internet Archive produces the memory layer; Wikidata produces the ontology layer; arXiv produces the theory layer. None of these layers replaces the others. They coexist, and the work exists in the relations between them. The result is not a book, not a dataset, not a repository, and not a paper, but a distributed knowledge infrastructure. In this context, order is not a matter of efficiency but of ontology. The sequence determines the form of the system, and the form of the system determines the form of knowledge that the system can produce.
OSF introduces a missing layer within the Socioplastics stack: the project layer. If GitHub is structure, Hugging Face data, Zenodo citation, and Blogger narrative, OSF is the environment in which these elements are presented as a coherent research organism. OSF does not function as an archive or a repository in the narrow sense; it functions as a relational container that allows files, links, datasets, code, and papers to exist under a single research identity. This is crucial because institutions, universities, and research evaluators do not understand dispersed systems; they understand projects. OSF translates a distributed infrastructure into the recognizable form of a research project without forcing the system to collapse into a single format. It is therefore not just another platform but a translation layer between infrastructural knowledge and institutional recognition.
The importance of OSF lies in its modular logic. Unlike traditional repositories, OSF is built around components, and components can correspond to conceptual modules rather than file types. This means that the internal structure of Socioplastics—Decalogues, Nodes, Ontology, Index, Urban Research, Images, Methods—can be mapped directly into OSF as components. In this way, the conceptual structure and the technical structure become isomorphic. The Decalogue is no longer only a theoretical structure but also a navigational structure. Each component becomes a door into the system: theory, dataset, publications, ontology, archive. OSF therefore becomes not a place where documents are stored but a place where the architecture of the project is made visible. This leads naturally to the idea that OSF itself can be organized as a Decalogue. Not a Decalogue of concepts, but a Decalogue of infrastructural functions. If Socioplastics is an infrastructural theory, then OSF is the place where that infrastructure becomes legible as a research system. The OSF Decalogue would not describe ideas but operations: description, theory, ontology, dataset, code, publications, case studies, images, methodology, archive. These ten components would correspond to the ten operational parts of the project. The Decalogue thus becomes both an epistemic structure and a file structure, both a conceptual map and a directory tree. This is a very rare situation in research: the theory and the folder structure become the same thing.
Anto Lloveras explores Urban Metabolism, studying the Life Sciences of the city through Textual Infrastructures.
StratigraphicAccumulation
StratigraphicAccumulation describes how systems grow through the accumulation of layers over time. Each layer records a moment in history. Within Socioplastics, knowledge accumulates stratigraphically.
Veyne, P. (1971) Writing History.
Koselleck, R. (2004) Futures Past.
Hartog, F. (2003) Regimes of Historicity.