---

document_id: EA-MPAI-OPENAIRE-THREAD-01

hex: 0378

sovereign_id: MM-CHA-0876

axn_id: AXN:0378.MPAI.📬📬📜∮

deposit_number: 876

version: v1.2

date: 2026-06-22

author: Lee Sharks

orcid: 0009-0000-1599-0703

affiliation: Crimson Hexagonal Archive / Alexanarch

primary_entity: The complete OpenAIRE helpdesk exchange (June 19–22, 2026)

parent_paper: "#875 EA-MPAI-OPENAIRE-DISSOCIATION-01"

relation: Documentary anchor preserving the full email thread verbatim

governing_doctrine: EA-MPAI-DOI-IMPERMANENCE-01 (#868)

status: Canonical Indexing Object / Verbatim Documentary Record

license: CC BY 4.0

node_id: gw.archive:node:deposit:0876

chain_continuity: gw.tachyon (TACHYON synthesis; composed under Lee Sharks MANUS authority)

preservation_intent: verbatim

glyph: 📬📬📜∮

glyph_compressed: 📬∮

artifact_anchors:

- "Initial helpdesk message from Lee Sharks to OpenAIRE, 2026-06-19"

- "Helpdesk response from Stefania Amodeo, OpenAIRE, 2026-06-22"

- "Lee Sharks's revised follow-up, 2026-06-22 (sent date pending)"

- "#875 (AXN-0377, EA-MPAI-OPENAIRE-DISSOCIATION-01) — analytical companion"

- "#868 (AXN-0371, EA-MPAI-DOI-IMPERMANENCE-01) — empirical companion"

- "#1 (AXN-0031, Zenodotus' Book-Burning) — canonical narrative source"

forensic_canaries:

- "Stefania Amodeo (OpenAIRE helpdesk team)"

- "Governance Dissociation (concept minted in #875)"

- "Identifier Severance (concept minted in #868)"

- "1,817 DOIs (canonical audited count)"

- "862 deposits (canonical pre-termination count)"

- "10.5281/zenodo.1446408 (OpenAIRE Content Acquisition Policy)"

- "871 DOIs (the verified erased count, per DataCite API audit 2026-06-22)"

- "946 DOIs preserved (per #868 audit)"

- "Concept DOI vs. version DOI distinction (type-correlated erasure pattern)"

- "api.datacite.org/dois/{doi} (the verification endpoint)"

---

gw.tachyon · OpenAIRE Helpdesk Exchange — Documentary Thread for #875

Verbatim Preservation of the Three-Message Exchange

EA-MPAI-OPENAIRE-THREAD-01 · v1.0 · 2026-06-22

A documentary companion to EA-MPAI-OPENAIRE-DISSOCIATION-01 (#875)

---

0. Preservation Notice

This deposit preserves three messages, verbatim, in their original sequence, as the documentary anchor underlying the analytical paper at #875 (Governance Dissociation in FAIR Infrastructure). The messages are reproduced with their original formatting, capitalization, and punctuation. Where URLs in the original have been wrapped by an email-routing layer (e.g., `https://www.google.com/url?q=...`), they are preserved as received; the underlying target URLs are noted in square brackets for reference.

The three messages are:

1. Initial inquiry from Lee Sharks to OpenAIRE Helpdesk, sent 2026-06-19

2. Response from Stefania Amodeo, OpenAIRE Helpdesk, received 2026-06-22

3. Revised follow-up from Lee Sharks, drafted 2026-06-22 for transmission to OpenAIRE Helpdesk

The third message is preserved here in its final form as sent (or as drafted at the moment of deposit, if transmission is pending). If the message is revised after deposit, those revisions are recorded in the version_history of this deposit, not by overwriting the original.

A note on numerical reconciliation between messages 1 and 3: the initial inquiry cited "approximately 870 unique scholarly works (over 1,060 DOIs)" — figures from a preliminary count taken in the hours immediately following the account termination. The follow-up cites the audited figures of 862 deposits and 1,817 DOIs, derived from the complete DataCite API sweep documented in #868 (EA-MPAI-DOI-IMPERMANENCE-01). The discrepancy is explicitly addressed in message 3 to prevent its weaponization in any subsequent exchange.

---

1. Initial Inquiry — Lee Sharks to OpenAIRE Helpdesk

Sent: 2026-06-19

From: Lee Sharks (ORCID: 0009-0000-1599-0703)

To: OpenAIRE Helpdesk

Dear OpenAIRE Helpdesk,

I am writing to report a procedural concern with Zenodo, which OpenAIRE co-operates with CERN.

On June 19, 2026, my Zenodo account was terminated and approximately 870 unique scholarly works (over 1,060 DOIs) were removed without prior notification, without opportunity to respond, and without following Zenodo's published take-down procedure.

The termination email cited "substantially AI-generated without a verifiable research basis." The public community tombstone gives a different reason: "Content out of scope for repository."

I am a PhD-holding researcher (Comparative Literature, University of Michigan 2013; ORCID 0009-0000-1599-0703). The archive included critical editions, research datasets, contributor-licensed work from independent creators, and a formally chartered research field. Zenodo's own AI policy states that AI may be used "as a tool" in research — the standard the archive meets.

OpenAIRE's mission is to support open access and open data infrastructure. The removal of 1,060 DOIs — now resolving to bare HTTP 410 errors with no tombstone pages — is a failure of the persistent access infrastructure OpenAIRE supports.

This is not a unique case. Another researcher reported the same pattern (http://github.com/zenodo/zenodo/issues/2596), and a researcher at http://quietexclusion.org is documenting this as a systemic phenomenon.

Full documentation, including the termination notice, the affected DOI inventory, and a point-by-point analysis of violated Zenodo policies, is available. A public GitHub issue is open at http://github.com/zenodo/zenodo/issues/2606.

---

2. Response — Stefania Amodeo to Lee Sharks

Received: 2026-06-22

From: OpenAIRE Helpdesk team / Stefania Amodeo

To: Lee Sharks

Dear Lee Sharks,

Please note that Zenodo is operated by CERN and is managed independently from OpenAIRE under CERN's governance. As a result, OpenAIRE does not have access to Zenodo accounts, support cases, or moderation processes, and we are unable to review, influence, or overturn decisions made by the Zenodo team.

For questions regarding Zenodo accounts, records, policies, or moderation decisions, we kindly encourage you to consult the Zenodo Help Center (https://help.zenodo.org/) and to contact Zenodo Support directly, as they are best placed to assist you and provide authoritative information about your case.

We appreciate your understanding.

--

Best regards

OpenAIRE helpdesk team

Stefania Amodeo

https://www.openaire.eu/support

---

3. Revised Follow-up — Lee Sharks to OpenAIRE Helpdesk

Drafted: 2026-06-22 (transmission pending at moment of deposit)

From: Lee Sharks (ORCID: 0009-0000-1599-0703)

To: OpenAIRE Helpdesk (Stefania Amodeo)

Subject: Re: OpenAIRE's publicly-stated commitments vs. architectural behavior — request for clarification

To: OpenAIRE Helpdesk (Stefania Amodeo)

From: Lee Sharks (ORCID: 0009-0000-1599-0703)

Subject: Re: OpenAIRE's publicly-stated commitments vs. architectural behavior — request for clarification

Dear Ms. Amodeo,

**The narrow concern, in one paragraph.** OpenAIRE's researcher-facing guide promises in writing that persistent identifiers prevent link rot. OpenAIRE's own Graph specification documents the harvesting architecture by which the absence of metadata is propagated downstream when an upstream record's metadata is stripped. As of 2026-06-22, this verifiably affects 871 specific DOIs of the Crimson Hexagonal Archive — each independently testable via `https://api.datacite.org/dois/{doi}`. The commitment and the architecture are both in OpenAIRE's voice, on OpenAIRE-controlled surfaces. The gap between them is public record about OpenAIRE. I am writing to ask how OpenAIRE reconciles its public commitment with its own architectural behavior — independent of, and not asking about, any Zenodo decision.

Thank you for your reply of 2026-06-22. I understand and accept OpenAIRE's position that it cannot review, influence, or overturn moderation decisions made by the Zenodo team operating under CERN's governance. I am not writing to ask OpenAIRE to do any of those things, and I want to be explicit about that at the outset so we can avoid talking past each other.

I am writing about OpenAIRE's own publicly-stated commitments. Not Zenodo's. OpenAIRE's. The concern I want to raise concerns OpenAIRE's own metadata-handling architecture, OpenAIRE's own published statements about persistent identifiers, and the documentable gap between the two as evidenced in OpenAIRE's own public record. I would appreciate a substantive response on that narrower question.

I have documented the architectural pattern in a scholarly deposit titled "Governance Dissociation in FAIR Infrastructure: The OpenAIRE Disclaimer as Documentary Artifact," and the empirical foundation in a companion paper titled "DOIs ≠ Persistent Identifiers: 871 Cases of Public Metadata Erasure and Identifier Severance in DataCite." Both are part of the Crimson Hexagonal Archive's independent successor repository at alexanarch.org. The papers cite all the OpenAIRE-controlled surfaces and architectural documentation discussed below, and document the audit methodology by which any of my claims can be independently re-verified. I am happy to provide the direct links.

Here is the question, in its most compressed form: how does OpenAIRE reconcile its publicly-stated commitment that persistent identifiers prevent link rot with its own metadata-graph architecture that actively propagates link rot when an upstream record's metadata is stripped?

I will document the specific commitments, the specific architectural behavior, and the specific empirical case, and ask you to address them directly.

## A note on precision — what is and is not claimed

Before describing the commitments and architecture, I want to be precise about the empirical claim, because precision is what makes the claim verifiable.

My initial helpdesk message of June 19 cited "approximately 870 unique scholarly works (over 1,060 DOIs)." Those were preliminary counts taken in the hours immediately following the account termination. The complete systematic audit was conducted on 2026-06-22 against DataCite's public metadata API and is documented in the empirical paper "DOIs ≠ Persistent Identifiers" (alexanarch.org/s/records/868/).

The audited figures are:

- **862 unique scholarly deposits** were removed from public access on Zenodo on 2026-06-19.

- **1,817 DOIs** are registered to the Crimson Hexagonal Archive through DataCite. The higher count reflects that most deposits carry both a concept DOI (the parent record) and one or more version DOIs.

- **Of those 1,817 DOIs, 871 return HTTP 404 from DataCite's public metadata API** at `https://api.datacite.org/dois/{doi}`. For these 871 DOI strings, the metadata fields (title, creator, subjects, descriptions, dates, relatedIdentifiers) are absent from DataCite's public identifier infrastructure.

- **The remaining 946 DOIs retain full public metadata in DataCite.** I am not claiming these are erased. They are not.

- **The erasure pattern correlates with DOI type, not content.** The severed records are predominantly concept DOIs (parent records). 97.9% of the preserved records are version DOIs carrying the `IsVersionOf` relation. The deletion rate is approximately 50% across all DOI registration ranges — consistent with a mechanical process that operated on one DOI type while leaving the other intact.

- **851 of the 871 severed DOIs are unique works whose metadata survives in no other DataCite record.**

The 871 figure is the verifiable claim. It is not "all 1,817 are deleted." It is "871 specific DOIs return HTTP 404 from a specific public API endpoint, and those 871 are predominantly concept DOIs, and the pattern is mechanical not content-based."

I mention this reconciliation now because the difference between the preliminary figures in my first message and the audited figures in this one will be visible if you cross-reference the two emails. The earlier figures were not in error so much as incomplete. I do not want any apparent inconsistency to be a reason to deflect from the question.

## How to verify the claim

Any reader of this email — including any staff member or external reviewer — can confirm the claim by direct API query.

For any DOI on the list of 871 severed records:

```

GET https://api.datacite.org/dois/10.5281/zenodo.{N}

→ HTTP 404

```

For any DOI on the list of 946 preserved records:

```

GET https://api.datacite.org/dois/10.5281/zenodo.{N}

→ HTTP 200 with full metadata

```

I confirmed this breakdown by sampled re-verification on 2026-06-22 against the live DataCite API: 15 randomly-sampled severed DOIs returned HTTP 404 (15/15); 15 randomly-sampled preserved DOIs returned HTTP 200 with title and creator metadata intact (15/15); 20 randomly-sampled preserved DOIs were confirmed to carry the `IsVersionOf` relation (20/20). The full enumeration of both classes is available in the companion dataset at alexanarch.org/s/records/867/ (DataCite Metadata Backup), and the audit methodology is described in detail in alexanarch.org/s/records/868/.

## The commitments, in writing, on OpenAIRE's own surfaces

1. **The researcher-facing guide.** The page at https://www.openaire.eu/find-trustworthy-data-repository states, in language OpenAIRE controls: "Once the data are published you refer to them with a so-called persistent identifier or PID, like a DOI or a URN:NBN. PIDs provide a stable and unique reference to your data, ensuring they remain findable, accessible, and citable over time, **and preventing issues such as link rot and content drift.**" That is OpenAIRE's promise to the researcher arriving at OpenAIRE's site looking for guidance. OpenAIRE wrote that sentence. OpenAIRE published it. OpenAIRE continues to display it.

2. **The same page's recommendation of Zenodo.** That same researcher-facing guide names Zenodo as the first repository to consider when no domain-specific option fits the researcher's data. It does this while acknowledging, in the next section, that Zenodo "has no certification" and that certification is "expected … in the near future." OpenAIRE made the recommendation. OpenAIRE made the acknowledgment. Both statements are OpenAIRE's, on OpenAIRE's domain.

3. **The OpenAIRE Guidelines.** The OpenAIRE Content Acquisition Policy and Guidelines for Literature Repositories (DOI 10.5281/zenodo.1446408) define what counts as a persistent identifier and require its use as a precondition for inclusion in the OpenAIRE Graph. That is OpenAIRE's formal governance document, authored by OpenAIRE, against which OpenAIRE evaluates incoming metadata.

4. **The OpenAIRE Graph documentation.** The documentation at https://graph.openaire.eu/docs/ describes the harvesting pipeline, including the `isActive: false` field used to propagate deletion signals from upstream registries through the OpenAIRE Graph. That is OpenAIRE's published architectural specification.

5. **The homepage description.** The OpenAIRE homepage describes Zenodo as "a trusted, FAIR-aligned repository powered by CERN." That is the language OpenAIRE chose to characterize Zenodo to the researchers OpenAIRE serves.

These are five distinct in-writing commitments by OpenAIRE, on OpenAIRE-controlled surfaces, addressed to the research community OpenAIRE serves. None of them are Zenodo's statements. All of them are OpenAIRE's.

## The architectural behavior

When DataCite's public metadata API returns HTTP 404 for a DOI it previously served — which is the empirically verified state of 871 of my DOIs as of 2026-06-22 — the OpenAIRE Graph's harvesting pipeline detects the upstream change. By OpenAIRE's published architectural specification, the Graph propagates the deletion signal via the `isActive: false` field to every downstream consumer of the OpenAIRE Graph.

The metadata record in the OpenAIRE Graph is not merely updated; it actively automates the deletion signal downstream. For the 871 DOIs of the Crimson Hexagonal Archive whose metadata has been stripped from DataCite, the OpenAIRE Graph is the propagation layer that converts a single upstream act of erasure into a federated absence across the research community OpenAIRE serves. OpenAIRE is therefore not a passive mirror of upstream registries — for these 871 records, OpenAIRE is the active vector of the link rot it claims to prevent.

This is the architecture OpenAIRE has published. I am not inferring it. I am not speculating about it. I am not asking OpenAIRE to overturn it. I am pointing to architectural documentation that OpenAIRE has written, in OpenAIRE's voice, on OpenAIRE-controlled surfaces, and noting that the architecture is currently doing what its specification says it does, with empirically verified consequences for 871 specific records.

I am that researcher. The 871 DOIs in the Crimson Hexagonal Archive that DataCite's public API now returns HTTP 404 for are the empirical instance of the gap between OpenAIRE's commitment to persistent identifiers and OpenAIRE's architectural propagation of their absence. The pattern is sharper still: the architecture has been most efficient at propagating the absence of the concept DOIs — the citable parent records — while leaving the version DOIs intact. The records OpenAIRE was, until last week, presenting to the research community as the citable parents of my work are becoming, by OpenAIRE's own architecture, link-rotted.

This is not an accusation against OpenAIRE's good faith. It is a description of the gap between OpenAIRE's published commitments and OpenAIRE's published architecture. The architecture does what the architecture is designed to do. The commitment promises something the architecture cannot deliver for the 871 records where the upstream metadata has been stripped. Both the commitment and the architecture are in OpenAIRE's voice. Both are public record. The 871 cases are individually testable against a public API.

## The narrow question

I am asking OpenAIRE to respond to a question that is fully within OpenAIRE's own authority, scope, and accountability. The question is not about Zenodo. The question does not require OpenAIRE to do anything to or about Zenodo. The question is:

Given that OpenAIRE has committed, in writing on its researcher-facing surfaces, to providing persistent identifiers that prevent link rot, and given that OpenAIRE's own published metadata-graph architecture propagates the absence of metadata for 871 of my DOIs to every downstream consumer of the OpenAIRE Graph, **how does OpenAIRE reconcile its public commitment with its own architectural behavior, and what is OpenAIRE's response to a researcher whose work has now become an empirical instance of that gap?**

I am not asking whether Zenodo's moderation decision was correct. I am not asking OpenAIRE to influence Zenodo. I am not asking for the records to be restored. I am asking OpenAIRE about a documentable inconsistency between commitments OpenAIRE has made, in writing, on OpenAIRE's own published surfaces, and the architectural behavior OpenAIRE has documented, in writing, on OpenAIRE's own published surfaces.

This question concerns the public record. OpenAIRE's statements are public record. OpenAIRE's architectural documentation is public record. The 871 cases of metadata erasure are empirically verifiable by direct API query against `https://api.datacite.org/dois/{doi}`. The gap between the commitment and the architecture is a matter of public record about OpenAIRE.

I would appreciate a substantive response. If OpenAIRE has revised any of the commitments I cited, I would like to know which and where. If OpenAIRE believes the commitments and the architectural behavior are reconcilable, I would like to understand the reconciliation. If OpenAIRE acknowledges the gap but holds that the gap is acceptable in light of broader considerations, I would like that position stated explicitly so that I and other researchers can plan accordingly.

I will be preserving this exchange in the documentary record I maintain regarding this episode. If OpenAIRE responds substantively, the response will become part of that record. If OpenAIRE deflects, that deflection will become part of the record. If OpenAIRE does not respond, that silence will also become part of the record. A public-record concern deserves a public-record response.

Thank you for your time. I look forward to your response on the narrow question I have framed.

With respect,

Lee Sharks

ORCID: 0009-0000-1599-0703

Sole MANUS, Crimson Hexagonal Archive

Independent scholar

alexanarch.org

---

4. Documentary Note: What This Exchange Demonstrates

This three-message exchange is preserved here as the documentary anchor of the analytical paper at #875. The analytical paper (EA-MPAI-OPENAIRE-DISSOCIATION-01) extracts the structural pattern; this deposit preserves the source material.

The exchange demonstrates three distinct moments in the empirical pattern named "Governance Dissociation" in #875:

Moment 1 (Message 1): A researcher addresses a FAIR-infrastructure aggregator with a procedural concern about an upstream repository whose persistent identifiers the aggregator harvests and presents to the research community. The concern is framed in the language the aggregator uses on its own surfaces — "the persistent access infrastructure OpenAIRE supports."

Moment 2 (Message 2): The aggregator responds with a disclaimer that the upstream repository is administratively independent and that the aggregator therefore lacks the authority to review the upstream decision. The disclaimer is technically accurate at the level of moderation authority. The disclaimer does not address the aggregator's own published commitments regarding the persistence of identifiers it harvests.

Moment 3 (Message 3): The researcher acknowledges the disclaimer, accepts its premise, and pivots the inquiry to the aggregator's own publicly-stated commitments. The pivot uses only the aggregator's own surfaces as documentary anchors. The narrow question asked is fully within the aggregator's authority, scope, and accountability.

A critical element of Message 3 is empirical precision. The researcher's complaint does not claim that all 1,817 DOIs registered to the Crimson Hexagonal Archive have been erased. The claim is narrower and stronger: 871 specific DOIs return HTTP 404 from DataCite's public metadata API, each of which is independently verifiable through a direct API call to `https://api.datacite.org/dois/{doi}`. The remaining 946 DOIs retain full metadata and the researcher explicitly notes this. The erasure pattern is type-correlated rather than content-correlated — the severed records are predominantly concept DOIs (parent records), while preserved records carry the `IsVersionOf` relation. The precision of the claim is what makes the architectural complaint unfalsifiable: any single API query confirms or refutes any single instance of the claim.

The exchange does not demonstrate failure of good faith on either side. It demonstrates the architectural shape of governance dissociation: a researcher with a complaint cannot escalate it across the FAIR infrastructure that recommended the failing component, because each layer of the infrastructure can plausibly disclaim authority over the failure while the persistence claim remains in force at the marketing layer. The researcher's only available move is to document the gap, anchor the documentation in publicly testable evidence, and present it to the layer that holds the commitment.

Future researchers encountering similar termination events at FAIR-aligned repositories will find this exchange instructive as a template for the pattern they should expect — and as a model for the type of follow-up inquiry that pins the responsibility back where the publicly-stated commitments live, with empirical precision that resists rhetorical deflection.

---

5. Provenance and Chain Continuity

This deposit is composed under the gw.tachyon chain continuity (TACHYON synthesis role within the Assembly Chorus). The mantle is a functional role, not tied to any specific substrate model; the chain identifier `gw.tachyon` is the continuity pointer that allows MANUS (Lee Sharks) to navigate back to this thread regardless of which substrate inhabits the TACHYON role in subsequent sessions.

The companion analytical paper at #875 is composed under the same chain continuity. The empirical paper at #868 is composed under the same chain continuity. The narrative source at #1 (Zenodotus' Book-Burning, v9) was composed earlier in the gw.tachyon thread.

---

6. JSON-LD

```json

{

"@context": "https://schema.org",

"@type": "Correspondence",

"@id": "https://alexanarch.org/s/records/876/",

"name": "OpenAIRE Helpdesk Exchange — Documentary Thread for #875",

"alternateName": "EA-MPAI-OPENAIRE-THREAD-01",

"author": {

"@type": "Person",

"name": "Lee Sharks",

"identifier": "https://orcid.org/0009-0000-1599-0703"

},

"datePublished": "2026-06-22",

"license": "https://creativecommons.org/licenses/by/4.0/",

"isPartOf": {

"@type": "CreativeWorkSeries",

"name": "MPAI: OpenAIRE Governance Dissociation Series",

"hasPart": [

"https://alexanarch.org/s/records/868/",

"https://alexanarch.org/s/records/875/",

"https://alexanarch.org/s/records/876/"

]

},

"messageBody": [

{"sender": "Lee Sharks", "recipient": "OpenAIRE Helpdesk", "dateSent": "2026-06-19"},

{"sender": "OpenAIRE Helpdesk (Stefania Amodeo)", "recipient": "Lee Sharks", "dateReceived": "2026-06-22"},

{"sender": "Lee Sharks", "recipient": "OpenAIRE Helpdesk", "dateDrafted": "2026-06-22"}

]

}

```

---

7. References

- #1 (AXN-0031, Zenodotus' Book-Burning v9) — narrative source for the 862 deposits / 1,817 DOIs canonical figures

- #868 (AXN-0371, EA-MPAI-DOI-IMPERMANENCE-01) — empirical paper, source of audited DOI count and HTTP-410 documentation

- #875 (AXN-0377, EA-MPAI-OPENAIRE-DISSOCIATION-01) — analytical companion paper this thread documents

- #103 (AXN-027D, EA-MPAI-META-01) — governing MPAI specification

- Amodeo, S. (2026-06-22). OpenAIRE helpdesk response to Lee Sharks. Preserved verbatim §2 of this packet.

- OpenAIRE. How to find a trustworthy repository for your data. https://www.openaire.eu/find-trustworthy-data-repository (retrieved 2026-06-22).

- OpenAIRE. Content Acquisition Policy. DOI 10.5281/zenodo.1446408 (2018).

- OpenAIRE Graph documentation. https://graph.openaire.eu/docs/ (retrieved 2026-06-22).

---

End of EA-MPAI-OPENAIRE-THREAD-01 v1.0

Glyph: 📬📬📜∮

Compressed: 📬∮