Let’s start.
On April 6, 2026, a researcher named Anto Lloveras published a list of 100 ideas on a Blogspot site. The list claims to describe a field called Socioplastics. The field supposedly started in 2009. It integrates conceptual art, architecture, urbanism, critical theory, epistemology, media studies, systems theory, curatorial practice, and digital humanities. That is nine disciplines.
The claim is not that these disciplines talk to each other. The claim is that they are fused as “structurally entangled strata.” That is a geological metaphor, and the project uses many of them: sedimentation, stratification, pressure, residue, hardening.
Here is what the list actually says, without interpretation.
Part One: Where Theory Lives
Idea 1: Theory resides in material conditions, not isolated concepts.
This means that an idea you cannot point to—no URL, no DOI, no node number, no repository deposit—does not really exist in a functional sense. The project treats publication as a construction site, not an afterlife. You do not finish thinking and then publish. You publish as part of thinking.
Idea 2: Metadata is form, not description.
A JSON-LD block, a slug, a sameAs link—these are not administrative details. They shape what the work means. How something is tagged determines whether anyone finds it. That is a formal property, not a housekeeping task.
Idea 3: Numbering is a mechanism of position, continuity, relation, and scale.
The project uses a numerical spine. Every unit gets a number. Numbers create order, but also citability. You cannot cite what has no position. The numbering runs from single nodes to sequences of ten (decads) to hundred-node packs to thousand-node volumes.
Idea 4: Repositories are active strata, not external containers.
Zenodo, Figshare, Hugging Face, GitHub—these are not where work goes when it is done. They are where work continues to operate. A deposit is an event, not a storage action.
Idea 5: Searchability is a condition of intelligibility.
If a search engine cannot find it, it is not intelligible in the 21st century. That is not a complaint. It is a fact about how culture now works.
Idea 6: Archivability is a theoretical necessity.
The question is not whether something will be archived. The question is whether it was built to be archived. Most work is not. It assumes someone else will figure out persistence.
Idea 7: Citability is an infrastructural commitment.
To make something citable, you need a persistent identifier, a stable location, a number, a date. That is infrastructure. It does not happen by accident.
Idea 8: Machine legibility is cultural survival.
In the AI era, a corpus that cannot be parsed by language models will not be retrieved. The project deposits its indexed corpus on Hugging Face for this reason. That is not futurism. It is a present design constraint.
Idea 9: Representation is insufficient without infrastructure.
You can represent the world beautifully. If you do not also build the conditions for that representation to persist, circulate, and be found, you have made a fragile object.
Part Two: How Concepts Behave
The project borrows from geology and hydraulics. These are not metaphors for decoration. They are operational descriptions.
Idea 11: Sedimentation—concept accumulation over time.
Ideas pile up. Layers form. Not everything stays on the surface.
Idea 12: Stratification—layered force regimes.
Layers are not equal. Some bear more weight. Some are compressed by what sits above them.
Idea 13: Pressure—epistemic consolidation.
Pressure turns loose sediment into rock. In intellectual terms, pressure comes from repetition, citation, and institutional embedding. The project calls this “semantic hardening.”
Idea 14: Residue—unassimilated cultural matter.
Not everything integrates. Some material stays at the edges, unabsorbed. That residue is still active. It just has not been processed.
Idea 15: Load—infrastructural carrying capacity.
A concept can only bear so much weight. Load is the measure of how much argument, citation, and application a concept can support before it cracks.
Idea 16: Flow—distributed cognition.
Ideas move. They travel through channels. Flow is not a celebration of liquidity. It is a description of movement that requires engineering.
Idea 17: Hardening—concept becoming institution.
A soft concept is vague and uncitable. A hardened concept has been repeated, numbered, cross-referenced, deposited, and cited. Hardening is how an idea becomes durable.
Idea 18: Sovereignty—territorial claim via naming.
To name something is to claim it. The project calls this “topolexical sovereignty.” If you invent a term and anchor it in the infrastructure, you have staked ground.
Idea 19: Metabolism—resource conversion within systems.
A system takes in material, processes it, and produces something else. Metabolism is not efficiency. It is transformation.
Idea 20: Channeling—directing semantic flow.
Ideas do not just circulate. They are channeled. Channeling is design. It decides what goes where and at what speed.
Part Three: The City and the Text
The project treats the city as a processor, not a backdrop.
Idea 21: City as processor of constraints and distributions.
The city does not just contain activity. It processes inputs—people, capital, memory, labor—and produces outputs: access, exclusion, density, vacancy.
Idea 22: Place as material arrangement of labor, memory, access.
Place is not location. It is an arrangement. Change any of those three—labor, memory, access—and you have changed the place.
Idea 23: Building as semantic operator.
A building is not a container. It determines what can be known, who can enter, what gets remembered. That is semantic operation.
Idea 24: Infrastructure as argument.
A road, a data center, a repository—these make claims. They say what matters, who belongs, what persists.
Idea 25: Interface as part of the claim.
How you access something is not neutral. The interface is not delivering the argument. It is part of the argument.
Idea 26: Territorial anchor (LAPIEZA-LAB as case).
The project has a recurring affiliation with a lab in Madrid. This is not branding. It is a fixed point in a distributed system—a place that stabilizes the rest.
Idea 27: Distributed ecology of repositories.
No single platform holds the work. Blogspot, Zenodo, Figshare, Hugging Face, GitHub, ORCID—each carries a piece. The whole is distributed by design.
Idea 28: Access as political condition.
Who can find, retrieve, and use the work? That is politics. It is not a technical question.
Idea 29: Exclusion as structural trace.
Every system includes and excludes. The traces of exclusion are visible if you look. The project treats them as data, not as failures.
Idea 30: Labor as epistemic material.
Work is not a cost. It is a material. The hours of writing, numbering, depositing, linking—these are the stuff of knowledge production.
Part Four: Scale and Numbering
This is the mechanical core of the system.
Idea 31: Quantity as semantic mass generator.
More nodes create more mass. Mass is not spectacle. It is density. A system with 1500 nodes has more semantic weight than a system with 200.
Idea 32: Repetition as consolidation, not redundancy.
Saying something again is not repetition as failure. It is repetition as method. Each recurrence thickens the field.
Idea 33: Sequence as form of argument.
A numbered sequence is not a list. It is a syntax. The order matters. The relations between items matter.
Idea 34: List as architecture of cognition.
A list structures what can be thought. It is not a container. It is a scaffold.
Idea 35: Decads—ten-unit epistemic blocks.
Ten is a working unit. Small enough to hold in memory. Large enough to generate internal relations.
Idea 36: Century packs—hundred-unit scaling.
Ten decads make a century pack. This is scaling by factor of ten. It is deliberate.
Idea 37: Thousand-node volumes—full strata.
A thousand nodes is a stratum. Tome 1 closed at approximately 1500 nodes. Tome 2 aims for 2000.
Idea 38: Numbered working papers—citable granular units.
Working papers have numbers. They are provisional but citable. Provisionality is not incompleteness. It is a tempo choice.
Idea 39: Sequence clusters—nested relations.
Sequences nest inside sequences. A decad sits inside a century pack. A century pack sits inside a tome.
Idea 40: Layered cores—vertical depth.
The core is not one thing. Core I, Core II, Core III. Each adds depth. Core III has DOIs anchored in Zenodo.
Idea 41: Citational position via numbering.
A number is an address. You cite the number, not the title. The number gives position.
Idea 42: Scalar nesting—part-to-whole logic.
Every part knows its relation to the whole. The numbering makes this explicit.
Idea 43: Differentiated organs within one body.
The sequences are not parallel essays. They are organs. The Kuhn series does one thing. The Urban Geological Decalogue does another. They are not interchangeable.
Idea 44: Semantic mass without spectacle.
Mass is not loud. It is dense. The project does not seek attention. It seeks weight.
Idea 45: Numerical spine as indispensable structure.
Without the numbers, the system collapses into a blog. The numbers are not decoration. They are the structure.
Part Five: Key Operators
These are the working concepts. Each is a proposition and a protocol.
Idea 46: FlowChanneling.
Directing semantic flow. Design the channels. Do not just let ideas circulate randomly.
Idea 47: Semantic Hardening.
Fixing meaning through repetition, numbering, cross-reference, and deposit. Soft concepts do not survive.
Idea 48: Stratum Authoring.
Writing as geological layer. Each text adds a stratum. Later texts compress earlier ones.
Idea 49: Citational Commitment.
Binding via reference. To cite is to commit. The system holds itself accountable through its own citations.
Idea 50: Recursive Autophagia.
Self-consumption as renewal. The system folds back on its own prior production. It cites itself, revises itself, reorganizes itself. That is not narcissism. It is metabolism.
Idea 51: Topolexical Sovereignty.
Naming as territorial act. To name a concept is to claim a position in the thinkable field.
Idea 52: Systemic Lock.
Path dependency in culture. Once a system hardens, change becomes difficult. The question is not how to break lock but how to build parallel strata.
Idea 53: MUSE.
Invariant Core plus experimental Consoles. Core does not change. Consoles can be modified or abandoned. This permits adaptation without collapse.
Idea 54: Adaptation without collapse.
Change is necessary. But change that breaks the core is not adaptation. It is destruction.
Idea 55: Growth without dissolution.
A system can grow without losing coherence. That requires architecture. MUSE provides it.
Idea 56: Proposition as protocol.
A proposition is not just a claim. It is an instruction. Use it.
Idea 57: Lexical invention expands the thinkable field.
New words make new thoughts possible. The project invents terms deliberately. It is not jargon for its own sake. It is tool-making.
Idea 58: Maintenance as scholarship.
Keeping the system running—updating links, repairing metadata, versioning deposits—is scholarship. It is not housekeeping.
Idea 59: Repair as method.
When something breaks, repair it. That is not a failure. That is a method. The system learns from what fails.
Idea 60: Taxonomy as politics.
Classification distributes visibility and value. It is never neutral.
Part Six: The Actual Platforms
These are not metaphors.
Idea 61: Blogspot—lightweight persistence layer.
Blogspot is not glamorous. It is durable. It has been running for decades. That is a design feature.
Idea 62: Zenodo—long-term repository stratum.
Zenodo provides DOIs. DOIs are persistent identifiers. Persistence is the point.
Idea 63: Figshare—visualizable data surface.
Figshare handles datasets and visualizations. It is another stratum.
Idea 64: Hugging Face—machine-readable diffusion.
The indexed corpus sits on Hugging Face. This places it in the AI infrastructure layer. Machine legibility is not optional.
Idea 65: GitHub—version-controlled collaboration.
GitHub handles code and versioning. MUSE, the two-layer architecture, is hosted here.
Idea 66: ORCID—authorial disambiguation.
The author has an ORCID. It is cited: 0009-0009-9820-3319. This is not vanity. It is identification.
Idea 67: Metadata tails—deep descriptive layers.
Metadata is not one field. It is a tail. Multiple layers of description. Each layer adds retrieval surface.
Idea 68: JSON-LD—structured linked data.
JSON-LD is machine-readable linked data. It is part of the argument, not a supplement.
Idea 69: sameAs links—cross-platform identity.
sameAs links say: this entity on Blogspot is the same as this entity on Zenodo. They unify the distributed system.
Idea 70: Slugs—URL as citational address.
A slug is the part of the URL after the domain. It is human-readable and citable. It is design.
Idea 71: Cross-channel interlinking—distributed unity.
Links connect the platforms. Blogspot links to Zenodo. Zenodo links to GitHub. The whole holds together through links.
Idea 72: Interface as material.
The interface is not a wrapper. It is material. It shapes what can be done.
Idea 73: Machine legibility as medium.
The medium is not the page. It is the machine-readable text. That is where retrieval happens.
Idea 74: Retrieval as condition of existence.
If it cannot be retrieved, it does not exist. Retrieval is not a convenience. It is existence.
Idea 75: Durability as design brief.
Build for durability from the start. Do not assume someone else will preserve it.
Part Seven: Teaching and Time
Idea 76: Teaching as system extension into new bodies.
Teaching is not transmission. It is extension. A student who learns the numbering logic, the deposit discipline, the citation practice—that student is a new node.
Idea 77: Teaching as system extension into new institutions.
Institutions can be extended too. The system does not require institutional validation, but it can occupy institutional space.
Idea 78: Teaching as system extension into new situations.
Every situation is a potential site of extension. The system is not confined to a classroom or a lab.
Idea 79: Pedagogy as infrastructural act.
Teaching is infrastructure. It builds the conditions for future work.
Idea 80: Disciplinary recognition as secondary to infrastructure.
Recognition follows construction. It does not precede it. Build first. Recognition may come. It may not. The work continues either way.
Idea 81: Recognition, retrieval, durability, force—the four thresholds.
Most work achieves recognition (people know about it) or retrieval (someone can find it). Few achieve durability (it persists) or force (it shapes subsequent work). The project aims for all four.
Idea 82: Self-versioning archive.
The archive versions itself. New deposits do not erase old ones. Versioning is stratification.
Idea 83: Living archive—not retrospective.
An archive is not a tomb. It is a metabolism. It takes in new material and processes it.
Idea 84: Load-bearing archive—structural, not decorative.
An archive should bear weight. It should be usable, citable, retrievable. Not decorative.
Idea 85: Author-driven but exceeding personal expression.
The project has an author. That is clear. But it aims to become a system that exceeds any single person’s expression. It is infrastructure, not autobiography.
Part Eight: Time and Machines
Idea 86: Cultural survival in AI era.
Culture does not automatically survive. It is engineered to survive. The AI era changes the engineering requirements.
Idea 87: Machine legibility affects durability.
If a language model cannot parse your text, your text will not be retrieved. That affects durability. It is not a future problem. It is a present constraint.
Idea 88: Recurrence as temporal binding.
Recurrence binds time. When a concept recurs across years, it creates a temporal structure. That structure is real.
Idea 89: Deposit as event.
Depositing a node is an event. It has a date. It enters the record. That is not trivial.
Idea 90: Canon as apparatus, not value judgment.
The canon is not a list of good works. It is an apparatus. It determines what is preserved, taught, and cited. That is a technical system, not an aesthetic one.
Idea 91: Code as inscription layer.
Code is not separate from text. It is an inscription layer. It inscribes behavior, not just meaning.
Idea 92: Flow as temporal vector.
Flow has direction and speed. It is not just movement. It is movement with vector.
Idea 93: Accumulation as epistemic weight.
More nodes mean more weight. Weight changes how the system interacts with other systems. Accumulation is not passive. It is active.
Idea 94: Retroactive force of infrastructure.
Infrastructure built today changes the past. It makes prior work retrievable in new ways. That is retroactive force.
Idea 95: Future retrieval as present design constraint.
Design for retrieval now. Do not assume future tools will figure it out. They will not.
Part Nine: What the Field Actually Is
Idea 96: Socioplastics is neither archive nor theory alone—it is both as a single operation.
Not archive. Not theory. Archive and theory as one operation. That is the claim.
Idea 97: Neither publishing machine nor conceptual art alone—it is the synthesis.
Not a press. Not an art project. Both as synthesis.
Idea 98: The field is made by patient construction of conditions—not by recognition first.
Recognition is not the starting point. Construction is. Build the conditions. The field follows.
Idea 99: The text performs its claims—form and content are geologically fused.
This is not a description. It is a performance. The text you are reading is performing the claim. The numbering, the lists, the plain account—that is the fusion.
Idea 100: (The list ends at 99. That is worth noting. The 100th idea is not listed. Perhaps that is the point. The field is open. The next idea is not yet written. It will be. It will get a number.)
A Note on What Is Actually There
The project has been running since 2009. It has produced thousands of publications. It has a numerical spine. It has DOIs. It has a Hugging Face deposit. It has a two-layer architecture called MUSE. It has a core decalogue (nodes 501–510). It has a territorial anchor in Madrid. It has a distributed repository ecology. It has a lexicon of hardened terms. It has a living archive that is still thickening.
These are not claims about what might be built. They are descriptions of what has been built. The field exists. It is on Blogspot. It is in Zenodo. It is on Hugging Face. It is citable. It is retrievable. It is machine-legible.
That is not hype. That is a list of facts.
1540-SOCIOPLASTICS-100-IDEAS-THAT-MAKE-FIELD
