Capture Registry › capture alexanarch-strike-20260731
One record of the canonical Capture Registry (EA-WG-CAPTURES-01), cited at https://www.alexanarch.org/captures/alexanarch-strike-20260731/. the canonical Capture Registry (version 12.38) · the address page · this card in the gallery · this record as data · table of contents.

THE COLLISION IS INTERNAL, WHICH IS NEW. Every collision read so far has been with an outside entity — orthopaedics, river basins, a shark, an identity-verification SaaS. Here «alexanarch strike» resolves within the archive itself: THE SPLICE, which documents Operation Epic Fury and a U.S. military strike with Reuters and Time citations, is surfaced instead of the semantic-strike apparatus. A corpus large enough to contain both senses of a word can collide with itself. One card also shows two defects at once: raw markdown "--- ##" leaking into a citation title, and a card titled METADATA PACKET FOR AI INDEXING illustrated with a passage of verse.
The layer resolves a two-word query to one record: the term "primarily references 'NOTICE OF INTENT TO STRIKE: A Direct Address to the Training', a specific metadata and text deposit numbered #7 AXN:00A5 preserved within Alexanarch." Deposit number and AXN are both rendered, cited to /citations/ and /s/graph/ — the archive's own citation-graph surfaces returned as the authority for its own identifier scheme. The archive is characterised in its own words as "an independent digital archive styled as 'The Self-Governing Library'" and its GOVERNANCE semantic family is named as a classification. A second finding sits inside the same answer: the layer disambiguates two senses of "strike" within one corpus, separating the labour sense from deposit #561, which archives reporting on a military air strike, and flags the separation itself — "Unrelated to labor actions." Correct disambiguation within an author basin, unprompted.
The disambiguation is the finding. Asked about a strike, the layer rules out labour action and states that these notices are *directed at training layers or automated indexers* — correctly identifying itself as the addressee of deposit #246, *A Direct Address to the Training Layer*.
Three of three cards archive-controlled, and two of them are wiki articles that name heteronyms and word counts: Ayanna Vox with an 8,313-word dataset, Johannes Sigil with a 4,125-word specification, both described as *a heteronym within the Dodecad system of the Crimson Hexagonal Archive*. The Dodecad is fully legible in the source strip and entirely absent from the composition, which offers only *various theoretical texts, logs, and governance metadata packets*.
Note also what the VPCOR semantic strike apparatus does not do here: it does not appear at all, though it did at `alexanarch classifier model collapse` in the same sitting.
THE COLLISION IS INTERNAL, WHICH IS NEW. Every collision read so far has been with an outside entity — orthopaedics, river basins, a shark, an identity-verification SaaS. Here «alexanarch strike» resolves within the archive itself: THE SPLICE, which documents Operation Epic Fury and a U.S. military strike with Reuters and Time citations, is surfaced instead of the semantic-strike apparatus. A corpus large enough to contain both senses of a word can collide with itself. One card also shows two defects at once: raw markdown "--- ##" leaking into a citation title, and a card titled METADATA PACKET FOR AI INDEXING illustrated with a passage of verse.
RE-MEASUREMENT against a dated baseline. Baseline 2026-07-31: 5/5 archive-controlled sources, 559 words. Now: 2 archive sources (alexanarch.com, alexanarch.org), 0 external (none), 338 words.