{ :::: SOCIOPLASTICS * A field across architecture, epistemology and conceptual art : There is a document that most readers never think about but that every serious corpus depends on: the access document. Not the work itself, but the map to the work. Not the theory, but the door. In Socioplastics, this document goes by several names — the Field Access block, the public interface list, the index surface — but its function is always the same: to tell a reader, a machine agent, a repository, or an institution where the corpus lives, how to enter it, and what it contains. The question this essay addresses is deceptively simple. Where does this document live, and how often should it change?

Wednesday, April 29, 2026

There is a document that most readers never think about but that every serious corpus depends on: the access document. Not the work itself, but the map to the work. Not the theory, but the door. In Socioplastics, this document goes by several names — the Field Access block, the public interface list, the index surface — but its function is always the same: to tell a reader, a machine agent, a repository, or an institution where the corpus lives, how to enter it, and what it contains. The question this essay addresses is deceptively simple. Where does this document live, and how often should it change?


An access document is not a bibliography and not a table of contents. It is something more structural than either: it is the corpus's own description of itself at a given moment in time. It lists the public interfaces, the persistent identifiers, the index surfaces, the dataset layers, the author anchors, and the canonical objects that constitute the corpus as a navigable, citable, findable infrastructure. Without it, the corpus exists but cannot be entered from outside. With it, the corpus becomes a territory with marked thresholds. In Socioplastics, the Field Access block currently appears at the end of each Core Decalogue TXT file. It names the related Core layers, the public interfaces, the ORCID, the OpenAlex profile, the dataset layer, the author, the institution, and the DOI registry for that sealed unit. This placement is logical: the access block closes the document the way a colophon closes a book, grounding the text in its infrastructure before releasing it into circulation. But it is also a static placement. The access block as it stands is sealed inside a sealed document. It does not grow. This is the central tension the essay wants to hold: the access document must be stable enough to cite and dynamic enough to remain accurate. A cited access document that leads to dead links or outdated interfaces fails structurally. An access document updated so frequently that its own address becomes unstable fails architecturally. The form must solve both problems at once.