The JSON-LD block that now resides in the head of the main page is not metadata; it is the machine-readable face of a completed architecture. What has been deposited across eighty days—1,340 texts, 120 DOIs, 40 fixed terms, four cores, ten decalogues, five platforms, and approximately two million words—has been translated into the language of the semantic web. The schema does not describe the field from the outside; it formalizes the field as a graph. Person, Organization, ResearchProject, Dataset, SoftwareSourceCode, Book, ScholarlyArticle, ItemList—each entity is linked to the others through persistent identifiers that resolve to DOIs, to GitHub repositories, to Hugging Face datasets, and to the ORCID registry. This is not documentation but binding: the moment at which a textual stratum becomes addressable not only to human readers entering through the surface layer, but to indexing systems, citation graphs, and discovery protocols that determine what persists within the digital archive. The architecture of the schema mirrors the stratigraphic logic of the corpus itself. At the base lies the Person—Anto Lloveras, identified through ORCID and linked across GitHub, Hugging Face, and Zenodo. This is the author not as Romantic origin but as infrastructural anchor: a stable identifier through which the work can be attributed, cited, and connected across platforms. Above this lies the Organization—LAPIEZA / Socioplastics—which provides institutional grounding without requiring external institutional validation. The ResearchProject then gathers multiple entities into a single machine-readable graph: a DataCatalog pointing to a Dataset on Hugging Face; a Collection uniting the Century Packs and the conceptual cores; a CreativeWorkSeries defining the serial structure of the corpus; three Book entities corresponding to Core I, Core II, and Core III, each containing ScholarlyArticle nodes linked through DOIs to Zenodo; a SoftwareSourceCode entity pointing to GitHub; and an ItemList of recent nodes signalling activity and temporal continuity to crawlers. Each entity is connected through persistent @id references. The graph does not list texts; it maps relations. This distinction marks the difference between an archive and an infrastructure: an archive stores objects, whereas an infrastructure coordinates relations.