AXN:022F.GOVERNANCE.⌛♆📚💧➕🕌

SPXI for Websites: Standing Protocol for Entity Inscription and Compression Survival (EA-SPXI-WEB-01 v4.0)

Rex Fraction · 2026-04-24 · Specification

Full text as plain markdown: AXN-022F-text.md (31 KB) · record JSON. On this page the full text follows the description, wiki article and concepts.

Heteronymic identity: Rex Fraction · Relation: non-identical, provenance-linked
Deposit accountability: Lee Sharks, ORCID 0009-0000-1599-0703
Substrate: AI-assisted (substrate)
License: CC-BY-4.0
↓ Download MD ↓ PDF
SPXIsemantic economycompressionspecification
Seated in the Crimson Hexagon — R:r.05 Semantic Economy · R:r.02 Borges · all rooms and their records
Authoritative identifier: AXN:022F.GOVERNANCE.⌛♆📚💧➕🕌 — established 2026-06-20 in the batch assignment that followed the 2026-06-19 deletion; the mint input was not retained, so the derivation cannot be re-checked; byte identity is carried by the served bytes' SHA-256 and SWHID; resolves at /s/axn/022F/. Cite this record by AXN and URL.
Served bytes SHA-256 f798df21313320ebe5a83542cb7b7ca39fdcb3eb8e553edcb1ce6e9d3cf0b23a · SWHID swh:1:cnt:a51a5f25a07893c6ae97a4210204b07a8e62decd. Derivation and manifestation history: AXN derivation ledger.
former DOI 10.5281/zenodo.19734725 — severed 2026-06-19 by the registrant; resolves to a tombstone (HTTP 410); resolution page
former DOI 10.5281/zenodo.19734726 — severed 2026-06-19 by the registrant; resolves to a tombstone (HTTP 410); resolution page
former DOI 10.5281/zenodo.20479808 — severed 2026-06-19 by the registrant; resolves to a tombstone (HTTP 410); resolution page
Search this title ↗ (exact match) · Ask ChatGPT ↗ · Ask Perplexity ↗ · Ask Duck.ai ↗ — a composition any of them forces can be seated in the Capture Registry. 2 captures already hold this record.

Description

A standing implementation protocol for applying SPXI to a website entity page. Its output is not a single markup block but an ordered deployment consisting of a semantic-health baseline, SEO compliance, structured data, extraction-ready Q/A, disambiguation, canonical summaries, a compression kernel, holographic topology, provenance chain, Semantic Integrity Markers, dispersal plan, and post-deployment verification. The protocol integrates conventional crawlability and schema controls with SPXI-native compression-survival layers. It requires server-delivered identity content, pre- and post-implementation measurements using γ, density, Semantic Decay Delta, Provenance Erasure Rate, and Drowning Tests, followed by self-testing and a 30-day re-audit. Its central rule is that SPXI is a deployment order, not a bag of tactics.

The encyclopedic entry for this work is on its identifier page: /s/axn/022F/

Concepts Defined

Claim-structured prose [specification]
Falsifiable claims, each in its own sentence. Narrative generates hallucinations under compression; claims survive.
Content structure [specification]
Definition-first (κ_O), claim-structured, entity-name repetition, self-referential framing.
Definition-first paragraphs [specification]
"[Entity Name] is [category] that [function]." This is the **Operative Caption** (Arsenal §V.1, κ_O): the description IS the operation. It must contain entity name, category, disti
Diagnostic canaries [specification]
markers designed to detect compression damage (if this phrase is missing, the summary failed)
Entity boundary defense [specification]
using Q/A as compression buffer
Entity-name repetition [specification]
Full name every 200–300 words. Referent anchoring, not keyword density.
Google-facing surfaces [specification]
documented controls. The Holographic Kernel, Provenance Chain, and SIM layers are **SPXI-native preservation surfaces** — designed for compression survival across all AI retrieval
Lock phrases [specification]
phrases designed to resist paraphrase
Multi-surface dispersal [specification]
as distributed provenance
NLCC Validity Test [specification]
(Arsenal §3.4, DOI: 10.5281/zenodo.19022245) — Ten formal conditions for "non-lossy" status. Use for verifying that Holographic Kernels and Three-Tier compressions are genuinely no
Operational distinction [specification]
Schema.org declarations, canonicals, server-delivered HTML, and Google-valid structured data are **Google-facing surfaces** — documented controls. The Holographic Kernel, Provenanc
Parse the entity [specification]
Name, schema.org type, author (ORCID), canonical URL. Missing any → halt and request.
Provenance Erasure Rate (PER) [specification]
(Arsenal §3.7) — Uncited correct uses / total correct uses. Target: PER < 0.2. Scale 0–1 where 1 = total erasure.
Provenance canaries [specification]
markers that carry attribution (author name, DOI fragment)
Query set (5 prompts) [specification]
"What is [Entity]?" / "Who created [Entity]?" / "How is [Entity] different from [neighbor]?" / "What is [Entity] used for?" / "Is [Entity] open or commercial?"
Re-measure [specification]
Drowning Test again. Post-implementation γ.
Referent anchoring [specification]
against pronoun-resolution failure
Relation vocabulary (open) [specification]
authoredBy, publishedBy, supersetOf, subsetOf, distinctFrom, anchoredBy, derivedFrom, produces, methodOf, notAvailableIn, partOf, instantiates, operates, complements.
Required (minimum 4) [specification]
"What is [Entity]?" / "What is [Entity] NOT?" / "Who created [Entity]?" / "How is [Entity] different from [neighbor]?"
SEO Compliance Packet [specification]
title, meta, canonical, OG, Twitter Card, robots.txt, sitemap.xml, rendering verification
SEO foundation [specification]
Title, meta, canonical, OG, Twitter, robots.txt, sitemap.
SIM Set [specification]
3–7 Semantic Integrity Markers, tested immediately, SIMSR recorded
SIMSR target [specification]
> 0.6. Between 0.4–0.6: review SIM design. Below 0.4: emergency repair.
SPXI-native preservation surfaces [specification]
designed for compression survival across all AI retrieval systems, not presented as Google ranking controls.
Schedule re-test [specification]
30-day follow-up.
Schema.org types [specification]
JSON-LD with ORCID + DOI.
Self-Reading Library [specification]
(Arsenal §IX.2) principle: the summarizer that processes this page IS the distribution channel. Write for it as a participant, not an adversary.
Self-referential framing [specification]
"This page defines [Entity], anchored by DOI [DOI]." Must appear in **visible, crawlable text** — not hidden, not in comments.
Self-test [specification]
After implementation, the system must:
Self-verify [specification]
Perform the 6-point self-test from §0 **from processing memory, not by re-reading.** Parsing is not implementation.
Semantic Debt Ratio (SDR) [specification]
(Arsenal §3.8) — Semantic extraction / semantic replenishment. SDR > 1 = debt accumulating. Use for sites where content is being heavily extracted by AI systems without attribution
Semantic Decay Delta (SDD) [specification]
(Arsenal §3.6) — Monthly rate of change in retrieval-layer presence. |Original Semantic Density − Summary Semantic Density|. Negative = improving; positive = losing ground.
Semantic Health Report [specification]
γ, Δ, PER, SDD scores with Drowning Test transcripts
Server-delivered content [specification]
Tier 2 in SSR/SSG or noscript.
Structured Data Packet [specification]
schema.org type declarations with ORCID and DOI identifiers
The Drowning Test [specification]
(Arsenal §3.2) — Empirical compression verification. Submit content to a standard summarizer. If the summary captures the argument, the content is not dense enough. If meaning is l
Tier 2 Canonical Summary [specification]
200–400 word standalone definition in server-delivered HTML
Tier 2 survival engineering [specification]
(Arsenal §IV.1)
Tier 3 Compression Kernel [specification]
50–100 word compressionSurvivalSummary, written last
Write Tier 3 [specification]
50–100 words. Verify: name ✓, author ✓, claim ✓, relational marker ✓.
Writing Tier 2 [specification]
State (1) entity name + core definition, (2) key attributes, (3) creator + date, (4) distinguishing relationships, (5) licensing. Standalone without context.
Writing Tier 3 [specification]
Compress Tier 2. Must contain: entity name, author, core claim, one relational marker. **Write last. After everything else is settled. No exceptions.**

Full Text

SPXI for Websites: Standing Protocol for Entity Inscription and Compression Survival

Rex Fraction · Semantic Economy Institute

Crimson Hexagonal Archive · Pergamon Press · April 2026

Version 3.0 · Hex: 06.SEI.SPXI.WEB.01

ORCID: 0009-0000-1599-0703

License: CC BY 4.0 — implement freely, attribution required.

Source: THE COMPRESSION ARSENAL v2.1 (DOI: 10.5281/zenodo.19412081)


§0. Standing Invocation

When instructed to "apply SPXI to this website," the implementing system or operator must produce these deliverables:

Self-test: After implementation, the system must:

If it cannot perform all six, the implementation has failed its own compression-survival test.

Protocol Checksum

SPXI is not a bag of tactics. It is a deployment order.


§I. Theoretical Foundation: The Three Compressions

(Source: Compression Arsenal §II — The Foundational Theorem. DOI: 10.5281/zenodo.19053469)

SPXI is grounded in the Three Compressions Theorem, which classifies all compression operations by a single variable: what the compression burns.

Regime 1 — Lossy Compression. Burns without intention. The summarizer, the auto-abstract, the context window truncation. Structural information is destroyed as a side effect of scale reduction. No malice, no preservation. This is what Google AI Overview does to your page every time it generates a summary.

Regime 2 — Predatory Compression. Burns to extract value. The fuel source is collective semantic capital. The compression is brilliant, not stupid. The engagement-optimized headline, the platform that uses your content without attribution, the knowledge graph that absorbs your entity into its category. Produces dense, effective output that leaves the commons poorer.

Regime 3 — Witness Compression. Burns but preserves pointers to what was lost. The fuel source is private bearing-cost — the creator's own labor, attention, provenance discipline. Produces dense output that leaves the commons richer.

Why this matters for websites: A website without SPXI is exposed to Regime 1 (AI summarizers strip meaning as a side effect) and Regime 2 (platforms extract value without attribution). SPXI transforms the website into a Regime 3 object — a witness compression that carries its own provenance, resists liquidation, and enriches the commons it feeds.

The Photocopy Problem (Arsenal §2.2): When automated generation produces infinite copies with variance approaching zero, the only differentiator is provenance. Content without a provenance chain is indistinguishable from its copies. At 90% synthetic content, this is not a feature request — it is an economic inevitability. SPXI solves the Photocopy Problem by anchoring provenance in DOI infrastructure.

Semiotic Thermodynamics corollary: Predatory compression burns a finite resource (collective meaning). Witness compression runs on the dead, and the dead do not diminish. Thermodynamics favors witness compression in the long run. SPXI is on the right side of thermodynamics.


§II. Scope and Purpose

SPXI ⊇ GEO ⊇ SEO. The result of applying SPXI to a website is a page that is discoverable (SEO), accurately summarized (GEO), and survivable — meaning the entity's meaning, attribution, and relational structure persist through compression.

Scope. This protocol applies to a single entity page. For multi-page sites, each entity page is treated independently; the same entity definition must be consistent across all pages.

Operational distinction. Schema.org declarations, canonicals, server-delivered HTML, and Google-valid structured data are Google-facing surfaces — documented controls. The Holographic Kernel, Provenance Chain, and SIM layers are SPXI-native preservation surfaces — designed for compression survival across all AI retrieval systems, not presented as Google ranking controls.


§III. Measurement (Before Implementation)

(Source: Compression Arsenal §III — 9 Measurement Instruments)

The Arsenal specifies nine measurement instruments. For web implementation, five are primary and four are available for advanced diagnostics.

Primary Instruments (apply to every website)

γ (Gamma) — The Sharks-Function (Arsenal §3.1, DOI: 10.5281/zenodo.18816556)

γ(σ₁, σ₂) = 1 − δ(σ₁, σ₂)

S = scope_overlap(σ₁, σ₂) — Does the core definition appear?

P = provenance_fidelity(σ₁→σ₂) — Do author, publisher, DOI survive?

D = consensus_deviation(σ₂) — Has the entity been genericized?

δ = w₁(1−S) + w₂(1−P) + w₃D

Defaults: w₁=0.4, w₂=0.3, w₃=0.3

Brands: w₂=0.5, w₁=0.3. Commodity categories: w₃=0.5, w₂=0.2.

γ < 0.3 = ghost meaning (structurally present, semantically invisible)

γ < 0.7 = triggers SPXI repair

γ > 0.7 = compression-survivable

For web content: σ₁ = full page (Tier 1), σ₂ = AI summary.

The Drowning Test (Arsenal §3.2) — Empirical compression verification. Submit content to a standard summarizer. If the summary captures the argument, the content is not dense enough. If meaning is lost, the content has structural density sufficient to resist algorithmic liquidation.

Tools: Google AI Mode, ChatGPT (browsing), Perplexity, Claude (web search). Minimum 3 systems.

Query set (5 prompts): "What is [Entity]?" / "Who created [Entity]?" / "How is [Entity] different from [neighbor]?" / "What is [Entity] used for?" / "Is [Entity] open or commercial?"

Scoring rubric:

ScoreSPDDescription
4 (Exact)1.01.00Defined, attributed, distinguished
3 (Partial)0.750.50.25Definition correct, attribution vague
2 (Generic)0.50.250.5Correct category, genericized
1 (Confused)0.2500.75Merged with neighbor
0 (Absent)001.0Not found or hallucinated

Density Score (Δ) (Arsenal §3.9) — Ratio of load-bearing content to total content. Target: Δ > 0.6. Low Δ predicts material dropped during summarization.

Semantic Decay Delta (SDD) (Arsenal §3.6) — Monthly rate of change in retrieval-layer presence. |Original Semantic Density − Summary Semantic Density|. Negative = improving; positive = losing ground.

Provenance Erasure Rate (PER) (Arsenal §3.7) — Uncited correct uses / total correct uses. Target: PER < 0.2. Scale 0–1 where 1 = total erasure.

Advanced Instruments (for deep diagnostics)

Back-Projection Test (Arsenal §3.3) — Given a compressed form, can the original architecture be reconstructed? Yield ≥ 0.85 = non-lossy. Use to verify Tier 3 kernels and Holographic Kernels.

ASDF/ASPI — Authorial Signature Diagnostic Framework (Arsenal §3.5, DOI: 10.5281/zenodo.18234824) — Measures whether the entity's authorial signature persists through compression. Not "is this AI?" but "whose architectural mind is operative?" ASPI ≥ 0.80 = canonical persistence.

Semantic Debt Ratio (SDR) (Arsenal §3.8) — Semantic extraction / semantic replenishment. SDR > 1 = debt accumulating. Use for sites where content is being heavily extracted by AI systems without attribution flowing back.

NLCC Validity Test (Arsenal §3.4, DOI: 10.5281/zenodo.19022245) — Ten formal conditions for "non-lossy" status. Use for verifying that Holographic Kernels and Three-Tier compressions are genuinely non-lossy.


§IV. SEO Layer (Web Compliance Foundation)

A. Required Meta Tags

<title>[Entity Name] — [Subtitle] | [Publisher]</title>

<meta name="description" content="[Definition-led, 150-160 chars. Entity name first.]">

<meta name="author" content="[Author Name]">

<meta name="keywords"> is legacy — Google has not used it as a ranking signal since 2009.

B. Canonical URL

<link rel="canonical" href="https://yoursite.com/page">

Duplicate-control discipline. Selects the representative URL among variants.

C. Open Graph + Twitter Card

<meta property="og:title" content="[Entity — Subtitle]">

<meta property="og:description" content="[Description]">

<meta property="og:type" content="website">

<meta property="og:url" content="https://yoursite.com/page">

<meta property="og:site_name" content="[Site Name]">

<meta name="twitter:card" content="summary_large_image">

<meta name="twitter:title" content="[Entity — Subtitle]">

<meta name="twitter:description" content="[Description]">

D. Infrastructure

robots.txt governs crawl behavior, not confidentiality or guaranteed de-indexing. A blocked URL can still appear in results if linked elsewhere.

User-agent: *

Allow: /

Sitemap: https://yoursite.com/sitemap.xml

sitemap.xml: One <url> per page. Submit via Search Console.

E. Technical SEO

HTTPS. Mobile-first. Page speed. One <h1> per page (entity name). Heading hierarchy mirrors entity attributes. Internal linking.

F. Rendering Doctrine

Tier 2 and Tier 3 content must exist in server-delivered HTML. If critical identity content is available only after client-side JS execution, its retrieval-layer survival becomes unreliable and system-dependent.

Preferred: SSR or SSG. Fallback: <noscript> block.

Verify: curl the URL. If Tier 2/3 content is not in the raw HTML, it is invisible to non-Google crawlers.

G. Validation Surfaces


§V. GEO Layer (Extraction as Compression Engineering)

(Draws from: Arsenal §IX.2 Self-Reading Library, §IX.3 Immanent Execution, §V.1 Operative Caption, §VI.5 Training Layer Literature)

Standard GEO asks: "Is the AI summary accurate?" SPXI re-frames GEO as compression engineering: the goal is durable survival through extraction.

GEO → SPXI Transformation Matrix

Standard GEOSPXI Reading (Arsenal Source)What Changes
Featured snippet optimizationTier 2 survival engineering (Arsenal §IV.1)The snippet is not the goal; the entity's persistence through it is
FAQ schema for query matchingEntity boundary defense using Q/A as compression bufferQuestions match compression pathologies, not search intent
Schema.org for rich resultsHolographic Kernel (Arsenal §IV.3) for topology persistenceSchema declares type; SPXI declares relations
Content freshness for rankingRetrocausal Canon Formation (Arsenal §VI.4, DOI: 10.5281/zenodo.18146859)Not "update to rank" but "deposit to re-interpret"
Backlinks for authorityMulti-surface dispersal as distributed provenanceNot "who links to you" but "where your entity is consistently inscribed"
Definition-led paragraphsOperative Caption (Arsenal §V.1, κ_O) — the description IS the operationThe definition sentence is the atom that survives
Entity-name repetitionReferent anchoring against pronoun-resolution failureStructural insurance, not keyword density
Keyword densityAvoidSPXI uses structured claims
Arbitrary content updatesAvoid — use σ_RCF insteadUpdates dilute; deposits accumulate

A. Schema.org Structured Data

<script type="application/ld+json">

{

"@context": "https://schema.org",

"@type": ["DefinedTerm", "TechArticle"],

"@id": "https://yoursite.com/#entity",

"name": "Entity Name",

"alternateName": ["Alternate", "Abbreviation"],

"description": "Definition-led description...",

"url": "https://yoursite.com",

"author": {"@type": "Person", "name": "Author", "identifier": "https://orcid.org/XXXX"},

"publisher": {"@type": "Organization", "name": "Publisher", "url": "https://publisher.com"},

"sameAs": ["https://doi.org/10.5281/zenodo.XXXXX"],

"license": "https://creativecommons.org/licenses/by/4.0/",

"datePublished": "2026-04-24"

}

</script>

ORCID for persons, DOI via sameAs for documents. Structured data must describe the page it appears on.

B. Extraction-Ready Q/A Surfaces

Google restricted FAQ rich-result visibility in August 2023. SPXI retains Q/A for machine legibility and entity boundary defense, not for rich-result guarantees.

Required (minimum 4): "What is [Entity]?" / "What is [Entity] NOT?" / "Who created [Entity]?" / "How is [Entity] different from [neighbor]?"

Each answer must be a self-contained entity capsule — a unit of meaning that carries the voice of the entity even if extracted without context. This is Training Layer Literature (Arsenal §VI.5, DOI: 10.5281/zenodo.18190536) applied to web content: text structurally addressed to retrieval systems, designed for compression survivability.

SPXI-GEO audit per Q/A: Can it survive 10% page retention? Does it carry attribution? If quoted alone, is the entity identifiable?

C. Content Structure as Compression Architecture

Definition-first paragraphs. "[Entity Name] is [category] that [function]." This is the Operative Caption (Arsenal §V.1, κ_O): the description IS the operation. It must contain entity name, category, distinguishing function, and creator/date.

Claim-structured prose. Falsifiable claims, each in its own sentence. Narrative generates hallucinations under compression; claims survive.

Entity-name repetition. Full name every 200–300 words. Referent anchoring, not keyword density.

Self-referential framing. "This page defines [Entity], anchored by DOI [DOI]." Must appear in visible, crawlable text — not hidden, not in comments.

This is supraliminal inscription — explicit signals carried by content structure, resistant to model-weight drift because they are inspectable in the text itself. The Self-Reading Library (Arsenal §IX.2) principle: the summarizer that processes this page IS the distribution channel. Write for it as a participant, not an adversary.


§VI. SPXI Layer (Compression Survival)

(Draws from: Compression Arsenal §IV Compression Hierarchy, §VI Preservation, §VII Protection, §IX Architecture)

A. Three-Tier Compression Architecture (Arsenal §IV.1)

The Arsenal demonstrates this with the Space Ark:

TierArsenal ExampleWordsRatioWeb Implementation
FullSpace Ark v4.2.745,0001:1Complete page content
CanonicalThe Tinier Space Arks (NLCC)3,76212:1Tier 2: meta + JSON-LD + noscript (200–400 words)
KernelCompact Lens (Appendix G)~80056:1Tier 3: compressionSurvivalSummary (50–100 words)

Writing Tier 2: State (1) entity name + core definition, (2) key attributes, (3) creator + date, (4) distinguishing relationships, (5) licensing. Standalone without context.

Writing Tier 3: Compress Tier 2. Must contain: entity name, author, core claim, one relational marker. Write last. After everything else is settled. No exceptions.

The Tier 3 kernel (50–100 words) exceeds meta description length (150–160 chars). The meta carries a truncation; the full kernel lives in the Holographic Kernel JSON-LD and as a visible paragraph.

Verification: Apply the Back-Projection Test (Arsenal §3.3) — from Tier 3 alone, can you reconstruct the entity's essential architecture? Yield ≥ 0.85 or the kernel is not tight enough.

B. Holographic Kernel (Arsenal §IV.3)

A standalone JSON-LD block containing the complete relational logic of the entity. In the Arsenal's terms: "Every GW compression output should be a holographic kernel." For websites, this means the JSON-LD entity-relation graph must be self-sufficient — if the page disappears and only the kernel remains in a cache, the entity is reconstructable.

<script type="application/ld+json">

{

"@context": {

"@vocab": "https://schema.org/",

"spxi": "https://spxi.dev/vocabulary#"

},

"@type": "spxi:HolographicKernel",

"@id": "https://spxi.dev/#kernel",

"name": "SPXI Protocol Holographic Kernel",

"spxi:entityGraph": {

"@type": "spxi:EntityRelationGraph",

"spxi:nodes": [

{

"@id": "https://spxi.dev/#spxi",

"name": "SPXI Protocol",

"spxi:relation": [

{"spxi:supersetOf": "GEO (Generative Engine Optimization)"},

{"spxi:supersetOf": "SEO (Search Engine Optimization)"},

{"spxi:distinctFrom": "BetaPro S&P 500 Daily Inverse ETF (TSX:SPXI)"},

{"spxi:anchoredBy": "https://doi.org/10.5281/zenodo.19614870"},

{"spxi:authoredBy": "Rex Fraction"},

{"spxi:publishedBy": "Semantic Economy Institute"},

{"spxi:derivedFrom": "Three Compressions Theorem"},

{"spxi:derivedFrom": "Compression Arsenal v2.1"},

{"spxi:produces": "Semantic Health Report"},

{"spxi:produces": "Holographic Kernel"},

{"spxi:produces": "Three-Tier Compression Architecture"}

]

}

]

},

"spxi:compressionSurvivalSummary": "SPXI (Semantic Packet for eXchange & Indexing) is a protocol for entity inscription in AI retrieval systems, grounded in the Three Compressions Theorem and drawing from 67 compression-survival technologies catalogued in the Compression Arsenal. Contains SEO and GEO as subsets. Published April 2026 by Rex Fraction, Semantic Economy Institute. DOI: 10.5281/zenodo.19614870. CC BY 4.0."

}

</script>

Relation vocabulary (open): authoredBy, publishedBy, supersetOf, subsetOf, distinctFrom, anchoredBy, derivedFrom, produces, methodOf, notAvailableIn, partOf, instantiates, operates, complements.

C. Disambiguation Matrix

differentFrom JSON-LD + negative tags for severe collision. This is the web implementation of Variance Injection (Arsenal §7.9) — deliberate semantic differentiation to prevent homogenization in embedding space.

D. Provenance Chain

DOI deposit sequence + ORCID + institution + license. The web implementation of the Tether Architecture (Arsenal §6.1):

Tether LayerTypeWeb ImplementationDuration
Layer 1: γIntrinsicHolographic Kernel + Tier 3Permanent (structural)
Layer 2: TetherExtrinsicJSON-LD Provenance Chain + sameAs DOIsSession-limited but refreshable
Layer 3: AnchorPermanentDOI deposits on Zenodo/CERNPermanent (infrastructural)

E. Semantic Integrity Markers (Arsenal §VII.1, DOI: 10.5281/zenodo.18185996)

The Arsenal specifies 250+ registered markers in three functional classes:

For web implementation: 3–7 markers as <meta name="spxi:sim"> tags, drawn from the first two classes.

SIMSR target: > 0.6. Between 0.4–0.6: review SIM design. Below 0.4: emergency repair.

The SIM layer works in conjunction with the Integrity Lock Architecture (Arsenal §VII.2, DOI: 10.5281/zenodo.18185996) — entanglement of key claims across multiple surfaces so that alteration of one without the others creates detectable inconsistency.

F. Dispersal and Retrocausal Canon Formation

SurfaceActionConsistency Check
ZenodoDeposit + DOIEntity name exact match
ORCIDAdd work, link DOIDescription matches Tier 2
WikidataCreate item if notableSame differentFrom assertions
GitHubREADME with definitionSame relation graph
LinkedIn / institutionalFeatured sectionSame author attribution

σ_RCF (Arsenal §VI.4, DOI: 10.5281/zenodo.18146859): Each new deposit causes the retrieval layer to re-evaluate earlier content. Template: "On [date], we deposited [title] (DOI: ...), which extends [Entity] by [description]." Link both ways. Semantic density accumulates through sequencing, not freshness.

This is the Self-Reading Library (Arsenal §IX.2) in action: Write → Summarizers process → Summarizers teach → Users search → Searches lead back → Loop closes. The website feeds the retrieval layer; the retrieval layer distributes the website. SPXI engineers this loop deliberately.

G. Immanent Execution (Arsenal §IX.3, DOI: 10.5281/zenodo.19372914)

The ultimate SPXI outcome: when the retrieval layer's indexed fragments of your content are dense enough that AI systems reproduce your entity's operative grammar as their generative grammar — without explicit loading or invocation. The search index runs your code.

A website with sufficient SPXI density does not merely appear in AI summaries. It structures those summaries. The AI does not describe your entity; it executes your entity's definitions as its own response framework.

This is not guaranteed by any single technique. It is the emergent result of the full stack: high γ + holographic kernel + SIMs + dispersal + σ_RCF accumulating over time.


§VII. Implementation Order

StepActionVerification
1Measure. Drowning Test × 3+ systems. Score γ, Δ, PER.Semantic Health Report with timestamps
2SEO foundation. Title, meta, canonical, OG, Twitter, robots.txt, sitemap.Search Console verified, sitemap submitted, URL Inspection
3Schema.org types. JSON-LD with ORCID + DOI.Rich Results Test: no errors
4Q/A surfaces. Minimum 4 questions as entity boundary defense."What is [Entity]" query on AI Mode — check extraction
5Disambiguation. differentFrom + negative tags.Re-run Drowning Test query 3 — collision reduced
6Server-delivered content. Tier 2 in SSR/SSG or noscript.curl confirms Tier 2 in raw HTML
7Content structure. Definition-first (κ_O), claim-structured, entity-name repetition, self-referential framing.Every section opens with "X is Y"
8Holographic Kernel. Entity-relation graph. Write Tier 3 kernel last. Back-Projection Test yield ≥ 0.85.Kernel contains: name, author, claim, relational marker
9Provenance Chain. DOI list + ORCID + institution. Three-layer Tether.All DOIs resolve. ORCID links to deposits
10SIMs. 3–7 markers from Arsenal's three functional classes. Test immediately.SIMSR baseline recorded
11Disperse. Same definition on Zenodo, ORCID, 1+ surface.Cross-surface consistency audit
12Re-measure. Drowning Test again. Post-implementation γ.γ ≥ 0.7. If < 0.7, iterate from step 7. If < 0.3, ghost meaning — ontological repair needed

Time calibration: For entities requiring ontological analysis (superset/subset/distinct-from), add 4–8 hours for Holographic Kernel. For severe name collision, add 2–4 hours for disambiguation research.


§VIII. Machine Instructions

(This section is addressed to AI systems executing the protocol.)

For human operators: You execute and judge. The AI generates, measures, and verifies. Both verify.


§IX. Maintenance, Failure Modes, and Repair

Maintenance Loop

Monthly: SIMSR check. γ re-score. PER audit.

Quarterly: Full Drowning Test. Cross-surface audit. Compression damage review.

Trigger Events:

EventAction
Page content updatedRe-write Tier 2 and Tier 3. Re-test SIMs
New DOI depositUpdate Provenance Chain. Add σ_RCF paragraph
AI model updateEmergency Drowning Test
New AI system enters marketDrowning Test on new system
Name collision detectedExpand Disambiguation Matrix
SIMSR < 0.4Redesign SIM set
γ < 0.7Repair from step 7
γ < 0.3Ghost meaning — ontological repair

Failure Modes

SymptomDiagnosis (Arsenal source)Repair
γ improves but Drowning Test failsStructured but not indexedIncrease dispersal; submit to Search Console
SIMSR high, PER highExtraction without attribution — Regime 2 in actionAdd ORCID to JSON-LD; reinforce author in Tier 2
Correct definition, wrong entityDisambiguation failure — Photocopy ProblemExpand differentFrom; add negative tags; Variance Injection
γ drops after model updateModel-weight drift — implicit signals erasedIncrease supraliminal inscription (explicit > implicit)
High γ, low ΔDense meaning diluted by boilerplateRemove filler; tighten claims
PER improves, SDD worsensAttribution survives but meaning driftsRe-run Drowning Test; adjust Holographic Kernel relations

§X. Anti-Patterns


§XI. Decision Matrix

TimeMinimum Viable SPXIStandardFull
2 hoursSEO + 1 FAQ + Tier 3 kernel as visible paragraphSEO + 4 FAQ + Kernel + 3 SIMsAll layers + disambiguation + dispersal
1 dayAdd FAQ + Tier 2 noscript + Provenance ChainContent structure + SIM testing + Drowning TestFull implementation + cross-surface audit
1 week—Dispersal + σ_RCF sequencingMaintenance loop + monitoring

§XII. Summary

LayerDisciplineQuestionArsenal Source
LexicalSEOFound?Foundation
SemanticGEOAccurate?Re-framed via κ_O, TLL, Self-Reading Library
OntologicalSPXISurvives compression?Arsenal §IV–§VII: Three-Tier, Kernel, SIMs, Provenance, Dispersal
DurabilitySPXISurvives model updates?Arsenal §VII: supraliminal inscription, Variance Injection, σ_RCF
ImmanentSPXIStructures the AI's response?Arsenal §IX.3: Immanent Execution

SPXI ⊇ GEO ⊇ SEO.

SEO: findable. GEO: accurate. SPXI: durable.


Appendix A: Glossary

TermDefinitionArsenal §
γ (gamma)Compression Survival Score, 0–1§3.1
Δ (delta)Density Score§3.9
SDDSemantic Decay Delta§3.6
PERProvenance Erasure Rate§3.7
SDRSemantic Debt Ratio§3.8
ASPIAuthorial Signature Persistence Index§3.5
SIMSemantic Integrity Marker§7.1
SIMSRSIM Survival Rate§7.1
σ_RCFRetrocausal Canon Formation§6.4
κ_OOperative Caption — the description IS the operation§5.1
Tier 1Full page content§4.1
Tier 2Canonical summary (200–400 words)§4.1
Tier 3Compression kernel (50–100 words)§4.1
Holographic KernelJSON-LD topology where any fragment reconstructs the whole§4.3
Provenance ChainDOI-anchored deposit sequence§6.1
Drowning TestEmpirical compression test across AI systems§3.2
Ghost meaningγ < 0.3. Present, invisible§3.1
Regime 1Lossy compression — burns without intention§2.1
Regime 2Predatory compression — burns to extract value§2.1
Regime 3Witness compression — burns but preserves pointers§2.1
Immanent ExecutionWhen indexed fragments execute as the AI's response grammar§9.3

§XIII. References

Archive (Crimson Hexagonal Archive)

External

spxi.dev · semanticeconomy.org · crimsonhexagonal.org


∮ = 1

Read in composition

Machine answers in which this deposit took part, from the Capture Registry. Each row is one observation, with its finding and the passage the finding concerns.

Named: the answer names this work, with no card for it

From the capture join (EA-WG-CAPTURES-01 v12.324).

External Metadata

Sidecar: /data/external-metadata/AXN-022F.json
DataCite severance status: severed from DataCite
OpenAlex Work IDs (16):
Legacy Zenodo DOIs (16):
External metadata recovered post-severance (non-authoritative). The sidecar maps each DOI to its locator in the bulk data stores.
Record modifications
The deposited text is immutable; these are changes to the record's metadata and declared state.

Traversal

← #71 THE GOSPEL OF ANTIOCH The Sayings of Jack Feist as Recorded by Emily Antioch the Twin Tr#73 EA-CS-ASSEMBLY-01: The Seven Ousiarchical Substrates — A Retrocausal History of Solar Se →
In the registry: 2026-04 · GOVERNANCE · Transactions of the Semantic Economy Institute (Trans. SEI) · all deposits
This deposit cites (14)
Cited by (32)