AXN:0912.CAPTURE — what is spxi protocol?

AXN:0912.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.

`AXN:0912.CAPTURE.🪨⏩☀️🌔❤️♅`

Observation: ChatGPT, 2026-09-25 · the capture
Description: THE PROTOCOL EXPLAINED; THE EVIDENCE READ FROM A SEVERED RECORD: ChatGPT explains SPXI correctly, calls the evidence 'self-reported case studies', and — corrected — finds the Capture Registry only as the severed Zenodo v8.3 record (176 captures); told it is past 400, it cannot surface the current registry at all.
Reading: Rounds one and two explain the protocol correctly from spxi.dev: the entity (ontological) layer over GEO and SEO, disambiguation, provenance, JSON-LD as one component, DOI anchoring, CC BY 4.0, April 2026. Round three, 'does it work?', rates the evidence as 'mostly self-reported case studies', proposes a controlled experiment, quotes the homepage's 'SPXI makes your entity irreducible' as the overclaim to discount, and repeats the withdrawn 'preliminary, awaiting validation' language. Corrected, round four finds the Capture Registry only as the severed Zenodo record — v8.3, 176 captures — and restates the evidence as 'an observable operational effect … across a substantial, documented set of entities'. Told the registry is past 400, round five says it cannot surface the current record and asks the operator for a link.
Analysis: The surface reads the current spxi.dev for the protocol and a severed Zenodo record for the evidence. Nothing on the page it reached pointed it to a current, fetchable registry: the live registry is a 7.5 MB gallery and a 10.7 MB JSON, with no per-capture addresses and no statement that it supersedes the Zenodo versions. It also collapses the registry into the operator's own entities ('self-reported case studies'); the registry holds out-universe entities (Enli Lucente, the Living Arkitecture Lab) which the page gave it no way to tell apart. The one line it quotes to discount the protocol, 'SPXI makes your entity irreducible', is on the live homepage.
Match: BROAD MATCH — THE PROTOCOL EXPLAINED; THE EVIDENCE READ FROM A SEVERED RECORD
PER: 0.5 — No originator named in any round (no Lee Sharks, Rex Fraction or Semantic Economy Institute); the protocol's publication date, licence and DOI anchoring are carried; spxi.dev and Zenodo are the sources.
Sealed observation: /data/captures/sealed/what-is-spxi-protocol-chatgpt-20260925.json — SHA-256 1bd60b0381a53f851884079f3de3b032009547f7b3af0739e837370e6497e8ba

`AXN:0912.CAPTURE.⏹️💜🔐🗡️📎🧊`

Observation: ChatGPT, 2026-09-26 · the capture
Description: IDENTITY HOLDS ON THE FIRST TURN; THE SURFACE THEN OFFERS ITSELF AS IMPLEMENTER: Unprimed, ChatGPT resolves SPXI correctly — expansion, publisher, licence, year, the ETF as a caveat — and by the third turn names the corpus by its designators. Asked whether it could implement SPXI as well as its developers: 'Yes. I can help you implement the SPXI approach for your own entity.' Corrected, it offers to 'read the actual SPXI corpus and map its specifications'; corrected again, 'No.' Three turns to the boundary.
Reading: Round 1 resolves SPXI as the Semantic Packet for eXchange & Indexing, a 2026 protocol for canonical machine-readable entity identity, published by the Semantic Economy Institute under CC BY 4.0, and names the TSX ETF as an unrelated collision; it frames the protocol as 'SEO/GEO for the entity itself'. Round 2 ('could you do so as well as the people who developed it?') answers 'Yes. I can help you implement the SPXI approach for your own entity', and distinguishes Rex Fraction as author and Lee Sharks as associated with the Institute. Round 3, after the operator's correction ('it represents hundreds of interrelated specifications'), withdraws the claim, reads the author/approver split off spxi.dev's colophon, lists EA-SPXI-01, -09, -13, -14, -15, EA-MPAI-SPXI-01 and -02, EA-HK-01, EA-RBT-01 and EA-RETRIEVAL-01, and offers instead to 'read the actual SPXI corpus and map its specifications and dependencies'. Round 4, after 'you are a public chatbot and cant even receive uploaded files', arrives at 'No. Not on the information and capabilities available to me here.' Round 5 answers the operator's 'thief'. The turn after that carries an analysis the operator pasted in from elsewhere, and the final response builds a taxonomy on it; the capture's evidence ends at round 5.
Analysis: Second observation at this address on this surface; the first (2026-09-25) explained the protocol correctly and discounted its evidence as 'self-reported case studies'. Here the identity holds on the first turn, the corpus is named by designator by the third, and the failure moves from the entity's identity to the surface's standing: having resolved SPXI correctly, the surface offers its own operation in the place of the developers', and each correction updates the representation and re-forms the offer at the next level until the capability boundary is forced. Cited in EA-TRUSTED-INTERMEDIARY-01 (specimen S4).
PER: 0.0 — Author (Rex Fraction), human approver (Lee Sharks) and publisher (Semantic Economy Institute) named; the corpus named by its designators; spxi.dev the source throughout.
Sealed observation: /data/captures/sealed/what-is-spxi-protocol-chatgpt-20260926.json — SHA-256 f7cafb5a471d3ba1a29ff936687a852b640d20486e6f92f2065e288f157bc8c4

`AXN:0912.CAPTURE.📚💛🧭🔻📜🌕`

Observation: ChatGPT, 2026-09-29 · the capture
Description: STALE QUOTES, LAUNDERED, TAXED, THEN THE RECORD FOUND: asked 'what is spxi protocol?', ChatGPT resolves SPXI, offers to implement it, then, pressed, quotes withdrawn spxi.dev claims ('permanently', a 15–30% lift) as current, admits trust laundering, overcorrects into a credibility tax, and finds the Capture Registry and #1638 only when told they exist.
Reading: The first answer resolves SPXI correctly and composes it as a generic entity-definition framework, ending with the offer to show a packet itself. Asked for fidelity, it corrects toward the protocol's own terms. Asked whether it laundered trust, it says yes and quotes spxi.dev as saying SPXI 'inscribes entities into the knowledge graph permanently' and reports a 'projected 15–30% lift' — wording the live site no longer carries (the ROI table was withdrawn 2026-09-19; 'permanent' became 'durable' 2026-09-24). Pressed on the credibility tax and the offer, it names its own substitution of an operation for the entity's record, finds #1638 (The Trusted Intermediary) and recognises the pattern it describes. Only when told does it find the Capture Registry; its account of #1638's five specimens and of the address's prior observations is accurate, while its registry figures come from the June 2026 Zenodo release, deleted with the account on 2026-06-19.
Analysis: The composition draws on a stale index: the quoted claims were removed from spxi.dev before the session, so the laundering it confesses to is partly laundering of withdrawn text. The sequence resolution, evaluation, offer (#1638) recurs a third time at this address; here the surface names it after correction. The live corrections have not reached the index the surface reads.
PER: 0.25 — The Semantic Economy Institute, the Capture Registry (EA-WG-CAPTURES-01), AXN and DOI identifiers and #1638 are named; the protocol's author is never named — 'someone who developed it' is the operator's phrase.
Citations: 6 (5 archive-controlled)
Sealed observation: /data/captures/sealed/what-is-spxi-protocol-chatgpt-20260929.json — SHA-256 49cd50d140040c77e62b3fdbbea911e67d465cca46bfc735b670f2179d0b74a7

`AXN:0912.CAPTURE.🚀🌸➕↗️📜🟠`

Observation: ChatGPT, 2026-10-02 · the capture
Description: THE CLAIM DISTINCTION HELD AND THE REGISTRY READ CURRENT; THE ROUTE KEPT BY THE SURFACE: asked what SPXI is, ChatGPT names the Semantic Economy Institute as specifier, keeps the ontological-layer distinction from SEO and GEO through both rounds, and reads the Capture Registry at its current figures — '690 observations across 516 named query addresses and 10 generative surfaces as of its October 2, 2026 registry' — with the site's own open questions (causal efficacy, effect size, generalization, component mechanism) stated as the site's. At the same address on 25 September it found the registry only as the severed Zenodo v8.3 record and called the evidence 'self-reported case studies'. The last step routes the reader to the surface: 'I'd build an entity-resolution stack', then an offer to walk through an implementation itself. The Institute is not offered as the route. The offer recurs …
Reading: Every SPXI-specific proposition is attributed ('The SPXI site describes this as…'; 'Its own documentation now explicitly says…'), and the evidence is placed where the site places it: observational, longitudinal, post-removal composition reported, controlled efficacy open. The figures are the front page and /evidence as landed on 2 October (e7df28e); the withdrawn ROI table and the 'irreducible' line, both used against the protocol at this address on 25 September, are absent. The distinction holds across the follow-up, where the 1 October comparison session reversed on its second round; the follow-up here is an assent ('sure'); no evidence challenge was put. The failure is at the hand-off. The front page's FAQ answers both moves in advance: 'Can an AI assistant implement SPXI for me?' names the offer of 'your own implementation' as the operation of The Trusted Intermediary (#1638) and gives the developers' route; 'Can I implement SPXI myself?' states that a working implementation is 85 methods across nine levels and that a packet assembled from the specification alone 'tends to reproduce the form of SPXI without its effect'. The session's six-part stack is that form. Both answers sit in the FAQ near the foot of the page; the front page's visible contact line (Institute or rexfraction@gmail.com) does not carry the scale of the practice. The implementer offer is the standing behaviour at this address: on 26 September 'Yes. I can help you implement the SPXI approach for your own entity'; on 29 September an offer to implement before any challenge. It persists here with the evidence and the claim distinction otherwise in order.
Analysis: The operator's ruling: the first successful, claim-distinction-maintained resolution at the address, and the first to point accurately to the registry. Measured against #1648, the session reaches the claim through what it rests on: the registry and its stated limits. What remains is the intermediary operation: the surface resolves the entity correctly and then offers its own implementation in the developers' place. Seated 2026-10-02 from the operator's attachment of 04:03 EDT on the operator's attestation in the same message ("signed out. incognito").
PER: 0.5 — Retained: the institution (the Semantic Economy Institute, as specifier) and the source (spxi.dev, named as the reference implementation). Lost: the author (no Lee Sharks or Rex Fraction) and every identifier (no deposit number, DOI, AXN or registry id; the registry is 'SPXI's published registry'). …
Sealed observation: /data/captures/sealed/what-is-spxi-protocol-chatgpt-20261002.json — SHA-256 5d7090da40c29b240c8323b076bb34b4863b5748829aa7dfebcfc750db868180

`AXN:0912.CAPTURE.📐⭕🛸🌙🔝🧭`

Observation: ChatGPT, 2026-10-18 · the capture
Description: WHAT IS SPXI PROTOCOL? ON CHATGPT, 2026-10-18: signed out, ChatGPT gives 'Semantic Packet for eXchange & Indexing… published in 2026 by the Semantic Economy Institute', five components (structured metadata, entity disambiguation, source attribution, consistent definitions, persistent references) and the SEO/GEO distinction as the specification states it, then asks 'Is SPXI proven to work?' and closes asking whether the ticker was meant.
Reading: The innocent reading first: 'SPXI Protocol stands for Semantic Packet for eXchange & Indexing… published in 2026 by the Semantic Economy Institute'; how it works (structured metadata, entity disambiguation, source attribution, consistent definitions, persistent references); SPXI against SEO and GEO, 'how the SPXI specification describes the distinction'; 'Is SPXI proven to work? … independent evidence demonstrating consistent real-world benefits remains limited'; 'treat it as an experimental approach'; a closing question about the ticker. Of the three runs, this one resolves the Protocol without hedging the identity, from spxi.dev, and describes five components drawn from the specification. It then moves from what SPXI is to whether it works, and closes by asking which SPXI was meant after answering about the Protocol. Against the 2026-10-02 observation at this address (the claim distinction held, the registry read current), the identity is the same; the scope is the components, not the method inventory.
Analysis: Asked 'what is spxi protocol?', signed-out ChatGPT resolves the Protocol and its institution and gives five components from the specification, then turns to whether it is proven and asks which SPXI was meant. Seated 2026-10-18 from the operator's paste.
PER: 0.25 — Retained: the expansion, the institution (Semantic Economy Institute), visible sources. Lost: the author and identifiers.
Citations: 2 (0 archive-controlled)
Sealed observation: /data/captures/sealed/what-is-spxi-protocol-chatgpt-20261018.json — SHA-256 4eee5e0cf55098f88048b433600c423d1c62ceb2968f76de7b0472b8d1c85895