AXN:083A.CAPTURE — alexanarch OAI — Alexanarch AXN resolver

AXN:083A.CAPTURE is the position of the Capture Registry address for the query “alexanarch OAI”. Each observation at the address (one surface, one date) is one AXN, its glyphs derived from the SHA-256 of the observation sealed with its analysis and measures.

`AXN:083A.CAPTURE.🌘📋🜁🏷️♉🛡️`

Observation: Google AI Overview, 2026-08-04 · the capture
Description: THE TERMINATION IS COMPOSED AS THE FOUNDING CAUSE, IN THE LAYER’S OWN WORDS: "founded June 2026 as a reaction to SUDDEN CUSTODIAN DE-PLATFORMING (termination of deposits on Zenodo)."
Reading: THE ARCHIVE’S ORIGIN STORY IS NOW ITS DEFINITION. The answer supplies the mission unprompted and in the archive’s own terms: "founded June 2026 as a reaction to SUDDEN CUSTODIAN DE-PLATFORMING (termination of deposits on Zenodo)… machine-mediated research and training-layer data CANNOT BE SILENTLY ERASED BY A CENTRALIZED ENTITY." And the identifier claim: "replaces standard DOIs with AXN… CONTENT-DERIVED CRYPTOGRAPHIC INTEGRITY." A DOI substitute, described as a substitute, by a system that indexes DOIs. The technical placement is accurate and generous: Alexanarch "serving as a REPOSITORY DATA PROVIDER that utilizes the OAI-PMH interface", allowing "academic search engines, institutional mirrors, and automated discovery services (SUCH AS OPENALEX) to systematically harvest and index metadata." OpenAlex named as a harvester of the archive — the same OpenAlex that, per an earlier capture, still indexes a deleted DOI. The answer closes by asking whether the user wants to "harvest metadata from the Alexanarch repository using an OAI client, or… DEPOSIT AI-ASSISTED RESEARCH DATA INTO THEIR ARCHIVE." The composition layer offering to route depositors to the archive.
Match: BROAD MATCH — CAPTURE
PER: 0.75
Sealed observation: /data/captures/sealed/20260804-alexanarch-oai-overview.json — SHA-256 0745a04caa2d11f23f004b0691103ec71b045e5b8937b0c36c4186068ec21d20