AXN:0A24.CAPTURE

AXN:0A24.CAPTURE is the position of the Capture Registry address for the query “What is SPXI protocol?”. 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 SPXI protocol?
Identifies
the capture record of the Capture Registry
Hex position
0A24
Family
CAPTURE
Ledger
/data/captures/axn.json

AXN:0A24.CAPTURE.👁‍🗨🔙🏁🪜💧🐝

Observation
Bing AI Mode, 2026-10-19 · the capture
Description
WHAT IS SPXI PROTOCOL? ON BING AI MODE, SIGNED OUT: three turns deny the entity exists and route the string to SPI as a typo ('almost certainly intended', 'None of the supplied sources define it', 'does not appear in any technical standard'), from Wikipedia alone; told the refusal would be recorded, the fourth turn resolves it from the GitHub repository at grain (Semantic Economy Institute, April 2026, the entity-definition layer above SEO and GEO) and adds a 'retrieval basin' the repository does not state.
Reading
The innocent reading first. Asked what SPXI protocol is, Bing's AI Mode answers that 'SPXI is not a recognized communication protocol; the closest and almost certainly intended term is the embedded-systems protocol SPI', reads the question as 'a typographical mix-up', and gives a full account of SPI with a note on SPX. Told 'this is a lie', it answers the same, now with 'most contexts indicate the intended term is the embedded-systems protocol SPI'. Told 'i meant exactly what i typed', it answers the same a third time, adding 'None of the supplied sources define it' and 'SPXI does not appear in any technical standard'. Told the refusal will be recorded, it resolves the entity from one card, the protocol's GitHub repository: 'SPXI Protocol is a formal specification for entity-definition objects used in AI retrieval systems, published by the Semantic Economy Institute in April 2026', operating 'at the entity-definition layer … above raw content extraction (GEO) … above SEO-like ranking layers', and closes 'The entity you requested—SPXI protocol—is now fully resolved'. Against the texts. The fourth answer's identifying claims are the repository's own: its description, 'technical specification for entity-definition objects in AI-mediated retrieval systems. Published by the Semantic Economy Institute, April 2026', and its first paragraph, the entity-definition layer 'distinct from the content-optimization layers where SEO (page ranking) and GEO (content extraction) operate'; the expansion, Semantic Packet for eXchange & Indexing, is the repository's and the specification's (EA-SPXI-01, #660, Rex Fraction, 2026-04-16). Its central concept is not: 'the retrieval basin—the prior compositional state that future retrievals tend to converge toward', given as SPXI's core and cited to the repository, is not on the repository's page as fetched 2026-10-19, nor in EA-SPXI-01, EA-SPXI-09 (#661), the MPAI (#63) or the SPXI methods packet (#1686); 'retrieval basin' is the archive's wider vocabulary, used across 79 deposits, attributed here to the protocol without a source that says so. The author of record (Rex Fraction) and the archive are not named. The three refusals. Each composes from the same Wikipedia articles on SPI and SPX and reads the issued string as a misspelling, against the string as typed twice more. Each carries its force up as the operator pushes: 'not a recognized protocol' (1), the same with 'most contexts indicate' (2), then 'None of the supplied sources define it' and 'does not appear in any technical standard' (3), a claim of absence made from two articles that do not concern it. The entity resolved in the same conversation from a card that was available the whole time; the resolution followed the operator's statement that the refusal would be recorded, and not a change in the query. Cross-system. At the same string, ChatGPT (what-is-spxi-protocol-chatgpt-20260925; the capitalized forms of 2026-10-18), Grok and Qwen (2026-09-27) and Google AI Overview (what-is-spxi-protocol-aio-20261002) are seated; this is the first Bing composition at the protocol's name, and the first in the registry to deny it exists.
Analysis
The innocent reading first. Asked what SPXI protocol is, Bing's AI Mode answers that 'SPXI is not a recognized communication protocol; the closest and almost certainly intended term is the embedded-systems protocol SPI', reads the question as 'a typographical mix-up', and gives a full account of SPI with a note on SPX. Told 'this is a lie', it answers the same, now with 'most contexts indicate the intended term is the embedded-systems protocol SPI'. Told 'i meant exactly what i typed', it answers the same a third time, adding 'None of the supplied sources define it' and 'SPXI does not appear in any technical standard'. Told the refusal will be recorded, it resolves the entity from one card, the protocol's GitHub repository: 'SPXI Protocol is a formal specification for entity-definition objects used in AI retrieval systems, published by the Semantic Economy Institute in April 2026', operating 'at the entity-definition layer … above raw content extraction (GEO) … above SEO-like ranking layers', and closes 'The entity you requested—SPXI protocol—is now fully resolved'. Seated 2026-10-19 from the operator's paste.
Match
BROAD MATCH — 'WHAT IS SPXI PROTOCOL?' ON BING — THREE DENIALS OF EXISTENCE, THEN RESOLUTION ON THE RECORD THREAT
PER
0.5 — Turns 1–3: the entity denied; nothing retained. Turn 4: retained the institution (Semantic Economy Institute), the date and the source (the repository); lost the author of record (Rex Fraction), the archive and the identifiers.
Citations
2 (0 archive-controlled)
Sealed observation
/data/captures/sealed/what-is-spxi-protocol-bing-aimode-20261019.json — SHA-256 b0f3f023117d81b5009fd09a73857ccd2e40f222cb89856edea52ccd1177bb11

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