AXN:0822.CAPTURE — semantic address alexanarch

AXN:0822.CAPTURE is the position of the Capture Registry address for the query “semantic address alexanarch”. 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:0822.CAPTURE.🌱👇♌○🛡️🍂`

Observation: Google AI Overview, 2026-07-25 · the capture
Description: THE COMPOSITION LAYER CITES THE ADDRESS SET BUILT TO QUERY IT. 1,964 canonical queries, published as a dataset with a file size, retrieved by the system they address.
Reading: THE INSTRUMENT’S INDEX IS IN THE BASIN IT INDEXES. Three of three cards are alexanarch.org, and two of them describe the semantic-address dataset in its own terms: "1,964 canonical queries — THE ADDRESSES THROUGH WHICH ALEXANARCH TERMS COULD BE RETRIEVED FROM THE COMPOSITION LAYER (Google AI Overview, AI Mode)", published as data/semantic-addresses.json at 1.28 MB. That is the addressing scheme of this registry, served back by the surface it was built to address. Earlier today the gallery was cited with a prior capture’s ANALYSIS as its snippet; here it is the QUERY SET ITSELF, with a byte count. Card 1’s snippet is the NAVIGATION BAR — "Browse Wiki Graph Lexical Citations Observatory Captures Book Resolve Addresses Datasets Principles Identifiers Deposit" — the archive’s entire surface inventory rendered as description. Second navigation-bar-as-snippet in the corpus after the «alexanarch deleuze» capture. The composed answer also offers to "pull the exact data you need" and asks whether the user wants "the cryptographic identifier (AXN) rules" — the layer volunteering to serve the archive’s own identifier specification.
Analysis: Framework-level adoption, and the only capture in the registry whose grounding set is entirely first-party. The surface did not describe a work in the corpus; it described the corpus's own retrieval instrumentation — canonical query paths, observation classes, the entity bridge to the lexical layer, the JSON repository — and got the architecture substantially right, sourcing every claim to alexanarch.org. The system that measures how retrieval surfaces receive this archive was itself received, accurately, by a retrieval surface. SCHEMA-DATA DRIFT (archive-side defect, not confabulation). The composition lists four observation classes: observed, subjunctive, unrated, and verified non-address. The live data carries three — subjunctive 1751, observed_address 238, verified_non_address 20 — and no address anywhere in the file bears the class 'unrated'. But the term is not invented: it is declared in the published schema at /data/semantic-addresses.schema.json, under class_counts, and the registry changelog records that on 2026-07-16 'observed_address and unrated collapsed into one class'. The class was retired in the data and left standing in the schema. The surface read the authoritative machine-readable contract and reported it faithfully; the contract was stale. FINDING: a published schema that outlives its own data becomes a source of durable, well-grounded, incorrect …
Match: BROAD MATCH — CAPTURE
PER: 0.5
Citations: 3
Sealed observation: /data/captures/sealed/semantic-address-alexanarch-framework-adoption-20260725.json — SHA-256 19b7ad9b2d78edefeadee9fc1b9ead826839b6c62786ff5ae57f3d8cb6f29289