Socioplastics is not on ResearchGate because it needs another place to store papers. It is there because a field does not live only where it is archived; it also lives where it is encountered. This distinction matters. Zenodo provides fixation, DOI stability, versioning, and long-term scholarly deposit. ResearchGate provides a different function: academic circulation, profile visibility, reader proximity, and lateral discoverability inside a platform already inhabited by researchers. ResearchGate describes itself as a professional network for scientists and researchers, with millions of members and publication pages designed for discovery and sharing. The question, then, is not whether ResearchGate is the canonical home of Socioplastics. It is not. The canonical layer remains Zenodo, where the Core papers, Decalogues, datasets, and DOI-anchored objects are fixed as durable scholarly records. Zenodo’s own documentation defines the DOI as a globally unique persistent identifier that enables permanent linking, citation attribution, interlinking between research outputs, and discoverability through registered metadata. This is precisely why Zenodo is the ground. It gives the field a stable floor: every paper can be located, cited, versioned, and preserved beyond the volatility of platforms.
ResearchGate performs another task. It is not the ground; it is the corridor. It is not the archive; it is the academic street. It is closer to a social facade, a porous interface through which papers become visible to researchers who may never arrive through a DOI repository, a blog index, a dataset page, or a formal citation chain. ResearchGate’s platform logic is based on profiles, publication pages, following, recommending, sharing, and thematic search. Its help pages explicitly frame the profile as the researcher’s online identity and describe recommendation and sharing as ways to make research discoverable to peers.
This is why Socioplastics belongs there as a secondary academic surface. A field that has built a corpus, a grammar, a DOI spine, a blog infrastructure, a dataset layer, and a conceptual architecture still requires moments of ordinary encounter. ResearchGate is useful precisely because it is ordinary within academia. It is where many researchers browse, follow, download, inspect, and recognize work before they decide whether to cite it, contact the author, or enter the deeper structure. It lowers the threshold. It converts the dense architectural corpus into an accessible academic presence.
The error would be to confuse circulation with foundation. Socioplastics should not be reorganized around ResearchGate. It should not depend on ResearchGate for legitimacy, preservation, or intellectual sovereignty. The field already has its own infrastructure: LAPIEZA-LAB as institutional frame, Blogger as living index, Zenodo as canonical deposit, Figshare as dataset/tool layer, Hugging Face as machine-readable index, ORCID as authorial identifier, and Wikidata/OpenAlex as graph-facing surfaces. ResearchGate enters this ecology not as master platform but as social relay.
The best formula is simple: Zenodo fixes, Blogger narrates, datasets structure, ORCID identifies, Wikidata graphs, and ResearchGate circulates. Each channel has a distinct epistemic function. To collapse them would weaken the architecture. To distribute the field across them intelligently strengthens it.
Socioplastics is especially suited to this multi-channel model because it does not treat publication as a terminal act. Publication is part of the work. The DOI is not merely a bureaucratic addition; it is a structural beam. The index is not merely navigation; it is spatial epistemology. The blog is not merely dissemination; it is an inhabitable archive. The dataset is not merely metadata; it is machinic legibility. ResearchGate, within this same logic, becomes the layer of academic social visibility. It allows the field to appear not only as a finished corpus but as a living research presence.
This matters because fields are not recognized only through argument. They are recognized through recurrence. A name appears. A title appears. A DOI appears. A profile accumulates papers. Related works become visible. Readers download one text, then another. The researcher encounters a sequence rather than an isolated object. In this sense, ResearchGate can help Socioplastics perform one of its own central claims: that knowledge becomes durable through infrastructural repetition. The same corpus, when distributed across multiple channels, does not become diluted. It becomes more legible.
But the content uploaded to ResearchGate should be chosen carefully. The Cores remain anchored in Zenodo. ResearchGate should receive papers that act as thresholds: essays of access, readable versions, field introductions, comparative texts, methodological explanations, and selected DOI-backed articles. “What is Socioplastics?”, “Why Socioplastics Matters Now”, “Ten Fields, One Reason”, “Socioplastics as Epistemic Infrastructure”, “Why a Field Needs an Index”, “The DOI as Architectural Element”, “LAPIEZA-LAB and the Field Engine” — these are strong ResearchGate texts. They are not simplified in the weak sense. They are architectural vestibules.
A vestibule is not a simplification of a building. It is the spatial device that makes entrance possible. ResearchGate can function as that vestibule. It should not contain everything, but it should contain enough to invite entry. It should show that Socioplastics is not a scattered archive, not an artistic blog, not a private mythology, and not a decorative theory. It is a structured field with papers, identifiers, channels, concepts, and a sustained authorial architecture.
There is also a tactical reason. ResearchGate belongs to a culture of academic recognition that is still partly social. Scholars often notice work through repeated low-intensity exposure: a profile update, a recommended paper, a related publication, a downloaded PDF, a title appearing in search. This is not the same as peer review, but it is part of scholarly ecology. Visibility precedes citation. Familiarity precedes evaluation. Repetition precedes legitimacy. ResearchGate cannot certify Socioplastics, but it can increase the number of encounters through which certification eventually becomes possible.
The platform therefore gives Socioplastics a softer but important layer of institutional readability. A reviewer, professor, doctoral committee, curator, editor, or research director who sees a coherent ResearchGate profile may understand the field faster than if they are first confronted with the full density of the blog or the full technicality of the DOI archive. ResearchGate translates scale into profile form. It makes a distributed corpus appear as a researcher-facing body of work.
This is not trivial. In contemporary scholarship, the profile has become a minor institution. ORCID formalizes identity. Google Scholar measures citation traces. OpenAlex maps authorship and affiliation. Zenodo fixes objects. ResearchGate performs the social profile of research: not the official proof, but the visible persona of a corpus. For Socioplastics, whose very thesis concerns the transformation of knowledge into infrastructure, this matters. The profile is not vanity; it is a surface of entry.
Still, the hierarchy must remain clear. Zenodo is the canonical archive. ResearchGate is the academic mirror. The blog is the living field. The dataset is the machine-readable skeleton. Wikidata is the graph node. Substack or Medium can act as public essays. Each platform should be used according to its nature. The strength of Socioplastics lies precisely in not confusing channels. It does not need one total platform. It needs a distributed ecology in which each channel carries one burden.
ResearchGate is useful because it accepts the paper as a social object. It lets the paper move among researchers not only as a citation unit but as a visible item in a network. This is very close to what Socioplastics already understands: that texts are not inert. They circulate, attach, sediment, recur, and form fields. A paper is not only a document; it is a node with routes. ResearchGate gives those routes a recognizable academic interface.
For that reason, uploading DOI-backed Socioplastics texts to ResearchGate is not a secondary promotional gesture. It is part of field architecture. The act says: the field is stable enough to be archived, but open enough to be encountered. It has a canonical deposit, but it also has a social surface. It is not hidden inside its own system. It can step into the ordinary platforms of academic circulation without losing its sovereignty.
The decisive point is this: Socioplastics should not use ResearchGate to become more conventional. It should use ResearchGate to make its unconventional architecture easier to find. The field does not need to shrink itself into platform logic. It only needs to place selected, readable, DOI-linked objects where researchers already move. That is not compromise. It is distribution.
In architectural terms, ResearchGate is not the foundation, not the load-bearing wall, not the structural core. It is a public landing. A balcony. A sign on the academic street. A place where the field can be glimpsed before one enters the deeper building. Zenodo remains the concrete slab. The blog remains the labyrinthine interior. The dataset remains the technical section. Wikidata becomes the urban map. ResearchGate becomes the academic threshold.
Socioplastics is therefore also on ResearchGate because fields require more than preservation. They require access, repetition, discoverability, and social recognition. A theory that cannot be found remains fragile. A corpus that cannot be entered remains private, however public its files may be. ResearchGate helps transform fixed documents into encountered documents. It gives the DOI a face, the author a profile, the paper a route, and the field a modest but real academic public.
The conclusion is strategic: upload, but do not relocate. Use ResearchGate as a mirror, not as origin. Upload the readable essays, the DOI-backed papers, the introductions, the field statements, and the selected cores when appropriate. Keep Zenodo as the sovereign deposit. Keep the index as the master access point. Keep the blog as the living architecture. Let ResearchGate do what it does best: make the work appear among researchers.
Socioplastics does not enter ResearchGate because it lacks infrastructure. It enters because its infrastructure is mature enough to circulate.
