{
 "axn": "AXN:020C.EMPIRICAL.🌾⚪⏏️🌿♉🏁",
 "root_axn": "AXN:020C.EMPIRICAL",
 "hex": "020C",
 "family": "EMPIRICAL",
 "emoji": "🌾⚪⏏️🌿♉🏁",
 "hash": "1ac7f817aaf03f03d115b98b920a00cab81029c48a3f20807409beb9cf26acbf",
 "title": "SPXI Is Not GEO: A Technical Distinction — EA-SPXI-09",
 "creator": "Rex Fraction",
 "orcid": "0009-0000-1599-0703",
 "date": "2026-04-16",
 "description": "EA-SPXI-09 distinguishes the Semantic Packet for eXchange & Indexing from Generative Engine Optimization by object, layer, mechanism, and intended durability. The preserved v1 text treats GEO as a content-layer practice that improves extractability, answer inclusion, and citation, while SPXI operates on entity definition through structured packets, disambiguation matrices, Semantic Integrity Markers, DOI-linked provenance, and pre/post-deployment measurement.\n\nAn April 18 amendment corrects the retrieval layer’s over-reading of that distinction. The refined relation is **SPXI ⊇ GEO**: SPXI is not reducible to GEO, but may contain GEO techniques as part of a broader entity-construction and provenance architecture. The amendment therefore preserves the original non-equivalence claim while rejecting mutual exclusion. The document should be described as a versioned technical distinction whose own retrieval reception forced a formal correction, not as a static v1 specification.",
 "content_type": "Canonical technical specification",
 "license": "CC-BY-4.0",
 "substrate": "Various",
 "keywords": [
  "a technical distinction",
  "entity construction",
  "entity collision",
  "model dependency",
  "semantic economy",
  "ai overview",
  "distinction",
  "inscription"
 ],
 "version": "v1.0",
 "deposit_number": 661,
 "sovereign_id": "MM-CHA-0520",
 "minted_at": "2026-06-20T22:00:00Z",
 "status": "ACTIVE",
 "clusters": [
  "Elemental",
  "Signal",
  "Terminal",
  "Elemental",
  "Alchemical",
  "Terminal"
 ],
 "reading": "Force → Alarm → Closure → Force → Transmutation → Closure",
 "axn_canonical": "1ac7f817aaf03f03d115b98b920a00cab81029c48a3f20807409beb9cf26acbf",
 "axn_display": "🌾⚪⏏️🌿♉🏁",
 "mirrors": {
  "blog": "https://mindcontrolpoems.blogspot.com/2026/04/ea-spxi-09-spxi-is-not-geo-technical.html"
 },
 "zenodo_dois": [
  "10.5281/zenodo.19637488",
  "10.5281/zenodo.19637246",
  "10.5281/zenodo.19637500"
 ],
 "full_text_path": "/data/texts/AXN-020C-text.md",
 "full_text_chars": 14163,
 "wiki_article": "**SPXI Is Not GEO** is a technical distinction in the SPXI Protocol series, authored by Rex Fraction for the Semantic Economy Institute. It compares Generative Engine Optimization, which structures existing content for extraction by AI summarizers, with SPXI, which attempts to construct and stabilize entity-definition objects across retrieval surfaces.\n\nThe original version distinguishes the two practices by their unit of intervention. GEO works on pages, prose, schema, and citation-oriented content. SPXI works on persons, organizations, concepts, frameworks, and other entities by combining positive definitions, negative disambiguation, persistent references, structured data, and measurement. The document accepts that the two practices share tools such as JSON-LD, schema markup, clear definitions, and dense factual prose.\n\nAfter indexing, the author added a v2 amendment because generated comparisons began treating the practices as mutually exclusive and assigning commercial returns to GEO while reserving only structural outcomes for SPXI. The amendment states that SPXI contains GEO methods as a proper subset when content-layer work is required. EA-SPXI-09 is consequently both a specification and an example of retrieval-layer correction: a distinction was successfully installed, then refined when its compressed form became too rigid.",
 "entities": [
  {
   "subject": "EA-SPXI-09",
   "predicate": "created_by",
   "object": "Rex Fraction",
   "type": "work",
   "evidence_status": "observed"
  },
  {
   "subject": "EA-SPXI-09",
   "predicate": "is_type",
   "object": "Archive work",
   "type": "work",
   "evidence_status": "observed"
  },
  {
   "subject": "EA-SPXI-09",
   "predicate": "belongs_to_family",
   "object": "EMPIRICAL",
   "type": "work",
   "evidence_status": "observed"
  },
  {
   "subject": "EA-SPXI-09",
   "predicate": "is_part_of",
   "object": "Crimson Hexagonal Archive",
   "type": "work",
   "evidence_status": "observed"
  },
  {
   "subject": "EA-SPXI-09",
   "predicate": "engages",
   "object": "Semantic Economy",
   "type": "concept",
   "evidence_status": "inferred"
  },
  {
   "subject": "Citation formatting",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Structuring references in ways that summarizers are more likely to preserve."
  },
  {
   "subject": "Construct entities",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "GEO optimizes existing content about an existing entity. If the entity does not yet exist in the kno"
  },
  {
   "subject": "Content clarity",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Both benefit from clear, authoritative prose that summarizers prefer to extract."
  },
  {
   "subject": "Cross-platform deployment",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Distribution of entity signals across multiple surfaces (Zenodo, GitHub, Medium, LinkedIn, corporate"
  },
  {
   "subject": "DOI-anchored deposits",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Permanent, institutionally preserved artifacts (Zenodo/CERN) that cannot be silently altered, deprec"
  },
  {
   "subject": "Definition-lead sentences",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Structuring content so that the first sentence of a section provides a clear, extractable definition"
  },
  {
   "subject": "Disambiguation matrices",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Positive definitions, negative tags, and boundary conditions that specify what the entity is, what i"
  },
  {
   "subject": "Encyclotron measurement",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Pre- and post-deployment audits that measure whether the entity has been accurately inscribed."
  },
  {
   "subject": "Entity definition blocks",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Structured data assemblies (JSON-LD, schema.org) that declare the identity, type, provenance, and bo"
  },
  {
   "subject": "FAQ markup",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Using schema.org FAQ structures to provide question-answer pairs that summarizers can extract direct"
  },
  {
   "subject": "Fact density",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Increasing the ratio of verifiable claims to prose volume, making content more useful to summarizers"
  },
  {
   "subject": "Fluency optimization",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Writing in a register that summarizers prefer to reproduce — clear, authoritative, low-ambiguity pro"
  },
  {
   "subject": "GEO answers",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "\"How do I make my existing content more visible to the AI?\""
  },
  {
   "subject": "GEO approach",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Optimize the company's existing blog posts, product pages, and FAQ sections for summarizer extractio"
  },
  {
   "subject": "Resolve entity collision",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "GEO does not include mechanisms for declaring what an entity is *not*. If a summarizer confuses two "
  },
  {
   "subject": "Resolves entity collision",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "The disambiguation matrix explicitly declares what the entity is not, providing the retrieval system"
  },
  {
   "subject": "SPXI answers",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "\"How do I make my entity exist in the AI's knowledge graph, permanently and accurately?\""
  },
  {
   "subject": "SPXI approach",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Build the company's entity definition from scratch. Deposit a disambiguation matrix that distinguish"
  },
  {
   "subject": "Schema markup",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Both deploy machine-readable structured data in page headers."
  },
  {
   "subject": "Structured data",
   "predicate": "minted_in",
   "object": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "type": "concept",
   "evidence_status": "observed",
   "note": "Both use schema.org vocabulary and JSON-LD encoding."
  }
 ],
 "journal": "Journal of Compression Studies",
 "cited_by": [
  {
   "deposit": 61,
   "axn": "AXN:0210.GOVERNANCE.🤙🖊️🔭🍀🖐️🕊️"
  },
  {
   "deposit": 72,
   "axn": "AXN:022F.GOVERNANCE.🔒👐🎺⛳✏️🔔"
  },
  {
   "deposit": 89,
   "axn": "AXN:0260.GOVERNANCE.🌲🕙☁️🕔●🔜"
  },
  {
   "deposit": 173,
   "axn": "AXN:030B.GOVERNANCE.🔎🎵🤲🫵🧫🏷️"
  },
  {
   "deposit": 174,
   "axn": "AXN:0310.GOVERNANCE.🌋🕔🌓🛡️🗝️🖐️"
  }
 ],
 "references_concepts": [
  "Citation formatting",
  "Construct entities",
  "Content clarity",
  "Cross-platform deployment",
  "DOI-anchored deposits",
  "Definition-lead sentences",
  "Disambiguation matrices",
  "Encyclotron",
  "Encyclotron measurement",
  "Entity definition blocks",
  "FAQ markup",
  "Fact density",
  "Fluency optimization",
  "GEO (Generative Engine Optimization)",
  "GEO answers",
  "GEO approach",
  "Model dependency",
  "Positive definitions",
  "Resolve entity collision",
  "Resolves entity collision",
  "Rex Fraction",
  "SIM presence",
  "SPXI answers",
  "SPXI approach",
  "Schema markup",
  "Semantic Economy",
  "Semantic Economy Institute",
  "Semantic Integrity Markers",
  "Semantic Integrity Markers (SIMs)",
  "Structured data",
  "The AI",
  "The Semantic Economy Institute",
  "Verifiability"
 ],
 "defines_concepts": [
  "Cross-platform deployment",
  "DOI-anchored deposits",
  "Citation formatting",
  "Construct entities",
  "Content clarity",
  "Definition-lead sentences",
  "Disambiguation matrices",
  "Encyclotron measurement",
  "Entity definition blocks",
  "FAQ markup",
  "Fact density",
  "Fluency optimization",
  "GEO answers",
  "GEO approach",
  "Resolve entity collision",
  "Resolves entity collision",
  "SPXI answers",
  "SPXI approach",
  "Schema markup",
  "Structured data"
 ],
 "references_concept_count": 33,
 "external_metadata_path": "/data/external-metadata/AXN-020C.json",
 "openalex_ids": [
  "https://openalex.org/W7154825390",
  "https://openalex.org/W7154842732",
  "https://openalex.org/W7154833069"
 ],
 "datacite_severance": "severed",
 "body_status": {
  "class": "full",
  "lacuna": false,
  "recovery_status": "COMPLETE",
  "residual_chars": 12974,
  "audited_at": "2026-07-17T04:49:17.789813Z",
  "audit_version": "v3-dual-store+recovery-map",
  "measured_prose_words": 1877,
  "measured_at": "2026-07-31"
 },
 "title_repair_log": [
  {
   "at": "2026-07-28T15:20:20Z",
   "defect": "registry_title_diverged_from_published_form",
   "was": "EA-SPXI-09: SPXI Is Not GEO A Technical Distinction",
   "now": "SPXI Is Not GEO: A Technical Distinction — EA-SPXI-09",
   "basis": "Set verbatim to the title this work carried at Zenodo, from data/doi-resolution-index.json (10.5281/zenodo.19614871, direct_verified, word overlap 1.00). The recovered metadata is the published form of record; the registry title was a variant."
  }
 ],
 "canonical_text_status": "canonical_full_text",
 "modifications": [
  {
   "date": "2026-08-01",
   "field": "content_type",
   "reason": "Wave 1 repair: audit ledger v1.1 recommended_content_type (workplan v1.5 §6 W1, MANUS batch approval 2026-08-01)",
   "was": "Archive work",
   "now": "Canonical technical specification"
  },
  {
   "date": "2026-08-01",
   "field": "journal",
   "reason": "Wave 6 venue normalization: full canonical journal name per MANUS ruling 2026-08-01 (venues.json authority)",
   "was": "MMRS",
   "now": "Machine-Mediated Reception Studies (MMRS)"
  },
  {
   "date": "2026-08-04",
   "field": "publisher",
   "reason": "PUB-POPULATE: dc:publisher from venues.json v1.1 press mapping (CP-R3 RULED-EXTENDED 2026-08-01); Alexanarch = publisher of record where no imprint applies",
   "now": "Pergamon Press"
  },
  {
   "date": "2026-08-04",
   "field": "status",
   "reason": "W12 STATUS-VOCABULARY v1.0 (MANUS ratified 2026-08-04): controlled vocabulary {ACTIVE, SUPERSEDED, WITHDRAWN, DRAFT}; MINTED_UNREVIEWED false on a 100%-audited corpus; freetext annotations preserved losslessly in body_status.status_note",
   "was": "MINTED_UNREVIEWED",
   "now": "ACTIVE"
  },
  {
   "date": "2026-08-05",
   "field": "description",
   "reason": "DW-??? intake (LABOR-prepared, TACHYON-verified: AXN match + factual probes vs record body)",
   "was": "Since this post was first published and indexed, the retrieval layer’s composition of “SPXI vs GEO ROI” has over-converged on non-equivalence. AI Overview compositions began assigning GEO all financial ROI (attributed revenue, CAC reduction, sales cycle velocity) and assigning SPXI only structural outcomes (durability, efficiency).",
   "now": "EA-SPXI-09 distinguishes the Semantic Packet for eXchange & Indexing from Generative Engine Optimization by object, layer, mechanism, and intended durability. The preserved v1 text treats GEO as a content-layer practice that improves extractability, answer inclusion, and citation, while SPXI operates on entity definition through structured packets, disambiguation matrices, Semantic Integrity Markers, DOI-linked provenance, and pre/post-deployment measurement.\n\nAn April 18 amendment corrects the retrieval layer’s over-reading of that distinction. The refined relation is **SPXI ⊇ GEO**: SPXI is not reducible to GEO, but may contain GEO techniques as part of a broader entity-construction and provenance architecture. The amendment therefore preserves the original non-equivalence claim while rejecting mutual exclusion. The document should be described as a versioned technical distinction whose own retrieval reception forced a formal correction, not as a static v1 specification."
  }
 ],
 "date_modified": "2026-08-05",
 "publisher": "Pergamon Press",
 "journal_assignment": {
  "assigned": "2026-08-15",
  "by": "TACHYON under operator adjudication",
  "pass": 5,
  "method": "read per deposit — title and content_type, one at a time. No script classified anything.",
  "previous": "Machine-Mediated Reception Studies (MMRS)",
  "supersedes": "the 2026-06-21 preliminary batch mapping (#866), which assigned 864 deposits and put 371 in one venue",
  "authority": "data/cha-journals.json · datasets/venues/records/"
 },
 "line": "capture-and-reception",
 "line_parent": "science",
 "line_basis": "derived",
 "_projection": {
  "note": "Derived file. Canonical machine record is this entry in data/registry.json; the human record is the record_url. Do not edit this file.",
  "record_url": "https://www.alexanarch.org/s/records/661/",
  "self_url": "https://www.alexanarch.org/data/records/661.json",
  "registry_url": "https://www.alexanarch.org/data/registry.json",
  "text_url": "https://www.alexanarch.org/data/texts/AXN-020C-text.md",
  "oai_pmh": "https://www.alexanarch.org/oai?verb=Identify"
 }
}