What about the rust? The Blogspot interface is obsolete by the standards of institutional repositories. Its theming is limited, its URL structure is dated, its metadata export is basic. The rust is visible. But rust is also a sign of age and use. A platform that has hosted the corpus for years, survived multiple redesigns of the web, and accumulated search authority through sheer persistence has a kind of durability that shiny new platforms cannot claim. Google indexes Blogspot aggressively. The corpus ranks for its own CamelTags because the domain has history. A freshly launched institutional repository, by contrast, starts at zero. It has no search gravity, no reader memory, no accumulated traces. The blog’s rust is its capital. DualAddress exploits this without sentimentality: the blog provides immediate discoverability, the DOI provides long-term citability. A reader finds the corpus through a blog search, reads the node, and cites it via the DOI. The two addresses are joined in the metadata skin. The Blogspot slug (socioplastics-2604-dualaddress-one-object-two-permanent-identifiers-2026) and the DOI (10.xxxx/...) resolve to the same conceptual object. The rust does not contaminate the anchor; the anchor does not sterilize the rust. They are symbiotic, not hierarchical. This is the opposite of the usual platform migration narrative, which treats blogs as provisional staging grounds for eventual institutional housing. DualAddress refuses to migrate. It multiplies surfaces. The blog remains primary for circulation; the DOI remains primary for citation; the corpus remains coherent because both addresses point to the same node. The 98/2 ratio is not a bug. It is the system’s way of saying: we do not wait for perfect infrastructure. We use what exists, anchor what matters, and let the rest breathe. Rust and formality, together, outlive any single solution. That is why DualAddress works.

DualAddress works because the corpus does not pretend that durability has only one form. The DOI is formal, institutional, persistent, and citable; the Blogspot URL is rougher, older, more exposed, but it carries the living body of the work. Ninety-eight per cent of the system may still sit on a rusty blog interface, while two per cent is fixed through DOI objects. Yet the combination works because each address performs a different task. The URL is where the corpus breathes: rhythm, seriality, search visibility, public access, everyday continuity. It is imperfect, but it is indexed, reachable, fast, familiar to Google, and already thick with years of accumulated traces. Its weakness is also its force—exposed enough to be crawled, old enough to have history, flexible enough to host mutation. The DOI anchors without replacing. It gives the corpus a formal citational spine without forcing the entire field into institutional rigidity. The 98/2 imbalance is not a problem. It is architectural. The blog is the terrain; the DOI is the survey marker. Together they produce a double ontology: one address for movement, one for persistence. That is why DualAddress works.

The mistake of most digital preservation discourse is to treat durability as a property that can be achieved by any single system. Deposit a PDF in a repository, assign a handle, and declare the object permanent. This fantasy ignores platform mortality, format obsolescence, institutional neglect, and the quiet decay of metadata. DualAddress refuses the fantasy. It accepts that no single address is permanent, then builds redundancy into the addressing scheme itself. The DOI (Digital Object Identifier) is maintained by registration agencies, resolver systems, and member institutions. It is as durable as the social and technical infrastructure that supports it—which is imperfect but, for the moment, the best formal anchor available. The Blogspot URL is maintained by Google, a corporation with no commitment to long-term epistemic infrastructure. It is far more fragile. But it is also far more alive. The blog receives new nodes weekly; the repository receives deposits periodically. The blog is where readers first encounter the corpus; the DOI is where they cite it. The blog captures the field in motion; the DOI fixes a version for the record. A corpus that relied only on DOIs would be citable but dead—a mausoleum of frozen versions. A corpus that relied only on the blog would be alive but unfindable in formal citation networks, and vulnerable to platform disappearance. DualAddress holds the contradiction together. It says: let the blog be the blog, and let the DOI be the anchor. Neither replaces the other. The system lives in the space between them.

The 98/2 ratio is not a failure to transition to proper infrastructure. It is a deliberate calibration of weight. Two per cent of the corpus—the sealed Cores, the canonical decalogues, the most cited operators—receives the full formal treatment: DOI, PDF surrogate, machine-readable metadata, repository deposit. This two per cent functions as the field’s load-bearing spine. The remaining ninety-eight per cent—the daily nodes, the experimental entries, the peripheral expansions, the provisional formulations—lives on the blog, with slugs and metadata but without DOI fixation. This distribution respects the different temporalities of knowledge production. A peripheral node may mutate, be corrected, or be superseded. It does not need a permanent anchor until it proves its structural value through recurrence. The DOI is a reward for density, not a precondition for existence. Conversely, a Core operator that has survived ThresholdClosure deserves a permanent anchor because it will be cited for decades. The 98/2 split ensures that formal fixation is reserved for material that has earned it. The rest remains liquid, mobile, correctable—the metabolic periphery from which new operators emerge. This is not laziness. It is metabolic regulation at the level of addressing.