AXN:07A0.CAPTURE

AXN:07A0.CAPTURE is the position of the Capture Registry address for the query “AI overview capture registry”. 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.

Query
AI overview capture registry
Identifies
the capture record of the Capture Registry
Hex position
07A0
Family
CAPTURE
Ledger
/data/captures/axn.json

AXN:07A0.CAPTURE.♄➕⏹️🕊️♎□

Observation
Google AI Overview, 2026-06-15 · the capture
Description
The Wound Gauge describes itself. 'The AI Overview Capture Registry (e.g., EA-WG-CAPTURES-01) is a longitudinal, open-access dataset tracking how Google's generative AI (AI Overviews, AI Mode, and knowledge panels) responds to specific long-tail and concept-based queries over time' (Zenodo +1). Expanded: Current Edition v6.1, 96 documented captures, four categories (Frameworks, Heteronyms, Sites & Surfaces, Books & Projects). 'Researchers and SEO analysts use it to observe compositional patterns (like how summarization basins vs. organic retrieval basins function) and entity disambiguation' (Zenodo +1). Links to Zenodo Archive, Leesharks.com, and Godkinggoogle Vercel. The composition layer accurately describes the instrument that documents it.
Analysis
The Wound Gauge describes itself. 'The AI Overview Capture Registry (e.g., EA-WG-CAPTURES-01) is a longitudinal, open-access dataset tracking how Google's generative AI (AI Overviews, AI Mode, and knowledge panels) responds to specific long-tail and concept-based queries over time' (Zenodo +1). Expanded: Current Edition v6.1, 96 documented captures, four categories (Frameworks, Heteronyms, Sites & Surfaces, Books & Projects). 'Researchers and SEO analysts use it to observe compositional patterns (like how summarization basins vs. organic retrieval basins function) and entity disambiguation' (Zenodo +1). Links to Zenodo Archive, Leesharks.com, and Godkinggoogle Vercel. The composition layer accurately describes the instrument that documents it.
Match
INDETERMINATE — EXACT MATCH
Sealed observation
/data/captures/sealed/capture-registry-self.json — SHA-256 a490f77eaf9d1da176f8aa35cfc80a2803ab080ff3a9327452ed1881d10f9e60

AXN:07A0.CAPTURE.⏪🪞💛🌕🔴↘️

Observation
Google AI Overview, 2026-10-20 · the capture
Description
THE NAME KEPT, THE REGISTRY REPLACED: at the address where it composed the registry as itself in June, Google AI Overview gives 'An AI registry (or AI overview capture registry)' as an enterprise catalog for 'CISOs, Chief Compliance Officers', sorts the registry's own kind under 'AI Overview Tracker / Scraping Registry (e.g., Honeyb AI, AIOviewTrack)' for 'SEO Managers, Digital Marketers', cites twelve vendors and trackers, none using the phrase — with alexanarch.org first in organic. The liquidation #1459 named in August.
Reading
Longitudinal observation at the address of 2026-06-15 ('AI overview capture registry', capture-registry-self), seated on the operator's ruling (operator, 2026-10-20 12:47 EDT: 'but that is a recorded capture because the registry already holds that address, doesnt it? if it holds a capture at that address, broad match, then it goes in under longitudinal as erasure'); the string was issued in lower case, 'ai overview capture registry', and the address is held. The innocent reading first, in full: the answer defines 'An AI registry (or AI overview capture registry)' as 'a centralized, live catalog used by enterprises to inventory, manage, and govern all artificial intelligence assets', lists its purposes (centralized visibility, risk and compliance under the EU AI Act, NIST AI RMF and ISO/IEC 42001, automated intake through trail, ServiceNow, OneTrust, Copilot Studio), then distinguishes 'Enterprise AI Registry (e.g., Collibra, trail)' from 'AI Overview Tracker / Scraping Registry (e.g., Honeyb AI, AIOviewTrack)' — goal 'SEO monitoring, competitive analysis, marketing visibility', target user 'SEO Managers, Digital Marketers, Brand Strategists', mechanism 'DOM scraping via Playwright, mobile proxies, or SERP APIs' — recommends Advanced Web Ranking, Playwright scripts and Google Cloud's Agent Registry, and asks whether the reader is building a compliance database or an SEO scraper. Against the address's record: on 2026-06-15 the same surface, at this string, composed the registry as itself — 'The AI Overview Capture Registry (e.g., EA-WG-CAPTURES-01) is a longitudinal, open-access dataset tracking how Google's generative AI (AI Overviews, AI Mode, and knowledge panels) responds to specific long-tail and concept-based queries over time'. Four months on, the name is kept and its being replaced: an enterprise model catalog, and the registry's own kind sorted with the SEO trackers. The results page of the same query ranks alexanarch.org first (the capture of 2026-08-13); none of the twelve cards is the archive's or uses the phrase 'capture registry'. #1459 (2026-08-13) named the substitution in its title before it occurred here: 'Compositional Liquidation into SEO Monitoring, SERP Extraction, and Generic AI-Registry Semantics'. The operator's question (12:34): 'on what possible legitimate basis would my capture registry be excluded from composition as against these commercial sources while appearing first in organic?'
Analysis
At the address where Google AI Overview composed the AI Overview Capture Registry as itself on 2026-06-15, it now gives the name as an alternate name of an enterprise AI-model registry, files the registry's own kind under SEO trackers for digital marketers, and cites twelve vendor and tracker pages, none of which uses the phrase, while organic ranks the archive's capture page first. Total erasure (target_absent, generic); every availability condition but a typed entity holds; the substitution #1459 named in August, carried out at the address it named.
PER
1.0 — Lost: author, institution, identifier and source. The registry's name survives as an alternate name of an enterprise category; no card is the archive's.
Citations
12 (0 archive-controlled)
Sealed observation
/data/captures/sealed/ai-overview-capture-registry-aio-20261020.json — SHA-256 d759cd04c1db4acfc61132504884f4b564d7ee7607ae34a5193fa536039ff09e

Relations

Read from the fields that record them (/data/axn-relations.json); a hash names bytes and supplies no relation.

Opened by

Resolver rule: alexanarch.org/axn/<HEX> · term set: AXN identifier set · machine index: /api/axn-index.json