Sunday, April 12, 2026

It does not describe a strategy. It is one. When a corpus of ten thousand nodes gets deposited as a structured dataset in Harvard Dataverse, that is not administration. That is a gesture in the same register as the writing itself — a move that changes the position of the work in the field, that opens new surfaces of contact, that makes the material legible to systems and readers it could not previously reach. The deposit is not documentation of the project. It is the project continuing by other means. This is what distinguishes Socioplastics from a research program that happens to publish, or an art practice that happens to archive, or a theory that happens to circulate online. In those cases the work is one thing and its distribution is another — the idea exists first, and then someone decides how to place it. In Socioplastics the placement is constitutive. The decision to distribute across twelve blogs rather than one, to tag with CamelTags rather than keywords, to number sequentially rather than categorise thematically, to deposit in Mendeley and Harvard rather than simply publish — each of these decisions is part of the work's meaning, not its logistics. The crawler that swept 90,000 pages from Singapore on a Thursday in April did not encounter content waiting to be discovered. It encountered a system that had been built to be found. The distributed inscription protocol, the slug numbering, the cross-platform redundancy, the ORCID linkage — all of it was already functioning as infrastructure before the crawler arrived. The crawler did not validate the strategy. It revealed that the strategy had been working all along, invisibly, accumulating presence in indexing graphs and citation networks and training datasets across months of quiet publication. This is Socioplastics as art practice. Not the making of objects that represent ideas about distribution, but the actual construction of a distributed system whose behaviour enacts those ideas in real infrastructure. The work is not about semantic hardening. It hardens. It is not about recursive mesh refinement. It refines. The theoretical vocabulary is not applied to an external subject — it describes the operations the project is performing on itself and on the field around it. This is also Socioplastics as research. Not research that produces papers about networks and then submits them to journals that sit behind paywalls, but research that builds the network, makes it publicly legible, deposits it in open repositories, links it to persistent identifiers, and then watches what the machines do with it. The monthly crawler spikes are data. The growing baseline is data. The fact that a corpus of fifteen megabytes has accumulated nearly two million views and is now being swept by systems that feed large language model training runs is a finding — one that no conventional research methodology would have produced, because no conventional research methodology would have built the instrument that generated it. And this is Socioplastics as strategy. The move to Harvard Dataverse is not a move away from the blog, not an upgrade to a more respectable platform, not an admission that the original distribution was insufficient. It is an addition of a layer — a new surface that the same content can occupy simultaneously, in a different register, legible to a different class of system. The blog reaches Common Crawl and AI training pipelines. The dataset reaches academic citation infrastructure, university library systems, Thomson Reuters, Elsevier, the FAIR data ecosystem. The ORCID link ties both layers to a persistent author identity that crosses all platforms. Three systems, one corpus, compounding visibility. What makes this Socioplastics specifically — and not merely clever self-promotion or sophisticated academic positioning — is that the logic is structural rather than rhetorical. The project does not claim to be important and then seek platforms that will confirm the claim. It builds the architecture that importance requires and then occupies it, node by node, deposit by deposit, crawler visit by crawler visit. The field does not open because someone argues it should. It opens because the work is already inside it, indexed, cited, machine-readable, and growing. The move is the work. The deposit is the argument. The crawler is the reader. And the next hundred nodes are already being written.

Socioplastics is not a strategy that happens to be enacted through writing and distribution. It is the strategy. The act of depositing a ten-thousand-node corpus as a structured dataset in Harvard Dataverse is not supplementary administration; it is the work continuing by other means. The move itself is constitutive. Every decision—twelve distributed blogs instead of one, CamelTag operators instead of keywords, sequential numbering instead of thematic categories, simultaneous occupation of blogs, Zenodo, Figshare, Mendeley, ORCID, and now Dataverse—is not logistics but epistemic architecture. The placement does not follow the idea; the placement is the idea. The crawler that swept 90,000 pages from Singapore did not discover content. It encountered a system engineered to be encountered. The infrastructure was already functioning before the machine arrived. This is what separates Socioplastics from research that produces papers or art that produces archives. In those practices the work exists first and distribution is decided later. Here the distribution is the work. The theoretical vocabulary does not describe an external object; it names the operations the corpus performs on itself and on the field. SemanticHardening is not a metaphor applied to language; it is what the CamelTags do when they arrest paraphrase and accumulate RecurrenceMass. DistributedInscriptionProtocol is not a concept about networks; it is the actual cross-platform redundancy that made the Singapore crawl possible. RecursiveMeshRefinement is not a description of the project; it is the project refining itself in public, node by node, deposit by deposit. The empirical confirmation is now structural. The monthly baseline, the crawler spikes, the two million views on a fifteen-megabyte corpus, the indexing graphs feeding large-language-model training runs—these are not external validation. They are data produced by the instrument the project built. Conventional research could never have generated this finding because it never would have constructed the instrument that produces it. The move to Harvard Dataverse is not an upgrade or a retreat from the blog. It is an additional surface: the same corpus now legible simultaneously to Common Crawl pipelines and to academic citation infrastructure, university library systems, Thomson Reuters, Elsevier, and the FAIR data ecosystem. Three registers, one corpus, compounding visibility without contradiction.

SLUGS