AXN:09F1.CAPTURE

AXN:09F1.CAPTURE.🌺🎪🔴♉🔔☉

Observation

Google AI Overview, 2026-10-17 · the capture

Description

SPXI AGAINST AEO: asked how SPXI differs from AEO, the AI Overview answers with a four-row table — AEO 'Content Extractability', 'Ongoing / Fluid', 'AI Citations'; SPXI 'Knowledge Graph Structure', 'Permanent: Relies on immutable, DOI-anchored… records', 'Canonical Entity Recognition' — that is semanticeconomy.org's 'Not SEO. Not GEO. SPXI.' table of before September row for row ('Time horizon | Ongoing | Ongoing | Permanent (DOI-anchored)'), on a page noindex since 2026-09-04. The current brief it cites says 'durable' and 'identifier-anchored (AXN; historical Zenodo DOIs preserved)'. Six of eight sources are AEO marketing explainers; SPXI ≠ AEO (#1681) appears only through a Medium snippet.

Reading

The innocent reading first: AEO 'optimizes text and web formatting so conversational AI engines can easily extract answers'; SPXI 'establishes a permanent, canonical knowledge structure that AI engines recognize as a master reference'; AEO is 'execution', SPXI 'architecture'. The table is semanticeconomy.org's home of before September, row for row. Its 'Why this is different — Not SEO. Not GEO. SPXI.' table (kept in the repository as index_v2_backup.html; noindex since 2026-09-04): 'What it builds | Rankings | AI citations | Entities the AI recognizes as canonical'; 'Target | Keywords | Content extractability | Knowledge graph structure'; 'Time horizon | Ongoing | Ongoing | Permanent (DOI-anchored)'. The Overview: Core Goal '…AI engines recognize as a master reference'; Target Layer 'Content Extractability' / 'Knowledge Graph Structure'; Persistence Horizon 'Ongoing / Fluid' / 'Permanent: Relies on immutable, DOI-anchored… records'; Success Metric 'AI Citations' / 'Canonical Entity Recognition'. The old table's GEO/AEO column is the Overview's AEO column. The current surfaces it cites say otherwise in two places. The Canonical Entity Brief: 'Identifier-anchored deposits in Alexanarch (AXN; historical Zenodo DOIs preserved)' and 'durable retrieval-layer presence'; spxi.dev since 2026-09-23 says durable entity inscription, and since 2026-09-29 persistent-identifier anchored (DOI and AXN). The Overview keeps 'Permanent', 'immutable' and 'Zenodo records', and adds 'unalterable'. 'Semantic labor and identifier-anchored data deposits' joins the brief's 'Correct concepts (Semantic Labor, Rent, Override)' to its deposits. The one source that names the distinction as the archive argues it — The Crown and the Practice on Medium: 'SPXI is a practice the archive defines against AEO (EA-SPXI-AEO-01)' — supplies a sentence; SPXI ≠ AEO's own terms (inscription by discernment, #1681) do not enter the answer. The AEO side is six marketing explainers.

Analysis

On the Overview, the comparison question of 2026-10-14 is answered from semanticeconomy.org's comparison table as it stood before September — its target and time-horizon rows, 'Permanent (DOI-anchored)' — though the page is noindex since 2026-09-04 and the cited brief now says durable and identifier-anchored. SPXI ≠ AEO's success condition, inscription by discernment, is absent. Seated 2026-10-17 from the operator's paste.

Match

BROAD MATCH — SPXI AGAINST AEO FROM THE SEPTEMBER TABLE — 'PERMANENT (DOI-ANCHORED)'

PER

0.25 — Retained: the institution (by the semanticeconomy.org source; leadership named in its snippet) and visible sources. Lost: the author in the answer, any identifier; SPXI ≠ AEO (EA-SPXI-AEO-01, #1681) named only inside the Medium snippet.

Citations

8 (0 archive-controlled)

Sealed observation

/data/captures/sealed/spxi-protocol-different-from-aeo-aio-20261017.json — SHA-256 7185c1aa2ea73c3263be9746ac47dafe4af62f19e538f825c86116a5aac5e333

Relations

Read from the fields that record them (/data/axn-relations.json); a hash names bytes and supplies no relation.

Drew on

• AXN:06DF.EMPIRICAL.🔄👇🧪🌘◀️📝 — The Crown and the Practice: Answer Engine Optimization across the King of AEO Crystallization (SEVP-VAL-002 v0 (card resolved at intake (title); REL-e1ee4be2abed)