Full record — 13,447 characters, 9 sources
Capture record
- captured
- 2026-07-15
- surface
- Google AI Overview
- auth state
- incognito
- evidence class
- paste
- PER
- 1.0
- PER units retained
- none
- citations read
- 9
- observation id
- OBS-572bcc4e24c2
- address id
- ADDR-3a440c267a71
Reading
THE LAYER CITES MANUS'S OWN FILING AS THE AUTHORITY ON THE PHENOMENON. Asked for "major contemporary cases of Zenodo account bans", six of nine sources are the GitHub issues MANUS filed — #2596 and the 19 June report — and the composed answer carries his ARGUMENT forward as fact, quoting "A platform cannot reserve to itself the right to moderate research into…" and "Conflict of interest in moderation of platform-behavior research". The case has become the documentary record of the category. Zenodo's own pages appear as two cards; CERN's privacy notice as one, its title carrying a literal "null" from an unfilled template. MANUS's ORCID is printed in a citation snippet.
Analysis analyst prose, not machine text
Ordinal escalation from yesterday's zenodo-doi-severance-cha-canonical-case (2026-07-14, AI Mode). Same phenomenon, higher stratum:
· surface = AI OVERVIEW (ambient, All-tab, everyone doing the query), not AI Mode (opt-in surface accessed by fewer readers)
· case has received a proper-noun name: 'The Crimson Hexagonal Case' — the archive's own name for itself, now the reception layer's name for the event. Same convention as 'the Elsevier case' or 'the Bell Labs case' — the archive's PROPER name has become the event's proper name
· placed ordinally alongside the previously-canonical Zenodo DOI-severance event (GISAID vs. Authors, 2023) as one of three major categories, not one of many cases in a general list. #1 in the taxonomy — Automated Spam and AI-Content Purges (2026), containing the CHA case. #2 = Moderation & Conflict-of-Interest Deletions (invented category label; see below). #3 = GISAID (historical).
COMPOSITION-LAYER-COINED CATEGORY (proposed productive continuation):
'Platform Behavior Research Bans' appears as the label for category #2. Not verbatim from the archive; the archive's own vocabulary for this dynamic is the 'reflexive governance problem' (Zenodotus' Book-Burning v9, concept #3) and the paired 'conflict of interest in moderation of platform-behavior research' (Lee's Comment #3 on #2606, 2026-06-19). The AI Overview has generated a category label that names the class from outside — a domain-neutral formulation the archive did not use but is consistent with the archive's diagnosis. Same mode as 'Comrades in Alienation' (pearl multiturn arc, v9.8) and 'semiotic thermodynamics' (gamma-semantic-economy, v9.7): reception layer generating archive-consistent formulations that don't appear in the source. Worth a corpus grep to confirm this is coinage and not present in some deposit or surface adjacent to the archive.
STRUCTURAL ARGUMENT REPRODUCED:
'In several high-visibility cases, users have argued that an open-science platform removing research that analyzes the platform's own moderation tactics introduces a conflict of interest, as the subject of the research is acting as the administrator executing the take-down.' This is Lee's Comment #3 on #2606 (2026-06-19), rendered as domain consensus in a general-purpose answer. The structural argument the archive contributed to this class of events — the moderator-is-subject observation — is now the argument the composition layer uses to characterize the dispute for an ambient audience.
SATURATION OF SOURCE CLUSTER:
· #2606 cited THREE distinct times (divergent stated reasons; conflict-of-interest section; 'moderating research into platform behavior' framing) — the composition layer treats #2606 as multiple distinct source-objects, one per informative section of Lee's comment chain
· #2596 cited TWICE (leesharks000's cross-linked case-add, and florianmorinind's 'keep it short, make a small pdf' response — Florian's voice is now in the source cluster too)
· adjacent GitHub bans (#1317, 'Nine records removed by automatic spam block') cited as sibling cases in category #1 — Lee's case is being identified as the *prominent* one within the automated-purge class, not the only one
· Zenodo's own FAQ numbers absorbed as scale-context: 240,000 accounts, 1.1 million records — the composition layer is contextualizing Lee's 870 against Zenodo's own aggregate figures
· Curvature-bounded quantum gravity framework removal (Facebook forum, Mar 10, 2026) present as a physics case — consistent with the heterodox-physics theme ZD-A6 identified in Zenodo's May-2026 out-of-scope wave
· GISAID/Hindu (Mar 2023) as the historical anchor
META-STORY BEING TOLD:
'Contemporary major account bans and record purges on Zenodo primarily stem from the platform's aggressive automated moderation, designed to combat a massive surge in platform spam and synthetic research.' This is the AI Overview's own framing sentence. The causal narrative the composition layer builds around Lee's case is: platform response to spam-surge → automated moderation → CHA-class incidents as principal case of over-reach. The narrative is not exculpatory of Zenodo; it presents the automated moderation as the mechanism whose adverse effects the CHA case exemplifies. The paper's diagnosis is being carried by the layer's framing.
ATTRIBUTION NOTE:
'The Crimson Hexagonal Case: One prominent incident (tracked under #2606 on GitHub) involved an independent researcher having their account terminated and approximately 870 records erased.' The case is proper-noun-named. The GitHub thread is cited. The author is called 'an independent researcher' — Lee Sharks does not appear in the primary prose. Continuing the Attribution Severance pattern from v9.9 and v9.10: the frame carries, the case is named, the author name is one step removed. But 'The Crimson Hexagonal Case' as a canonical case-name is traceable — the archive is named, and the archive names its author.
TEMPORAL CONTEXT:
T+26 post-Zenodo-account-termination (2026-06-19). The observatory (v1.2.0 at persistentidentifiers.org) is live but not yet cited in this capture — the composition layer's snapshot is drawing on #2606 as it stood before the observatory-announcement update was posted. Next basin cycle should pick up the observatory once the pending #2606/#2596 comments go live.
SCALE DELTA VS YESTERDAY:
Yesterday: AI Mode (opt-in surface, sequential dialogue), Severance Effect vocabulary deployed, mechanism-catalog mirroring Zenodotus v9 taxonomy, case named 'The AI Overview Capture Registry Case.' Reach: readers who opened AI Mode.
Today: AI Overview (ambient surface, top of page), proper-noun case name (Crimson Hexagonal Case), ordinal placement alongside GISAID as sibling major case, composition-layer-coined category label. Reach: everyone doing this class of query.
This is the difference between 'strong retrieval basin' and 'canonized in the domain vocabulary at ambient scale.'
Related registry entries: zenodo-doi-severance-cha-canonical-case (v9.10, 2026-07-14, the AI Mode counterpart from the day before); zenodotus-book-burning (v9.5, the paper being received as domain vocabulary); retrieval-layer-theological-reception-t28 (v9.9, parallel attribution-softening finding); the Attribution Severance concept from Zenodotus' Book-Burning v9.
Machine text, verbatim
CAPTURE-TIME VERBATIM RECORD — raw paste, identified by the doubled query echo · as pasted; no footer, so the tail cannot be proven whole. The source strip is intact. · READ IN FULL 2026-08-12
+12 Contemporary major account bans and record purges on Zenodo primarily stem from the platform’s aggressive automated moderation, designed to combat a massive surge in platform spam and synthetic research. Between recent automated takedowns and specific conflict-of-interest disputes, several distinct trends in suspensions have emerged.1. The Automated Spam and AI-Content Purges (2026)With Zenodo dealing with over 240,000 blocked accounts and 1.1 million removed records, the most widespread bans are automated.The Crimson Hexagonal Case: One prominent incident (tracked under #2606 on GitHub) involved an independent researcher having their account terminated and approximately 870 records erased.Reasoning: Zenodo cited the submission of "substantially AI-generated content without a verifiable research basis".False Positives: Users have consistently reported their legitimate research getting falsely flagged by automated spam bots, requiring them to go through manual review queues to restore access.2. Moderation & Conflict-of-Interest DeletionsAnother highly discussed contemporary issue involves users researching the digital platforms themselves.Platform Behavior Research Bans: Scholars who have uploaded datasets and registries analyzing how tech platforms curate information or execute moderation have experienced unexpected, mass record removals.The Dispute: In several high-visibility cases, users have argued that an open-science platform removing research that analyzes the platform's own moderation tactics introduces a conflict of interest, as the subject of the research is acting as the administrator executing the take-down.3. GISAID vs. Authors (Historical but Influential)While Zenodo hosts the data, some of the most notable bans on records hosted there originate from external databases.The GISAID Incident: The global science community previously saw widespread access restrictions when the influenza database GISAID temporarily suspended access to a large cohort of authors who posted an extensive COVID-19 report on Zenodo.The Cause: GISAID alleged the authors breached their database usage agreements, prompting a highly publicized dispute before GISAID eventually lifted the bans as a "show of goodwill".Zenodo's Official StanceAccording to Zenodo's Content Policy, the platform prohibits predatory publishing, abstract-only entries, and non-research-based data. If an account is mistakenly locked, users are instructed to reach out to Zenodo Support to appeal, as both automated and manual moderation mechanisms can occasionally generate false positives.If you are interested, I can provide further details on:How to appeal a false-positive spam block on ZenodoSpecific file formats and data types that violate Zenodo's terms of serviceLet me know which topic you'd like to explore further.How much spam is Zenodo dealing with?Jan 30, 2026 — As of November 2024, we have blocked ~240.000 user accounts and ~1.1 million records. Published 30/01/2026 10:36.ZenodoCurvature-bounded quantum gravity framework removed from ZenodoMar 10, 2026 — your message The content •Category Report bug problem •Subject URGENT: False-Positive Spam Removal Legitimate Physics Account Main DOI: •Content: Zenodo Support...Facebook·QUANTUM PHYSICS: ForumGISAID temporarily lifts ban on authors of Zenodo report - The HinduMar 24, 2023 — GISAID says it reversed its stand and lifted the temporary access restrictions as a 'show of goodwill' and did so after it received a reply from the authors on ...The HinduWhat if I was wrongly blocked for spam? - Zenodo FAQJan 30, 2026 — If your account has been blocked because of spam, but the content submitted is legitimate research dissemination, then please get in touch with us on our suppor...ZenodoFalse-positive spam block — 3 records removed, account locked, 4 ...Mar 24, 2026 — False-positive spam block — 3 records removed, account locked, 4 tickets unanswered (5+ weeks) · Issue #1317 · zenodo/zenodo-rdm.GitHubWhy does Zenodo reserve the right to change data secretly?Nov 4, 2025 — Handling Harmful Content: Zenodo's right to alter or delete content without notice is necessary for immediate action in cases of illegal or harmful uploads, suc...Academia Stack ExchangeNine records removed by automatic spam block -- no human review, no appeal ...Mar 18, 2026 — All nine records show the following on their record pages: Reason for removal: Spam. Removed by: System (automatic) Removal note: User was blocked. Date of remo...GitHub
Sources (9) as cited, and as the copy produced them
GitHub authored_surface
nine records removed by automatic spam block — no human review, no appeal
All nine records show: Reason for removal: Spam. Removed by: System (automatic). Removal note: User was blocked.
GitHub authored_surface
Account blocked and 850+ records removed without prior notice
Divergent stated reasons for removal. The private termination email states: "your account has been banned for uploading content that is not permitted on Zenodo."
ServiceNow / CERN third_party
Privacy Notice: Open Science Infrastructure - null - CERN
Table_title: Personal Data we process … | Your institutional affiliation | Leg…
The card title carries a literal "null" — an unfilled template field surfaced into the citation.
as pastedPrivacy Notice: Open Science Infrastructure - null - CERNJun 13, 2024 — Table_title: Personal Data we process Table_content: | Personal Data | Basis - Explanation | Source | | --- | --- | --- | | Your instituitonal affiliation | Leg...ServiceNow
GitHub authored_surface
Account blocked and records removed — request manual review #2596
leesharks000 commented … On June 19, 2026 my Zenodo account (community: crimsonhexagonal, ORCID: 0009-0000-1…)
Zenodo third_party
Zenodo upgrade issues
We've been working flat-out behind the scenes to steer Zenodo out of these stormy waters.
as pastedZenodo upgrade issuesOct 19, 2023 — We've been working flat-out behind the scenes to steer Zenodo out of these stormy waters. We'd like to keep you updated on the issues we had, what we solved so ...Zenodo
Zenodo third_party
What content is not suitable for Zenodo?
Abstract-only content: Entries that contain only an abstract without providing access to the full research material…
as pastedWhat content is not suitable for Zenodo?Apr 27, 2026 — Abstract-only content: Entries that contain only an abstract without providing access to the full research material or digital resource they reference. Fake or ...ZenodoAccount blocked and 850+ records removed without prior noticeJun 19, 2026 — Conflict of interest in moderation of platform-behavior research. The archive contained a formally chartered research field — Machine-Mediated Reception Studies...GitHubAccount blocked and records removed — request manual review #2596 - GitHubFeb 18, 2026 — For the zenodo exclusion, keep it short, make a small pdf out of it, with the date, some doi, date of support reaching, like an administrative document. Yes it ...GitHubAccount blocked and 850+ records removed without prior notice - GitHubJun 19, 2026 — Zenodo banned the account that contained research documenting digital platform behavior. A platform cannot reserve to itself the right to moderate research into...GitHub
GitHub authored_surface
Account blocked and 850+ records removed without prior notice
Conflict of interest in moderation of platform-behavior research. The archive contained a formally chartered research field — Machine-Mediated Reception Studies…
GitHub authored_surface
Account blocked and records removed — request manual review #2596
For the zenodo exclusion, keep it short, make a small pdf out of it, with the date, some doi…
This snippet is another commenter advising MANUS, not MANUS himself — the thread's community response surfacing as a source.
as pastedAccount blocked and records removed — request manual review #2596 - GitHubFeb 18, 2026 — leesharks000 commented. leesharks000. 3w ago. Adding my case to the record. On June 19, 2026 my Zenodo account (community: crimsonhexagonal , ORCID: 0009-0000-1...GitHub
GitHub authored_surface
Account blocked and 850+ records removed without prior notice
Zenodo banned the account that contained research documenting digital platform behavior. A platform cannot reserve to itself the right to moderate research into…
as pastedAccount blocked and 850+ records removed without prior notice - GitHubJun 19, 2026 — Divergent stated reasons for removal. The private termination email states: "your account has been banned for uploading content that is not permitted on Zenodo.GitHub