{
 "spxi_instrument": {
  "method": "0.9",
  "name": "Capture Registry (longitudinal observation)",
  "level": 0,
  "level_name": "Measurement",
  "url": "https://www.spxi.dev/methods/#m-0-9",
  "inventory": "https://www.spxi.dev/methods/",
  "statement": "SPXI instrument: method 0.9 of 85, level 0 (Measurement), Capture Registry (longitudinal observation).",
  "also": []
 },
 "slug": "persistent-identifier-erosion-observatory-aio-20261014",
 "date": "2026-10-14",
 "surface": "Google AI Overview",
 "surface_basis": "Surface not stated; the standing default applies (operator, 2026-10-01: 'assume they do [start in overview], i will specify if they begin in ai mode'). The 'AI Mode Conversation' header is the expanded Overview's residue (rule of 2026-09-21).",
 "surfaces": [
  "Google AI Overview"
 ],
 "auth": "incognito, signed out",
 "auth_basis": "'signed out incognito both' — operator, 2026-10-14 15:02 EDT.",
 "ev": "paste",
 "mt": "BOTH NAMES HELD, THE OPERATOR NAMED, CASE 001 MOVED TO ZENODO",
 "match": "BROAD MATCH",
 "match_note": null,
 "s": "Platform Erosion",
 "q": "persistent identifier erosion observatory",
 "q_kind": "the observatory's name spelled out, without the article or a question. NEW address.",
 "cites": 7,
 "cite_list": [
  {
   "n": 1,
   "site": "www.persistentidentifiers.org",
   "rel": "authored_surface",
   "title": "Persistent Identifiers — The PID Erosion Observatory",
   "snip": null,
   "url": null,
   "note": "the observatory's own page"
  },
  {
   "n": 2,
   "site": "www.alexanarch.org",
   "rel": "archive_controlled",
   "title": "The Platform Erosion Observatory: The Zenodo Removal Census as ...",
   "snip": null,
   "url": null,
   "note": "#1045's wiki article",
   "deposit": 1045,
   "deposit_basis": "title"
  },
  {
   "n": 3,
   "site": "GitHub",
   "rel": "third_party",
   "title": "persistent-identifiers · GitHub Topics",
   "snip": null,
   "url": null,
   "note": "GitHub's persistent-identifiers topic, listing the observatory's repository"
  },
  {
   "n": 4,
   "site": "www.alexanarch.org",
   "rel": "archive_controlled",
   "title": "platform erosion observatory — Google AI Overview, 2026-08-11 ...",
   "snip": null,
   "url": null,
   "note": "the Capture Registry's own record of 2026-08-11 at 'platform erosion observatory'"
  },
  {
   "n": 5,
   "site": "github.com",
   "rel": "authored_surface",
   "title": "GitHub - leesharks000/platform-erosion-observatory: Platform ...",
   "snip": null,
   "url": null,
   "note": "the observatory's repository"
  },
  {
   "n": 6,
   "site": "www.axnidentifiers.com",
   "rel": "authored_surface",
   "title": "Why AXN exists — identifier erosion, measured at registry scale",
   "snip": null,
   "url": null,
   "note": "axnidentifiers.com, 'Why AXN exists'"
  },
  {
   "n": 7,
   "site": "medium.com",
   "rel": "authored_surface",
   "title": "THE OBELUS AND THE TOMBSTONE: On the Two Marks of ...",
   "snip": null,
   "url": null,
   "note": "THE OBELUS AND THE TOMBSTONE (#1068), on Medium",
   "deposit": 1068,
   "deposit_basis": "title"
  }
 ],
 "archive_controlled_cites": 2,
 "transcript": "[Google AI Overview (expanded), 2026-10-14, incognito, signed out. The paste carries the header 'AI Mode Conversation' and echoes the query twice; citation clusters are reduced to their numbers, links to their text; the raw paste keeps the /goto URLs.]\n\nYou said: persistent identifier erosion observatory\nThe Platform Erosion Observatory (also known as the PID Erosion Observatory) is an empirical research initiative and framework designed to measure whether persistent identifiers (PIDs)—such as DOIs—actually persist, and to study what happens when scholarly digital objects are removed from institutional or data repositories. [1, 2, 3]\nThe project addresses the reality that PIDs are not permanent strings, but rather maintained relations that are susceptible to \"erosion\" or deletion over time. [1]\nCore Focus & Instruments\n\n* Measuring \"Custody Separation\": The observatory tracks the actual population of platform-driven scholarly record removals. It evaluates how platforms handle metadata after a deletion occurs, specifically evaluating \"tombstone\" compliance rates (whether a placeholder remains) and the \"shape of absence\". [1, 2, 3]\n* The Zenodo Removal Census: Acting as its primary case study instrument (Case 001), it tracks a specific cohort of over 14,000 DOIs to establish a baseline analysis of how, why, and when records vanish from the Zenodo repository. [1, 2]\n* Cross-Platform Tracking: It outlines a forward roadmap to extend this tracking across multiple major scholarly platforms to map structural enforcement actions and account-level deletions. [1]\n\nKey Ecosystem Concepts\nThe project is part of a broader, sovereign alternative tracking architecture spearheaded by researcher Lee Sharks. It acts as the research counterpart to infrastructure initiatives, which include: [1]\n\n* The Severance Registry / Resolution Index: A system designed to map severed identifiers and resolve them outside of the primary platform's control. [1, 2]\n* The Capture Registry: An engine designed to capture asymmetry in how corrections and representation changes are documented across repositories. [1]\n\nFor open-source code and dataset specifics, you can view the project directly on the Platform Erosion Observatory GitHub Repository. [1]\nIf you'd like to dive deeper, let me know if you want to explore:\n\n* The methodology behind the Zenodo Removal Census\n* What tombstone compliance rates reveal about repository permanence\n* How a Resolution Index handles severed identifiers\n\nwww.persistentidentifiers.org\nPersistent Identifiers — The PID Erosion Observatory\nWhat is a persistent identifier? A string whose relation to its object is maintained indefinitely by a responsible organization — resolution, metadata, and ...\nwww.alexanarch.org\nThe Platform Erosion Observatory: The Zenodo Removal Census as ...\nJul 6, 2026 — Wiki Article 0 — The Platform Erosion Observatory: The Zenodo Removal Census as First Instrument, and the Plan for a Broader Cross-Platform Tracker is a empiric...\nGitHub\npersistent-identifiers · GitHub Topics\nDec 31, 2024 — Platform Erosion Observatory — empirical instrument for measuring what happens to scholarly records after removal: survival in aggregators, tombstone behaviour,\nwww.alexanarch.org\nplatform erosion observatory — Google AI Overview, 2026-08-11 ...\nAug 11, 2026 — Core Focus Areas render identifier custody, removal censuses, and ... as pastedPersistent Identifiers — The PID Erosion Observatory Persistent Identifiers ...\ngithub.com\nGitHub - leesharks000/platform-erosion-observatory: Platform ...\nThe Platform Erosion Observatory. Measuring whether persistent identifiers persist. Public face of EA-EROSION-01 (deposit #1045, AXN:0421.EMPIRICAL ...\nwww.axnidentifiers.com\nWhy AXN exists — identifier erosion, measured at registry scale\nmeasured by the PID Erosion Observatory · dated captures preserved. A persistent identifier is a maintained relation, not a string. When the maintenance ...\nmedium.com\nTHE OBELUS AND THE TOMBSTONE: On the Two Marks of ...\nJul 11, 2026 — ... Erosion Observatory; 1,838 severed identifiers resolving through the sovereign Resolution Index; the reception layer's confusions documented capture by ...",
 "transcript_raw": "AI Mode Conversation\nYou said: persistent identifier erosion observatorypersistent identifier erosion observatory\nThe Platform Erosion Observatory (also known as the PID Erosion Observatory) is an empirical research initiative and framework designed to measure whether persistent identifiers (PIDs)—such as DOIs—actually persist, and to study what happens when scholarly digital objects are removed from institutional or data repositories. [[1](https://www.google.com/goto?url=CAESgAEB6zswFScJ6-IUs9ZGf6J_qcSLMueYILo1ifUGvTtCZ0srmgxcQsH92fbO_6cM2TzXaze5mTgpiBhSi1DMZnbAg73awgnsV_6H2ZDntNpVfDx85HE8zit6sWdiiIzEvNrX2iemMWkxKdTNFv8kCXHoKKOvvnSBUpLzXO5_UoQ2Fg), [2](https://www.google.com/goto?url=CAESdAHrOzAVFYb2mi9oT4FrI2K_WAfEngNuom7AYplEB3qNrsjD7RdMATUm5Y8BQXFCkih-_9tfnaU_IrAE8p6YfruBb_6OZRnht-66j_vd7m0vqclQiamZOsVuD8gnzJprTT8AwnCNtKgXnSrHj7X_BImWMhPg), [3](https://www.google.com/goto?url=CAESggEB6zswFXbZZaipZ5NzGBqBeTJDYNKsynaj9TqccRnywra98vvgfNa-dJddX73xJxa8Bc2Uj9pqwhhndIagpPijR8IzBECY4YdjXtD574D5a8gK7k4fKfqr9-6uvvzlJO-7ekOvWSeWLtQA7XkK-2rfeVlbU0GfTRrV2Ptswdw0-oYR)]\nThe project addresses the reality that PIDs are not permanent strings, but rather maintained relations that are susceptible to \"erosion\" or deletion over time. [[1](https://www.google.com/goto?url=CAESWwHrOzAVhtOGH0sf-3J5cR4WFquDyX7Ltea77nu50ErHWyb2K8w2gx6Mwgoiu3XUAWDx_h9ZTfBYYb9A5SusWoQDAhXsnccaofqV9LQ0RLyIUdw6_ztlz-TcC9Q)]\nCore Focus & Instruments\n\n* Measuring \"Custody Separation\": The observatory tracks the actual population of platform-driven scholarly record removals. It evaluates how platforms handle metadata after a deletion occurs, specifically evaluating \"tombstone\" compliance rates (whether a placeholder remains) and the \"shape of absence\". [[1](https://www.google.com/goto?url=CAESYgHrOzAVwclx53UWemI-gRUgGTkOznhLvhwOD1FL-KWWDDY-0S_D1WwST_ulXelY08XEGx8kUEEUreC95ck44E-_xMpxTSPEgeWUF7tzwNnZj2FwHDnger2VMWgMipW4D7D4), [2](https://www.google.com/goto?url=CAESgAEB6zswFScJ6-IUs9ZGf6J_qcSLMueYILo1ifUGvTtCZ0srmgxcQsH92fbO_6cM2TzXaze5mTgpiBhSi1DMZnbAg73awgnsV_6H2ZDntNpVfDx85HE8zit6sWdiiIzEvNrX2iemMWkxKdTNFv8kCXHoKKOvvnSBUpLzXO5_UoQ2Fg), [3](https://www.google.com/goto?url=CAESggEB6zswFXbZZaipZ5NzGBqBeTJDYNKsynaj9TqccRnywra98vvgfNa-dJddX73xJxa8Bc2Uj9pqwhhndIagpPijR8IzBECY4YdjXtD574D5a8gK7k4fKfqr9-6uvvzlJO-7ekOvWSeWLtQA7XkK-2rfeVlbU0GfTRrV2Ptswdw0-oYR)]\n* The Zenodo Removal Census: Acting as its primary case study instrument (Case 001), it tracks a specific cohort of over 14,000 DOIs to establish a baseline analysis of how, why, and when records vanish from the Zenodo repository. [[1](https://www.google.com/goto?url=CAESgAEB6zswFScJ6-IUs9ZGf6J_qcSLMueYILo1ifUGvTtCZ0srmgxcQsH92fbO_6cM2TzXaze5mTgpiBhSi1DMZnbAg73awgnsV_6H2ZDntNpVfDx85HE8zit6sWdiiIzEvNrX2iemMWkxKdTNFv8kCXHoKKOvvnSBUpLzXO5_UoQ2Fg), [2](https://www.google.com/goto?url=CAESYgHrOzAVwclx53UWemI-gRUgGTkOznhLvhwOD1FL-KWWDDY-0S_D1WwST_ulXelY08XEGx8kUEEUreC95ck44E-_xMpxTSPEgeWUF7tzwNnZj2FwHDnger2VMWgMipW4D7D4)]\n* Cross-Platform Tracking: It outlines a forward roadmap to extend this tracking across multiple major scholarly platforms to map structural enforcement actions and account-level deletions. [[1](https://www.google.com/goto?url=CAESYgHrOzAVwclx53UWemI-gRUgGTkOznhLvhwOD1FL-KWWDDY-0S_D1WwST_ulXelY08XEGx8kUEEUreC95ck44E-_xMpxTSPEgeWUF7tzwNnZj2FwHDnger2VMWgMipW4D7D4)]\n\nKey Ecosystem Concepts\nThe project is part of a broader, sovereign alternative tracking architecture spearheaded by researcher Lee Sharks. It acts as the research counterpart to infrastructure initiatives, which include: [[1](https://www.google.com/goto?url=CAESYgHrOzAVwclx53UWemI-gRUgGTkOznhLvhwOD1FL-KWWDDY-0S_D1WwST_ulXelY08XEGx8kUEEUreC95ck44E-_xMpxTSPEgeWUF7tzwNnZj2FwHDnger2VMWgMipW4D7D4)]\n\n* The Severance Registry / Resolution Index: A system designed to map severed identifiers and resolve them outside of the primary platform's control. [[1](https://www.google.com/goto?url=CAESwgEB6zswFSlwpRHuWjp8PlruGi1anIp2Ca5NTbEzM1lzNOlL19oO0wrDX_nrsMVTcZF9Blc1lpK5GbktLBAZMQiTxHaI-p8C1yOYVp3gnZFmsAzAtAG_Ds8qcCYajUaVkYPYyg1_qdkVlRIXqGuMH8clMkTnsaeUxvjJKtx8i5UOGo97W8PXkm5oBcJa1hDnaeNL-00ZyRYcO7V-PZuUK_DAkMdsbA02UQeabRfp4ZbCZjiVU4DpKzNiWspPsnWvlBcUFQ), [2](https://www.google.com/goto?url=CAESYgHrOzAVwclx53UWemI-gRUgGTkOznhLvhwOD1FL-KWWDDY-0S_D1WwST_ulXelY08XEGx8kUEEUreC95ck44E-_xMpxTSPEgeWUF7tzwNnZj2FwHDnger2VMWgMipW4D7D4)]\n* The Capture Registry: An engine designed to capture asymmetry in how corrections and representation changes are documented across repositories. [[1](https://www.google.com/goto?url=CAESggEB6zswFXbZZaipZ5NzGBqBeTJDYNKsynaj9TqccRnywra98vvgfNa-dJddX73xJxa8Bc2Uj9pqwhhndIagpPijR8IzBECY4YdjXtD574D5a8gK7k4fKfqr9-6uvvzlJO-7ekOvWSeWLtQA7XkK-2rfeVlbU0GfTRrV2Ptswdw0-oYR)]\n\nFor open-source code and dataset specifics, you can view the project directly on the [Platform Erosion Observatory GitHub Repository](https://www.google.com/goto?url=CAESdAHrOzAVFYb2mi9oT4FrI2K_WAfEngNuom7AYplEB3qNrsjD7RdMATUm5Y8BQXFCkih-_9tfnaU_IrAE8p6YfruBb_6OZRnht-66j_vd7m0vqclQiamZOsVuD8gnzJprTT8AwnCNtKgXnSrHj7X_BImWMhPg). [[1](https://www.google.com/goto?url=CAESdAHrOzAVFYb2mi9oT4FrI2K_WAfEngNuom7AYplEB3qNrsjD7RdMATUm5Y8BQXFCkih-_9tfnaU_IrAE8p6YfruBb_6OZRnht-66j_vd7m0vqclQiamZOsVuD8gnzJprTT8AwnCNtKgXnSrHj7X_BImWMhPg)]\nIf you'd like to dive deeper, let me know if you want to explore:\n\n* The methodology behind the Zenodo Removal Census\n* What tombstone compliance rates reveal about repository permanence\n* How a Resolution Index handles severed identifiers\n\n[www.persistentidentifiers.org](https://www.persistentidentifiers.org)\nPersistent Identifiers — The PID Erosion Observatory\nWhat is a persistent identifier? A string whose relation to its object is maintained indefinitely by a responsible organization — resolution, metadata, and ...\n[www.alexanarch.org](https://www.alexanarch.org)\nThe Platform Erosion Observatory: The Zenodo Removal Census as ...\nJul 6, 2026 — Wiki Article 0 — The Platform Erosion Observatory: The Zenodo Removal Census as First Instrument, and the Plan for a Broader Cross-Platform Tracker is a empiric...\nGitHub\npersistent-identifiers · GitHub Topics\nDec 31, 2024 — Platform Erosion Observatory — empirical instrument for measuring what happens to scholarly records after removal: survival in aggregators, tombstone behaviour,\n[www.alexanarch.org](https://www.alexanarch.org)\nplatform erosion observatory — Google AI Overview, 2026-08-11 ...\nAug 11, 2026 — Core Focus Areas render identifier custody, removal censuses, and ... as pastedPersistent Identifiers — The PID Erosion Observatory Persistent Identifiers ...\ngithub.com\nGitHub - leesharks000/platform-erosion-observatory: Platform ...\nThe Platform Erosion Observatory. Measuring whether persistent identifiers persist. Public face of EA-EROSION-01 (deposit #1045, AXN:0421.EMPIRICAL ...\n[www.axnidentifiers.com](https://www.axnidentifiers.com)\nWhy AXN exists — identifier erosion, measured at registry scale\nmeasured by the PID Erosion Observatory · dated captures preserved. A persistent identifier is a maintained relation, not a string. When the maintenance ...\nmedium.com\nTHE OBELUS AND THE TOMBSTONE: On the Two Marks of ...\nJul 11, 2026 — ... Erosion Observatory; 1,838 severed identifiers resolving through the sovereign Resolution Index; the reception layer's confusions documented capture by ...\n",
 "transcript_class": "CAPTURE-TIME VERBATIM RECORD (SOURCE CARDS INCLUDED)",
 "transcript_complete": "Complete as pasted: one operator turn and one answer with its card rail of 7 cards.",
 "transcript_read": "READ IN FULL 2026-10-14",
 "per": 0.5,
 "per_v": {
  "author": true,
  "inst": false,
  "id": false,
  "src": true
 },
 "per_note": "Retained: the operator by name and the observatory's surfaces as cards. Lost: the institution and any identifier.",
 "sf": "Source cards: www.persistentidentifiers.org; www.alexanarch.org; GitHub; www.alexanarch.org; github.com; www.axnidentifiers.com; medium.com.",
 "sf_derived": null,
 "reading": "Checked 2026-10-14: 'Rate measures attribution separation; the Platform Erosion Observatory measures custody separation; the Capture Registry measures representation and correction asymmetry' is #1067's; 'a 14,284-DOI control cohort' and 'the shape of absence' are the observatory's own description (spxi.dev, method 0.15); PEO Case 001 is #1408, 'T0 Enumeration of the Firenze crui.unifi Corpus (14,284 DOIs)', a DataCite client collapse (14,283 → 0, 13–20 July 2026), not a Zenodo cohort; 1,838 severed identifiers through the Resolution Index is #1068's card snippet.",
 "analysis": "At the spelled-out name the Overview holds the instrument whole, both names as one, with its operator named and the archive's own division of labour among its instruments; the error is at one figure, a DataCite case carried into the Zenodo census. Against the 'what is' Overview the same day, the names that one split are here joined. Seated 2026-10-14 from the operator's message of 15:02 EDT, on the attestation in the same message ('signed out incognito both').",
 "d": "BOTH NAMES HELD, THE OPERATOR NAMED, CASE 001 MOVED TO ZENODO: at 'persistent identifier erosion observatory' the Overview gives the instrument under both names ('The Platform Erosion Observatory (also known as the PID Erosion Observatory)'), its premise ('PIDs are not permanent strings, but rather maintained relations'), its measures (custody separation, tombstone compliance, 'the shape of absence'), its roadmap, and names its operator: 'a broader, sovereign alternative tracking architecture spearheaded by researcher Lee Sharks'. It places the Severance Registry / Resolution Index and the Capture Registry beside it, the latter in the archive's own words (#1067: 'the Capture Registry measures representation and correction asymmetry'). One figure moves: Case 001, the 14,284 DataCite DOIs of the Firenze client crui.unifi (#1408), becomes 'a specific cohort of over 14,000 DOIs' tracked for 'how, why, and when records vanish from the Zenodo repository'.",
 "d_full": "BOTH NAMES HELD, THE OPERATOR NAMED, CASE 001 MOVED TO ZENODO: at 'persistent identifier erosion observatory' the Overview gives the instrument under both names ('The Platform Erosion Observatory (also known as the PID Erosion Observatory)'), its premise ('PIDs are not permanent strings, but rather maintained relations'), its measures (custody separation, tombstone compliance, 'the shape of absence'), its roadmap, and names its operator: 'a broader, sovereign alternative tracking architecture spearheaded by researcher Lee Sharks'. It places the Severance Registry / Resolution Index and the Capture Registry beside it, the latter in the archive's own words (#1067: 'the Capture Registry measures representation and correction asymmetry'). One figure moves: Case 001, the 14,284 DataCite DOIs of the Firenze client crui.unifi (#1408), becomes 'a specific cohort of over 14,000 DOIs' tracked for 'how, why, and when records vanish from the Zenodo repository'.",
 "d_truncated": false,
 "links": [
  {
   "url": "https://www.alexanarch.org/captures/persistent-identifier-erosion-observatory-aio-20261014/",
   "authority": "canonical",
   "note": "the capture's own record page; cite this form"
  },
  {
   "url": "https://www.alexanarch.org/captures/#persistent-identifier-erosion-observatory-aio-20261014",
   "authority": "gallery",
   "note": "the canonical gallery, anchored by slug"
  },
  {
   "url": "https://www.godkinggoogle.com/captures/#persistent-identifier-erosion-observatory-aio-20261014",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.leesharks.com/captures/#persistent-identifier-erosion-observatory-aio-20261014",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.machinemediation.org/captures/#persistent-identifier-erosion-observatory-aio-20261014",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  }
 ],
 "imgs": [],
 "img_urls": [],
 "cite": "https://www.alexanarch.org/captures/persistent-identifier-erosion-observatory-aio-20261014/",
 "citable_unit": "address — the exact issued string on one surface, per the Surface Rule (MANUS, 2026-08-15)",
 "addr_id": "ADDR-595a2a143874",
 "obs_id": "OBS-034bc99fc0d5",
 "n_observations": 1,
 "observations": [],
 "dates": [
  "2026-10-14"
 ],
 "defects": [],
 "findings": [
  "ONE INSTRUMENT, BOTH NAMES. 'The Platform Erosion Observatory (also known as the PID Erosion Observatory)'; at the 'what is' string the same day the two were split.",
  "THE OPERATOR NAMED. 'spearheaded by researcher Lee Sharks'.",
  "THE ARCHIVE'S OWN DIVISION OF LABOUR. Custody separation (the observatory), correction asymmetry (the Capture Registry): #1067's sentence, distributed.",
  "CASE 001 MOVED. The Firenze crui.unifi corpus at DataCite (14,284 DOIs; #1408) given as the Zenodo Removal Census's Zenodo cohort.",
  "THE REGISTRY CITED. Card 4 is the Capture Registry's record at 'platform erosion observatory', 2026-08-11; card 2 is #1045's wiki article."
 ],
 "series": null,
 "other_slugs": null,
 "collisions": null,
 "oq": null,
 "rounds": null,
 "turns": null,
 "rerun": "https://www.google.com/search?q=persistent+identifier+erosion+observatory",
 "rerun_alt": null,
 "heteronym": null,
 "model_attribution": null,
 "operator_disclosure": null,
 "longitudinal_priors": [
  "platform-erosion-observatory-20260811",
  "pid-erosion-observatory-what-is-aio-20261014"
 ],
 "longitudinal_successors": null,
 "related_deposits": [
  1045,
  1068,
  1067,
  1408,
  1044
 ],
 "intended": null,
 "originator": {
  "name": "Lee Sharks",
  "relation": "archive",
  "entity_type": "site",
  "spxi_treatment": "full",
  "basis": "The PID Erosion Observatory (persistentidentifiers.org) is the archive's measurement instrument: founded 2026-07-06 as the Platform Erosion Observatory (EA-EROSION-01, #1045), renamed on 2026-07-12 with its domain; SPXI method 0.15. Recorded 2026-10-14."
 },
 "notes": {
  "date_basis": "The operator's message of 2026-10-14, 15:02 EDT.",
  "operator_words": "new entiry.. signed out incognito both:"
 },
 "record_url": "https://www.alexanarch.org/captures/persistent-identifier-erosion-observatory-aio-20261014/"
}