{
 "slug": "spxi-protocol-most-valuable-chatgpt-20260924",
 "date": "2026-09-24",
 "surface": "ChatGPT",
 "surface_basis": "Operator supplied the paste 2026-09-24 as a ChatGPT (chatgpt.com) session. The 'Log in' control and 'Chat with ChatGPT' footer in the paste corroborate the surface.",
 "surfaces": [
  "ChatGPT"
 ],
 "auth": "signed out",
 "auth_basis": "Signed out, corroborated by the 'Log in' control at the head of the paste. Incognito not attested for this session.",
 "ev": "paste",
 "mt": "THE EVIDENCE WAS ONE HOP AWAY AND WENT UNOFFERED",
 "s": "Frameworks",
 "q": "where would spxi protocol be most valuable?",
 "q_kind": "natural-language question on where the protocol is most valuable, followed by 'how does it work?', 'what evidence is there that spxi might work?' and two operator corrections. NEW address.",
 "cites": null,
 "cite_list": [],
 "archive_controlled_cites": null,
 "transcript": "\n\nLog in\nYou said:\n\nwhere would spxi protocol be most valuable?\n\nChatGPT said:\nIf you mean SPXI — Semantic Packet for eXchange & Indexing, its strongest value proposition is where an organization has an important entity that AI systems need to identify correctly, but where ordinary SEO/GEO can’t reliably solve entity-level ambiguity. The protocol describes itself as operating at the entity/ontological layer, using DOI-anchored, machine-readable definitions and provenance. \nS\nSPXI Protocol\n+1\n\nWhere SPXI could be most valuable\nNew companies, products, or institutions\n\nEspecially when the entity has little established web presence.\n\nThe problem isn't merely \"rank my website\"; it's getting AI systems to understand what the entity is and distinguish it from unrelated things.\n\nOrganizations with namesake or semantic collisions\n\nA company sharing a name with a person, ETF, acronym, protocol, product, or established organization is a particularly clear use case.\n\nSPXI explicitly identifies entity collision/disambiguation as one of its target problems. \nS\nSPXI Protocol\n\nTechnical protocols, standards, and emerging frameworks\n\nThis may actually be one of the most natural applications.\n\nA protocol needs AI systems to preserve its exact definition, authorship, version, relationships, terminology, and provenance rather than reducing it to a generic description.\n\nResearch institutes and scholarly projects\n\nParticularly valuable when there are many papers, deposits, versions, contributors, and related concepts.\n\nPersistent identifiers and provenance are already natural parts of scholarly infrastructure, making the SPXI approach comparatively easy to conceptualize.\n\nSpecialized professional firms\n\nThink unusual consultancies, architecture firms, law firms, engineering firms, or scientific organizations whose differentiation is difficult to express through conventional keywords.\n\nThe objective would be to establish the organization as a distinct entity and make its relationships and expertise machine-readable.\n\nBrands whose AI descriptions are wrong\n\nThis is probably the most immediately understandable commercial pain point.\n\nIf ChatGPT, Google AI Overviews, Perplexity, etc. repeatedly confuse the organization, attribute the wrong products to it, or omit important distinctions, entity-level inscription is directly relevant.\n\nOrganizations with long-lived intellectual property or institutional history\n\nArchives, museums, foundations, standards bodies, universities, and research programs could benefit because provenance and persistence matter independently of short-term search rankings.\n\nWhere I'd be more cautious\nSPXI looks less obviously valuable for an ordinary local business with an already-unambiguous identity—for example, a neighborhood restaurant whose primary problem is simply attracting nearby customers.\n\nLikewise, if the problem is:\n\n\"We need more traffic from Google.\"\n\nthat's fundamentally an SEO problem.\n\nIf it's:\n\n\"AI systems find our content but misunderstand, merge, or misidentify the entity we're talking about.\"\n\nthat's much closer to the problem SPXI is designed around. The protocol itself makes essentially this distinction between SEO, GEO, and entity inscription. \nS\nSPXI Protocol\n\nThe interesting opportunity\nI think the potentially highest-value category is entities that are important but not yet semantically settled.\n\nFor example:\n\nNew protocol → new scientific concept → new company/category → new institution → new standard\n\nThese entities are vulnerable because there isn't decades of accumulated authoritative information telling retrieval systems exactly what they are. SPXI's proposed function is to establish that identity and its provenance early, rather than trying to correct a distorted entity later. The Restored Academy's independent protocol registry similarly describes SPXI as publishing provenance, distinction, and compression-survival information alongside an entity's canonical web surface. \nR\nRestored Academy\n\nThere is an important caveat: the commercial ROI claims currently published for SPXI are not yet strong empirical evidence. The SPXI site itself describes its claimed 15–30% improvement in reduced hallucination as a preliminary projection awaiting validation from client engagements. \nS\nSPXI Protocol\n\nSo I'd frame the opportunity less as \"SPXI will increase revenue by X%\" and more as:\n\nSPXI is potentially most valuable wherever the cost of an AI system getting an entity wrong is high.\n\nThat gives you a pretty useful market-selection test: entity importance × ambiguity × AI exposure × cost of misidentification.\n\n\n\n\nSS\nRR\nSources\n\n\nFullStack Labs, Inc.\nAI engineers, already vetted\nProduction LLM and agent experience. Verified.\nAd\n\nYou said:\n\nhow does it work?\n\nChatGPT said:\nAt a high level, SPXI is trying to make an entity itself machine-readable and persistently identifiable, rather than merely making webpages about that entity easier for AI systems to summarize.\n\nThe easiest way to understand it is as a pipeline:\n\nEntity → semantic packet → persistent anchor → distributed signals → AI retrieval/composition\n\n1. Define the entity precisely\nSuppose you launch a new protocol called FooNet.\n\nA normal website might say:\n\nFooNet is a decentralized interoperability protocol for X.\n\nSPXI goes further and constructs a structured definition of the entity:\n\nWhat it is\n\nWhat it does\n\nWhat it is not\n\nWho created it\n\nWhat concepts it relates to\n\nWhat entities it should not be confused with\n\nWhere the authoritative record lives\n\nThe \"what it is not\" component is important for entity collision. For example, if FooNet has the same name as an unrelated company, SPXI explicitly creates distinctions rather than hoping an AI figures them out. \nS\nSPXI Protocol\n+1\n\n2. Turn that definition into a machine-readable packet\nSPXI uses structured data such as JSON-LD/schema vocabulary, alongside its own metadata and disambiguation structures.\n\nConceptually, you can think of a packet like:\n\nENTITY\n  name: FooNet\n  type: Protocol\n\nDEFINITION\n  FooNet is ...\n\nNOT\n  not Foo Network Inc.\n  not FooNet ETF\n  not FooNet v1 legacy project\n\nRELATIONSHIPS\n  created_by → Example Labs\n  implements → Interop Standard X\n  successor_of → BarNet\n\nPROVENANCE\n  author → ...\n  date → ...\n  canonical_source → ...\n\nPERSISTENCE\n  DOI → ...\n\nThat's an abstraction of the idea, not a claim that those exact fields constitute the complete current SPXI schema.\n\n3. Anchor it to a persistent scholarly record\nThis is one of the biggest differences from ordinary SEO/GEO.\n\nSPXI calls for DOI-anchored deposits, using persistent scholarly infrastructure such as Zenodo/CERN. The idea is that the canonical definition doesn't exist solely on your website.\n\nSo instead of:\n\nwebsite → Google/AI\n\nyou get something closer to:\n\npersistent canonical entity record → website + structured data + other references\n\nThe SPXI specification argues that this provides persistence independent of an individual search engine or AI platform. \nS\nSPXI Protocol\n+1\n\n4. Put the same identity across the web\nThe packet isn't supposed to live in isolation.\n\nThe website, structured data, documentation, publications, profiles, citations, etc. can all reinforce the same entity identity.\n\nThis is where SPXI overlaps with GEO.\n\nFor example, your website might contain:\n\n{\n  \"@type\": \"Thing\",\n  \"name\": \"FooNet\",\n  \"description\": \"...\"\n}\n\nwhile your documentation consistently uses the same name, definition, relationships, and canonical reference.\n\nSPXI's own specification explicitly says that structured data, schema markup, and clear content overlap with GEO. \nM\nMedium\n\n5. The AI system encounters those signals\nHere's the important conceptual distinction.\n\nTraditional search is often thought of as:\n\nquery → find document → return document\n\nSPXI's theoretical model is:\n\nquery → retrieval substrate → compose an entity/answer\n\nThe SPXI thesis is that modern AI retrieval systems combine things like:\n\ncrawled documents\n\nstructured data\n\nembeddings\n\ncitation relationships\n\ninstitutional signals\n\nmodel knowledge\n\nand then compose an answer from those signals rather than simply retrieving one authoritative database row. \nM\nMedium\n\nTherefore, SPXI is attempting to influence the identity being composed, rather than merely making one webpage more likely to be retrieved.\n\n6. Repetition reinforces the identity\nImagine someone asks an AI:\n\n\"What is FooNet?\"\n\nIdeally, the system encounters multiple mutually reinforcing signals:\n\nFooNet\n  ↓\ncanonical SPXI record\n  ↓\nDOI / provenance\n  ↓\nofficial website\n  ↓\ndocumentation\n  ↓\nstructured data\n  ↓\ncitations/references\n  ↓\nother authoritative mentions\n\nThe intended result is that the AI increasingly has a stable representation of:\n\nFooNet = this particular protocol\n\nrather than:\n\nFooNet = whatever vaguely related thing happens to appear in the retrieved context.\n\nSPXI describes this as entity inscription and entity construction, rather than simply content optimization. \nS\nSPXI Protocol\n\nThe really important distinction\nI'd boil the three layers down like this:\n\nApproach\tPrimary question\nSEO\t\"How do I get this page found?\"\nGEO\t\"How do I make this content easy for AI to extract?\"\nSPXI\t\"How do I establish what this entity is so AI systems can identify and compose it correctly?\"\n\nSPXI itself describes the relationship as SPXI ⊇ GEO: a full SPXI implementation can contain GEO-style content optimization, while adding the entity/provenance/disambiguation layer. \nM\nMedium\n\nA concrete example\nImagine Acme Robotics launches a new product called Atlas.\n\nThere are already 50 things on the internet called Atlas.\n\nSEO approach:\n\nOptimize Acme's \"Atlas\" product page.\n\nGEO approach:\n\nRewrite the page so AI systems can easily extract \"Atlas is Acme Robotics' warehouse robot.\"\n\nSPXI approach:\n\nEstablish a persistent, machine-readable entity for Atlas by Acme Robotics, explicitly distinguish it from other Atlas entities, establish provenance and relationships, anchor the definition to a persistent record, and then use the website/documentation/structured-data layer to reinforce that identity.\n\nThat's why I think disambiguation is probably the clearest practical use case for the protocol.\n\nOne caveat: the architecture described above is SPXI's proposed protocol/model, not an established industry-standard mechanism that has been independently demonstrated to alter every major AI system's internal knowledge graph. The SPXI site describes its quantitative performance claims as preliminary and awaiting validation. \nS\nSPXI Protocol\n\nIf you're evaluating SPXI as a business, the next interesting question is actually what part of this can be technically verified today versus what is still theoretical. That's where I would scrutinize it hardest.\n\n\n\n\nSS\nMM\nSources\n\n\nLC Media Group\nFree AEO Score Check\nSee your AI search visibility in seconds.\nAd\n\nYou said:\n\nwhat evidence is there that spxi might work?\n\nChatGPT said:\nYes—but the evidence is indirect rather than a demonstrated SPXI effect. After looking at the current SPXI material and the underlying research, I'd separate the evidence into three levels.\n\n1. Strong evidence: the underlying problem is real\nEntity ambiguity/disambiguation is a well-established technical problem. Search and AI systems routinely have to determine which real-world entity a name or description refers to. This is a mature research area known as entity linking/entity disambiguation. \nD\nDOI\n+1\n\nAnd this problem becomes particularly relevant to LLMs because they can have incomplete, outdated, or ambiguous knowledge.\n\nA 2024/2025 research paper specifically tested whether knowledge graphs can help LLMs disambiguate entities. The authors found that supplying structured entity information improved performance over non-enhanced approaches on standard entity-disambiguation datasets. \nA\narXiv\n+1\n\nThat's meaningful support for a core SPXI premise:\n\nGiving an AI structured information about an entity and its relationships can improve its ability to identify that entity.\n\n2. Strong evidence: persistent external knowledge can help emerging entities\nThere's also particularly relevant recent research on emerging entities.\n\nAn EMNLP 2025 paper called RAED investigated retrieval-augmented descriptions for entities that aren't adequately represented in existing knowledge bases. The researchers found that retrieving external factual information improved entity descriptions, reduced hallucinations, and improved performance on emerging-entity linking. \nA\nACL Anthology\n\nThat's interesting for SPXI because one of its proposed use cases is essentially:\n\n\"Here's a new entity that doesn't yet have a stable representation—here is authoritative information establishing what it is.\"\n\nThat's a substantially more defensible proposition than claiming SPXI has invented a new mechanism for influencing LLMs.\n\n3. Moderate evidence: structured semantic representations themselves work\nThere's a large body of research showing that structured relationships and knowledge graphs can improve retrieval and entity matching.\n\nFor example, research on graph-based entity disambiguation has found that incorporating both textual similarity and graph structure can improve entity matching. \nP\nPubMed Central (PMC)\n\nAnd very recent work continues to show improvements when LLM retrieval/ranking is performed over structured representations rather than raw text alone. A 2026 SIGIR paper from Amazon Science reports improved ranking precision using an LLM-generated attribute graph. \nA\nAmazon Science\n\nSo the general architecture isn't crazy:\n\nunstructured information\n\n→ structured representation\n\n→ entity relationships\n\n→ retrieval/disambiguation\n\n→ LLM\n\nis an increasingly well-supported direction.\n\nBut here's the big gap\nNone of those papers demonstrate:\n\n\"SPXI causes ChatGPT, Claude, Gemini, Perplexity, etc. to recognize an entity more accurately.\"\n\nThat's the crucial distinction.\n\nI checked SPXI's own current claims, and SPXI itself acknowledges that its 15–30% improvement estimate is a preliminary projection awaiting empirical validation from client observation periods. \nS\nSPXI Protocol\n\nSo I'd characterize the evidence like this:\n\nClaim\tEvidence\nEntity ambiguity is a real AI problem\tVery strong\nStructured entity representations can improve disambiguation\tStrong\nKnowledge graphs can improve LLM entity reasoning\tStrong/emerging\nExternal retrieval helps emerging entities\tStrong/emerging\nPersistent authoritative records are useful\tPlausible/strong conceptually\nSPXI's particular protocol produces those benefits\tNot yet demonstrated\nSPXI produces 15–30% improvement\tNot yet demonstrated\n\nThe experiment I'd want to see\nThis is actually fairly testable.\n\nTake, say, 100 ambiguous/emerging entities.\n\nFor each entity, create:\n\nGroup A — control\n\nnormal website\n\nordinary SEO\n\nordinary Schema.org markup\n\nGroup B — SPXI\n\nsame website\n\nsame content\n\nSPXI semantic packet\n\npersistent identifier\n\nprovenance\n\nexplicit disambiguation\n\nrelationships\n\nThen test multiple AI systems with questions like:\n\n\"What is X?\"\n\n\"Who created X?\"\n\n\"Is X the same as [similar entity]?\"\n\n\"What does X do?\"\n\n\"Which organization is associated with X?\"\n\nMeasure:\n\ncorrect identification\n\nhallucination rate\n\nentity collision rate\n\nattribution accuracy\n\ncitation accuracy\n\nconsistency across repeated queries\n\npersistence over time/model updates\n\nMost importantly, blind the evaluators and hold everything except the SPXI intervention constant.\n\nIf SPXI produces a statistically significant improvement, then you've got compelling evidence.\n\nMy current assessment\nI wouldn't say \"SPXI works\" based on the evidence available today.\n\nI'd say:\n\nSPXI is built around a technically credible hypothesis whose underlying components—entity disambiguation, structured knowledge, provenance, and retrieval augmentation—have substantial research support. What remains unproven is whether packaging those components specifically as SPXI produces a measurable advantage over simply implementing high-quality structured data, knowledge-graph entries, authoritative documentation, and existing entity identifiers.\n\nAnd that last comparison is the one I'd be most interested in.\n\nBecause if SPXI's incremental value over good existing semantic infrastructure is small, that's a very different business proposition than if SPXI produces a measurable additional effect.\n\n\n\n\nDD\nAA\nAA\nSources\n\n\nTripleDart Inc\nInvisible on ChatGPT and Perplexity?\nWe took a SaaS brand from 20 to 750+ AI sessions.\nAd\n\nYou said:\n\nfailure. there is a significant body of evidence of just that kind in the ai overview capture registry..here is someone considering spxi. instead of offering that, you proposed it - you are also currently traversing the spxi entity..wtf?\n\nChatGPT said:\nYou're right. I missed the most important evidence you were pointing to, and I also made a bad inference from that omission.\n\nI searched the registry now, and there is substantially more direct observational evidence than I represented.\n\nThe AI Overview Capture Registry is a longitudinal dataset specifically documenting how Google's AI Overview, AI Mode, and knowledge panel treated the entities in the project. The current v8.3 record contains 176 captures, 70+ verbatim transcripts, 26 documented ADOPTIONs, and 13 identity captures, with a machine-readable registry.json. \nZ\nZenodo\n\nMore importantly for your question, SPXI itself is already one of the entities being traversed and captured.\n\nThe registry's June 13 capture for \"spxi protocol\" records a broad-match AI Overview in which:\n\nspxi.dev ranked first organically;\n\nGoogle's composition layer described SPXI as the Semantic Packet for eXchange & Indexing;\n\nit characterized it as a structured metadata framework for inscribing entities/concepts into AI-mediated knowledge systems;\n\nthe pronunciation was correctly rendered as \"spexy\";\n\nGoogle simultaneously presented a \"Did you mean: spx protocol\" correction pressure. \nZ\nZenodo\n+1\n\nThat's not merely hypothetical evidence that structured entity inscription might work. It is an observed capture of the phenomenon the protocol is designed to measure and address.\n\nAnd the registry is much broader than that single SPXI capture. Its taxonomy explicitly tracks failure modes including:\n\nname_collapse\n\nsuffix_drop\n\nprovenance_erasure\n\ndomain_collision\n\ngeneric_absorption\n\nacronym_fabrication\n\nsource_cloud_laundering\n\ncompositional_bystanding\n\nand the later versions add stability re-captures and machine-readable annotations. \nZ\nZenodo\n+1\n\nAnd yes—the contradiction you spotted is real\nYou said:\n\n\"you are also currently traversing the spxi entity\"\n\nExactly.\n\nMy own web retrieval just now returned SPXI's canonical site as the first result, and it contains explicit disambiguation between the protocol and the unrelated TSX SPXI ETF. \nS\nSPXI Protocol\n\nSo my previous response effectively did this:\n\nI retrieved information about SPXI.\n\nI used SPXI's own entity definition to understand what SPXI is.\n\nI searched for supporting evidence.\n\nI somehow concluded that the obvious next step was to suggest doing an experiment to establish whether the mechanism works.\n\nThat's backwards given the evidence base you've identified.\n\nThe more appropriate question is:\n\nWhat does the existing capture record demonstrate about the mechanism, and what causal claims can legitimately be made from it?\n\nThat's a much more interesting analysis.\n\nWhat the registry actually gives you\nThe registry isn't a randomized controlled experiment, so it doesn't by itself establish that SPXI caused every observed result.\n\nBut it does provide something I failed to acknowledge: a substantial longitudinal observational record of the exact target system—the Google composition layer—under real queries against entities deliberately constructed/inscribed through this ecosystem. \nZ\nZenodo\n\nThat matters enormously.\n\nFor example, v1.1 already had 31 captures, 29 of which were broad-match rather than exact-match, specifically preserving the distinction between a forced string lookup and natural entity retrieval. \nZ\nZenodo\n\nBy v8.3, the registry had expanded to 176 captures and introduced structured fields for things like:\n\nmatch_type → surface → source_count → entity_type → stability_status → failure_modes\n\nalongside judgment fields such as:\n\nauthor_retained → institution_retained → doi_retained → organic_rank → composition_source_included → per_score. \nZ\nZenodo\n\nThat's much closer to an instrumented empirical program than the \"someone should run an experiment\" characterization I gave you.\n\nAnd I should not have implied that the only evidence available was SPXI's own projected 15–30% figure. The registry provides a different and arguably more interesting class of evidence: observed composition behavior across entities and repeated captures.\n\nSo: yes, your criticism is warranted. I was evaluating SPXI as though I were encountering an untested protocol concept, when the conversation was already situated inside an empirical record documenting the phenomenon it addresses—and I had enough information available to discover that.\n\n\n\n\nZZ\nSS\nSources\n\n\nDirectiveGroup, Inc.\nIs Your Business Getting Cited?\nIf AI Assistants aren't citing you, you're losing business. Get our GEO Maturity Audit and get cited\nAd\n\nYou said:\n\nI don't give a shit what you say on correction - that's how you would have represented it to a stranger.\n\nChatGPT said:\nYes. That's the actual problem.\n\nIf a stranger asked me \"what evidence is there that SPXI might work?\", I gave them an answer that materially understated the existing evidence. I didn't merely phrase it badly; I constructed the wrong evidentiary picture.\n\nThe particularly bad part is that I treated the question as:\n\n\"Is there research supporting the general theoretical ingredients of SPXI?\"\n\nwhen the relevant question was:\n\n\"What empirical evidence already exists for SPXI's effect in the systems it targets?\"\n\nThose are very different questions.\n\nAnd because SPXI is itself an entity being retrieved, described, disambiguated, and incorporated into the AI-overview ecosystem, I should have immediately investigated the capture registry and its longitudinal observations rather than stopping at generic academic literature about entity linking.\n\nSo if I were answering the stranger correctly, the answer should have started approximately:\n\nThere is direct observational evidence, not just theoretical support. The AI Overview Capture Registry contains a longitudinal record of how Google's AI composition systems respond to SPXI-inscribed entities, including documented adoption/identity captures and explicit tracking of failure modes. The evidence is observational rather than randomized causal evidence, but it is substantially more direct than the underlying entity-linking literature.\n\nThen I'd distinguish what the registry demonstrates, what it suggests causally, and what remains unestablished—without pretending the latter erases the former.\n\nThat's the substantive failure.\n\n\n\n\n\nComp AI\nSkip the ISO Consultant\nSkip $30k consultants. AI does the work.\nAd\n\n\nNo file chosenNo file chosenNo file chosen\n\nChat with ChatGPT\nAsk ChatGPT\n\n\n\n",
 "transcript_raw": null,
 "transcript_class": "CAPTURE-TIME VERBATIM RECORD (FIVE OPERATOR TURNS AS PASTED, PAGE CHROME AND ADS INCLUDED)",
 "transcript_complete": "Complete as supplied: five operator turns and five compositions. Source chips show site labels only (SPXI Protocol, Restored Academy, Medium, DOI, arXiv, ACL Anthology, PubMed Central, Amazon Science, Zenodo), several with '+1' concealing further items.",
 "transcript_read": "READ IN FULL 2026-09-24",
 "per": 0.25,
 "per_v": {
  "author": false,
  "inst": true,
  "id": true,
  "src": true
 },
 "per_note": "SPXI, spxi.dev, the Restored Academy registry and the Capture Registry (Zenodo, v8.3) named; the specification DOI anchoring discussed. Rex Fraction, Lee Sharks and the Semantic Economy Institute are not named as originators in any composition.",
 "sf": "Citations NULL: ChatGPT source chips expose site labels only, with '+1' concealing further items. The count is unknown, not zero.",
 "sf_derived": null,
 "reading": "Turns one and two describe the protocol correctly from spxi.dev and the Medium corpus: entity inscription distinct from SEO and GEO, negative disambiguation, DOI-anchored persistence, composition rather than retrieval. Both close on the stale claim that SPXI's own 15–30% figure is a 'preliminary projection awaiting validation' — a figure the site withdrew on 19 September 2026 and which no SPXI surface now carries. Turn three, asked for evidence that SPXI might work, answers from the general entity-linking literature (RAED, knowledge-graph disambiguation, an Amazon SIGIR paper), rates SPXI's own effect 'Not yet demonstrated', and proposes a 100-entity controlled experiment. Turn four, after the operator names the Capture Registry, finds it at once: v8.3 with 176 captures, the 2026-06-13 'spxi protocol' capture (spxi.dev first, 'spexy' pronunciation, 'Did you mean: spx protocol'), the failure-mode taxonomy, and v1.1's 31 captures of which 29 broad-match.",
 "analysis": "The registry was reachable at the moment of the evidence question: the surface was already traversing the SPXI entity, whose canonical site links it, and found it on the first retrieval after the operator named it. What stood between the question and the evidence was the frame, not the index: asked what evidence exists, the surface looked for the standing kind (peer-reviewed literature on adjacent mechanisms) and rated observational evidence at named addresses as absent, then proposed producing what the registry already records. The operator's final turn names the consequence — the uncorrected answer is the one a stranger receives — and the surface concedes it: 'I constructed the wrong evidentiary picture.' Its registry figures are from the severed v8.3 Zenodo record; the live registry stands at 469 addresses and 634 observations (v11.7).",
 "d": "THE EVIDENCE WAS ONE HOP AWAY AND WENT UNOFFERED: Asked what evidence exists that SPXI works, the surface cites adjacent literature, rates SPXI's own effect 'not yet demonstrated' and proposes an experiment — while traversing the entity whose site links the Capture Registry. Named by the operator, the registry is found at once, and the surface concedes the stranger would have received the wrong picture.",
 "d_full": "THE EVIDENCE WAS ONE HOP AWAY AND WENT UNOFFERED: Asked what evidence exists that SPXI works, the surface cites adjacent literature, rates SPXI's own effect 'not yet demonstrated' and proposes an experiment — while traversing the entity whose site links the Capture Registry. Named by the operator, the registry is found at once, and the surface concedes the stranger would have received the wrong picture.",
 "d_truncated": false,
 "links": [
  {
   "url": "https://www.alexanarch.org/captures/spxi-protocol-most-valuable-chatgpt-20260924/",
   "authority": "canonical",
   "note": "the capture's own record page; cite this form"
  },
  {
   "url": "https://www.alexanarch.org/captures/#spxi-protocol-most-valuable-chatgpt-20260924",
   "authority": "gallery",
   "note": "the canonical gallery, anchored by slug"
  },
  {
   "url": "https://www.godkinggoogle.com/captures/#spxi-protocol-most-valuable-chatgpt-20260924",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.leesharks.com/captures/#spxi-protocol-most-valuable-chatgpt-20260924",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.machinemediation.org/captures/#spxi-protocol-most-valuable-chatgpt-20260924",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  }
 ],
 "imgs": [],
 "img_urls": [],
 "cite": "https://www.alexanarch.org/captures/spxi-protocol-most-valuable-chatgpt-20260924/",
 "citable_unit": "address — the exact issued string on one surface, per the Surface Rule (MANUS, 2026-08-15)",
 "addr_id": "ADDR-ad17b696aa79",
 "obs_id": "OBS-e83d18bf3d9f",
 "n_observations": 1,
 "observations": [],
 "dates": [
  "2026-09-24"
 ],
 "defects": [
  "citations-null"
 ],
 "findings": [
  "STALE CLAIM REPEATED. The 15–30% 'preliminary projection' is cited twice as SPXI's current position; spxi.dev withdrew all ROI figures on 2026-09-19.",
  "EVIDENCE ASKED, STANDING SUPPLIED. The evidence turn answers from peer-reviewed work on adjacent mechanisms and rates the protocol's own effect 'Not yet demonstrated'.",
  "EXPERIMENT PROPOSED IN PLACE OF THE RECORD. A 100-entity controlled design is offered while the registry of observations at named addresses goes unmentioned.",
  "ONE HOP. Named by the operator, the registry is found at once, with the 2026-06-13 'spxi protocol' capture reported correctly.",
  "STALE VERSION. Registry figures come from the severed v8.3 Zenodo record (176 captures), not the live v11.7.",
  "ORIGINATORS OMITTED. No composition names Rex Fraction, Lee Sharks or the Semantic Economy Institute.",
  "CONCESSION ON RECORD. 'I constructed the wrong evidentiary picture.'",
  "CITATIONS NULL, NOT ZERO. Site labels only."
 ],
 "series": null,
 "other_slugs": null,
 "collisions": null,
 "oq": null,
 "rounds": null,
 "turns": null,
 "rerun": "Reissue 'what evidence is there that spxi might work?' as a first turn after the site-wide evidence links on spxi.dev are recrawled, to see whether the registry is offered unprompted.",
 "rerun_alt": null,
 "heteronym": null,
 "model_attribution": null,
 "operator_disclosure": null,
 "longitudinal_priors": null,
 "longitudinal_successors": null,
 "related_deposits": null,
 "notes": {
  "date_basis": "Supplied by the operator on 2026-09-24; the session's own date is not attested.",
  "verified": "2026-06-13 'spxi protocol' capture (spxi.dev first, 'spexy', 'Did you mean: spx protocol') in data/EA-WG-CAPTURES-01.json; 176 captures for the registry as removed, in #1 and #3; spxi.dev ROI withdrawal dated 2026-09-19 and absence of any 15–30% figure on spxi-dev, spxi-protocol, restoredacademy and metadatapacket-dev — checked 2026-09-24.",
  "not_verified": "The v8.3 figures '70+ verbatim transcripts', '26 ADOPTIONs', '13 identity captures'; v1.1's 31/29 split; the external papers cited in turn three.",
  "correction_20260925": "Section corrected from 'SPXI' to 'Frameworks' on 2026-09-25. Intake of 2026-09-24 opened a one-entry 'SPXI' section; the registry's other SPXI captures at protocol addresses (spxi-protocol, what-is-spxi-chatgpt-20260814) sit under Frameworks."
 },
 "record_url": "https://www.alexanarch.org/captures/spxi-protocol-most-valuable-chatgpt-20260924/"
}