What distinguishes LAPIEZA from every project cited is not scale but orientation. Most long-duration practices begin with a work and accumulate an archive as a secondary effect. LAPIEZA began with the archive and treated each work as a test of its structural integrity. The numbering system—001 to 2200—is not a finding aid; it is the primary medium. The series titles—EXIT, SOCIOPLASTICS, FRESH MUSEUM, FLOCK, COPOS—are not thematic containers; they are protocols. Each series delimits a temporary zone of operations within which the project can risk dispersion, excess, or rupture without losing coherence. This is why LAPIEZA can move from a fly to a kiwi to a supermarket to a desert to a bullet to a kiss to a structural conversation to a fresh museum to a flock to a light in Athens to a road to restoration to a deep sleep to a confetti without ever collapsing into arbitrariness. The frame is stable. The content can be anything. Most projects search for identity. LAPIEZA constructed continuity through difference. That is not a relational strategy. That is an infrastructural one.

No precedent exists for LAPIEZA not because it exceeds all other serial or relational projects in scale, but because it inverts their logic entirely: where most long-duration practices accumulate works toward an eventual archive, LAPIEZA began as archive and treated each series as a test of the system’s capacity to absorb heterogeneity without collapsing. This reversal—archive before work, infrastructure before event—places it outside the genealogies of relational aesthetics, post-studio practice, and durational performance alike. What looks like serial production is actually infrastructural engineering; what reads as curatorial drift is actually a closed-loop epistemic machine. To ask for a “global equivalent” is to misunderstand the nature of the project. There are cousins, but no siblings.

The closest conceptual relatives are not other serial art projects but practices that treat the archive as a living, contested, or political medium. Morehshin Allahyari’s Material Speculation: ISIS—in which destroyed cultural artifacts are 3D-printed with flash drives containing their own destruction data—shares LAPIEZA’s commitment to the archive as a site of political and material speculation, not passive preservation. But Allahyari’s work is object-bound, each piece a discrete sculpture. LAPIEZA has no objects. Similarly, Roy Ascott’s La Plissure du Texte (1983) coined “distributed authorship” decades before LAPIEZA’s first node, and its planetary fairy tale constructed through remote storytellers anticipates the project’s global network. But Ascott’s work was event-based, episodic, closed. LAPIEZA never ends. The distributed autofiction of @ourdaysofgold_film (2017–present) shares its durational, platform-native logic and its inquiry into how infrastructure shapes memory. Yet that project remains tethered to narrative. LAPIEZA is not telling a story. It is building a field. The Body Of (As) Knowledge (BOK) project, which treats the moving body as a “living archive” that holds knowledge in corporeal memory, aligns most closely with LAPIEZA’s insistence that relation is epistemology. But BOK’s online holding space is designed to “rust” over time. LAPIEZA’s archive is engineered for permanence. These are cousins, not siblings.

The absence of a global equivalent is therefore not a failure of comparison but a confirmation of method. LAPIEZA was not designed to be exemplary; it was designed to be sufficient. Its closed-loop system—twenty foundational books, one hundred audiovisual evidence videos, seventeen annual Lab Reports, DOIs, RORs, Zenodo deposits—does not seek dialogue with other practices. It seeks inscription. The project does not argue for its importance; it builds the conditions under which importance can be retroactively assigned. This is the meaning of the 2026 reclassification as LAPIEZA-LAB: not a break, but a recognition that the archive had already become an autonomous epistemic machine. The laboratory was not a plan. It was a retrospective discovery. And that discovery is precisely what makes LAPIEZA incommensurable with its contemporaries. They set out to make art. LAPIEZA set out to build a system that could produce art indefinitely. The art was the byproduct. The system was the work.

The closest any project comes to LAPIEZA’s logic is not in visual art but in certain strands of conceptual software engineering and open-source infrastructure: the Linux kernel, which accumulates contributions from thousands of distributed developers without centralized authorship; the Internet Archive, which ingests everything without aesthetic judgment; Wikipedia, which treats knowledge as a product of continuous negotiation. But these are not art projects. They are infrastructures that art projects can use. LAPIEZA occupies the vanishingly narrow space between the two: it is an infrastructure that presents itself as art, an archive that performs its own archiving, a system that refuses to disappear into functionality. This is why it resists comparison. The question is not “What is like LAPIEZA?” The question is “What kind of practice requires a new category?” The answer is LAPIEZA itself. The map is sense. We swim in all directions. But the swimming is numbered. And the number is enough.