Socioplastics does not grow by protecting a single entrance. It grows by multiplying entrances that all lead back to the same load-bearing core. The project index defines the system as a long-term research infrastructure in which writing, datasets, identifiers, software environments, and semantic metadata operate together rather than separately. It also states the scale of the corpus plainly: more than two thousand indexed entries, organised across three Tomes, with each unit carrying a numerical identifier, a CamelTagged descriptor, and a stable URL. That matters because a system of this size cannot rely on one homepage alone. It needs many doors, each performing a different function, all oriented toward the same conceptual centre.

One door is the Project Index itself: the cartographic entrance, where the field is named, structured, and explained. Another is ORCID, which fixes authorship through a persistent researcher identity. Another is OpenAlex, which places that authorship and its outputs inside an open scholarly graph. Another is the Hugging Face dataset, where the corpus becomes machine-readable through fields such as id, slug, url, tomo, and doi. Another is GitHub, where MUSE appears as the technical and organisational substrate of the system. And then there are the DOI anchors on Zenodo and Figshare, which the index presents not as decoration but as structural documents selected for long-term citability. Each door receives a different visitor: readers, crawlers, indexers, repositories, institutional evaluators, or software agents. The point is not dispersion. The point is distributed coherence. A weak network multiplies surfaces and loses identity; a strong mesh multiplies surfaces and intensifies recognisability. In Socioplastics, every threshold points inward again. The index links to ORCID, OpenAlex, GitHub, Hugging Face, and the main channels; the dataset reflects the corpus as structure; the DOI layer hardens selected conceptual anchors; the semantic layer translates the field into machine-legible entities such as ResearchProject, Dataset, SoftwareSourceCode, and CreativeWorkSeries. The project index says this very clearly: what is not machine-readable is not discoverable. That sentence is the whole strategy in miniature. Porosity is not the opposite of rigour here. Porosity is the condition under which the field becomes harder to erase. This is why more doors make the system stronger. If one platform weakens, the field remains accessible elsewhere. If one reader arrives through a blog post, another arrives through ORCID, another through OpenAlex, another through a DOI, another through the dataset. All of them encounter different surfaces of the same nucleus. The architecture is therefore not symbolic but operational: one layer names, one identifies, one maps, one stores, one cites, one computes. The result is not mere visibility. It is persistence by design. Socioplastics does not circulate as a single site or a single publication series. It circulates as a mesh whose method is already inscribed in its architecture. 

*

*

*

*

*

The more doors a research system has, the stronger it becomes—provided they all lead to the same core. Socioplastics works in this way. It does not depend on a single homepage or a single publication format, but on a distributed set of entry points: the Project Index names and organises the field; ORCID fixes authorship through persistent identity; OpenAlex places the work inside an open scholarly graph; DOI records on Zenodo and Figshare stabilise selected anchor texts; Hugging Face turns the corpus into a machine-readable dataset; GitHub supports the technical layer of MUSE. Each point serves a different function, but all return to the same conceptual nucleus. Project Index ***** This multiplicity is not dispersion. It is structure. A text can be found through the blog, verified through ORCID, mapped through OpenAlex, cited through a DOI, processed through the dataset, and connected technically through code. Every link increases addressability; every addressable unit increases the probability of retrieval, citation, and long-term persistence. What matters is not immediate readership alone but infrastructural legibility. A distributed system survives because it is harder to erase, harder to isolate, and easier to re-enter from many directions. In that sense, porosity is not weakness. It is durability designed as architecture.