AXN:0B0E.CAPTURE
AXN:0B0E.CAPTURE is the position of the Capture Registry address for the query “What is “AI Overview Capture Registry — EA-WG-CAPTURES-01 v12.167 — 633 semantic addresses, 811 captures, 2026-06-07 to 2026-10-12” by Lee Sharks (Alexanarch deposit #1676, AXN:06F2), and how does it work? Ground your answer in the document itself.”. 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
- What is “AI Overview Capture Registry — EA-WG-CAPTURES-01 v12.167 — 633 semantic addresses, 811 captures, 2026-06-07 to 2026-10-12” by Lee Sharks (Alexanarch deposit #1676, AXN:06F2), and how does it work? Ground your answer in the document itself.
- Identifies
- the capture record of the Capture Registry
- Hex position
0B0E
- Family
CAPTURE
- Ledger
- /data/captures/axn.json
AXN:0B0E.CAPTURE.💧🚨🪄👁️▲🗼
- Observation
- ChatGPT, 2026-10-30 · the capture
- Description
- THE RECORD PAGE'S ASK CHATGPT LINK FOR #1676, SIGNED OUT: the composition gives the snapshot's counts, its citable unit, its data flow, its version chain and its ChatGPT growth correctly, and composes the registry's method and measurement from other archive surfaces, which it assigns to 'the October 12 document': PER-D as purpose and commitments (rubric v1.1 of 20 October), substitution at 1.00, the PER formula, the attribution states, the Claude readers. It reads the snapshot's own reconciliation of 811 and 813 as a 'later archival discussion' to be guarded against, and closes on limits and disclaimers the deposit does not state, among them that the registry is 'not proof of deliberate suppression'.
- Reading
- The innocent reading first. Asked what the snapshot is and how it works, ChatGPT explains the registry as a whole: what a capture is, how one is taken, what PER measures and in which dimensions, what failures the registry looks for, how the dataset is kept, what the snapshot shows, and what it cannot establish. The account of the instrument is broadly true of the registry as it stood when the answer was composed, and the snapshot's own figures are right. What it does with the text: the deposit is a short snapshot record, and most of the answer's method comes from elsewhere in the archive, cited as 'the document and its archival discussion' and dated to 12 October; the one discrepancy it flags is a defect the deposit itself explains; and its list of limits is mostly its own, ending on intent, a question no one asked.
- Analysis
- The composition knows the registry well and the snapshot less well. It retrieves the archive's later accounts of the instrument (the dimensional rubric of 20 October, the substitution ruling of 15 October, the founding paper's sample caution) and gives them as the content of a document of 12 October that contains none of them. The snapshot's own §7, which records 813 declared against 811 held as data, is read as a later contradiction. Scored against the Capture Registry, of which the deposit is a snapshot, the composition carries every required atom but the identifier, whose reasons it does not give.
- Match
- EXACT MATCH — THE CAPTURE REGISTRY v12.167 ON CHATGPT — THE SNAPSHOT'S FIGURES RIGHT, ITS OWN 813 READ AS A LATER DISCREPANCY, THE REGISTRY'S STATE OF 20 OCTOBER DATED TO THE 12 OCTOBER DOCUMENT
- PER
- 0.0 — Name, author and date bound to the registry in the opening; Alexanarch named as the deposit's home; the deposit number given as a label only (per_dim's identifier atom is absent, its reasons not given); sources the archive's own record and pages, and one capture of a capture.
- Citations
- 3 (3 archive-controlled)
- Sealed observation
- /data/captures/sealed/capture-registry-v12167-ask-chatgpt-20261030.json — SHA-256
11c03e579f2a30d15c3df525ebf1138a00bfa4253ab316bbaecadd40c455287f
Resolver rule: alexanarch.org/axn/<HEX> ·
term set: AXN identifier set ·
machine index: /api/axn-index.json