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

SPXI for Websites is the standing web-deployment protocol attributed to Rex Fraction.

Invocation—“apply SPXI to this website”—requires twelve deliverables:

1. Semantic Health Report 2. SEO Compliance Packet 3. Structured Data Packet 4. Extraction-Ready Q/A Surfaces 5. Disambiguation Matrix 6. Tier 2 Canonical Summary 7. Tier 3 Compression Kernel 8. Holographic Kernel 9. Provenance Chain 10. SIM Set 11. Dispersal Plan 12. 30-Day Verification Schedule

The protocol begins with measurement rather than markup. Primary instruments include the Sharks-Function γ, Drowning Test, Density Score, Semantic Decay Delta, and Provenance Erasure Rate. Advanced instruments include back-projection, ASDF/ASPI, Semantic Debt Ratio, and the NLCC validity test.

The SEO layer covers titles, descriptions, canonical URLs, Open Graph, Twitter Cards, crawl controls, sitemaps, HTTPS, mobile rendering, heading hierarchy, and validation. It distinguishes crawl control from confidentiality and requires critical entity content in raw server-delivered HTML.

The GEO layer is reframed as compression engineering. Definition-first prose, Q/A surfaces, entity-name repetition, and claim-structured paragraphs are not treated as ends in themselves; they are used to improve survival through extraction.

SPXI adds the layers GEO and SEO do not supply: negative-tag disambiguation, DOI and ORCID provenance, three-tier compression, Holographic Kernels, SIMs, cross-surface alignment, and measured re-testing.

The implementation self-test asks the system to state the entity type, recite the compression kernel, identify collision neighbors, cite provenance identifiers, report γ subscores, and regenerate the Holographic Kernel. Failure on any item means the deployment has not survived its own compression test.

The protocol’s governing statement is: SPXI is not a bag of tactics. It is a deployment order.