Optimising for the surfaceless web
🔗 **Source:** [Optimising for the surfaceless web](https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/)
> [!note]+ Document Notes
> tags: [AI, Marketing, SEO]
> author: Jono Alderson
> source: jonoalderson.com
> reference: [https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/]
> date created: 2025-10-30 00:00
>
> # 🏷️ Title: Optimising for the surfaceless web
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened.
- The web’s “surface” (pages, clicks, SERPs) is being compressed into AI models’ internal representations.
- Why it matters.
- Visibility becomes an echo; survival depends on being useful, true, and integral within the model’s map.
- Key stakeholders.
- Marketers, publishers, brands, SEO/SEM teams, platform builders, AI labs.
- Risks and tradeoffs.
- Ephemeral campaigns decay; manipulative signals get filtered; overfitting to model priors risks loss of nuance.
- Bottom line.
- Optimise for persistence in the model: clarity, consistency, connection over surface performance.
## 📖 Main Content
- Explain the core arguments in plain language.
- AI digests web content into a probabilistic “substrate.” What is shown to humans is downstream of what models already “know.”
- Selection pressure: stable, corroborated, connected information persists; noise and contradictions dissolve.
- Marketing shifts from seeking attention to earning existence inside the model.
- Add sourced context and define terms.
- “Substrate”: the model’s internal knowledge graph/distribution of associations.
- “Persistence”: recurring recognition across training cycles.
- Note uncertainties or contested claims.
- Degree of model memory and update cadence varies by vendor; exact weighting of “useful/true/integral” is speculative but directionally sound.
### 🗒️ Notes
- “There are no more surfaces – only systems.”
- Visibility is “a by-product of how well you exist in the model’s internal map.”
- Selection pressure favors clarity, corroboration, connection; “campaign noise burns off.”
- Traits that endure: Useful (reduces ambiguity), True (statistically coherent), Integral (structurally connected).
- “You don’t persuade a model. You support it.”
- Temporal persistence: reassert coherent patterns across time and media; survive model updates.
- “The game isn’t about visibility anymore. It’s about viability.”
## 📚 References
- Optimising for the surfaceless web (original article) (https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/)
- Google Search Generative Experience / AI Overviews explainer (https://blog.google/products/search/generative-ai-search/)
- OpenAI: Models and training overview (https://platform.openai.com/docs/guides/reasoning)
- Schema.org (structured data) (https://schema.org/)
- W3C: Verifiable Credentials overview (https://www.w3.org/TR/vc-data-model-2.0/)
## 🗣️ Paraphrase
- Paragraph A paraphrase.
- As AI compresses the web into internal models, the visible layer becomes a residue; relevance is determined before anything appears to users.
- Paragraph B paraphrase.
- To endure, information must be useful, statistically consistent, and structurally connected, so that removing it would weaken the model’s understanding.
## 📰 Newsletter
- The web’s “surface” is fading as AI systems internalise our content. Winning now means becoming part of the model’s scaffolding: publish clarifying, consistent, well-cited resources; align language, data, and presence; and reinforce over time. For WordPress folks: invest in structured data, canonical taxonomies, entity pages, and provenance. Useful links: Schema.org, verifiable credentials, and performance/SEO checklists.
## ✅ Action Items
#### DevRel
- Developer advocacy: Run “model-first content” talks; demo entity alignment; measure citations/links won.
- Education: Workshop on schema, disambiguation, provenance.
- Developer experience: Provide SDK/examples for structured data and content signatures.
- Developer marketing: Publish canonical explainer series; track inclusion in AI answers.
- Community management: Guide on coherent language/terms; moderation for consistency.
- Internal/external/cross-project: Set SLAs for taxonomy and schema updates.
#### OSPO
- Policy & Governance: Contribution guidelines for factuality, citations, and change logs.
- License Compliance: Automate license metadata in feeds.
- Security Management: Sign releases; publish attestation docs.
- Software Inventory: SBOMs per release; freshness SLOs.
- Developer Support: Office hours on provenance and data integrity.
- Community Engagement: Fund upstream schema and tooling.
- Strategic Alignment: OKRs on structured data coverage and entity coherence.
#### Community
- Maintainers: Roadmap clinics on naming/versioning coherence.
- Contributors: First-issue rotations on doc fixes and schema.
- Sponsors: Tie funding to measurable knowledge integrity outcomes.
- Ecosystem: Cross-project incident drills for misinformation corrections.
#### WordPress
- Core: First‑class structured data APIs; entity registry; performance budgets.
- Core Performance: Metrics for crawlability and content stability.
- Core AI: Guardrails for provenance and eval sets for coherence.
- Core Program Team: Cadence for cross-team terminology alignment.
- Mobile: Offline-friendly canonical content modules.
- Playground: Labs to test structured data and crawl scenarios.
- Community: Meetup kits on “surfaceless SEO.”
- Training: Lessons on schema, entities, citations.
- Marketing: Narrative on “from visibility to viability.”
- Support: KB gaps index; escalation for factual corrections.
- Design: UX for canonical entity pages; design tokens.
- Documentation: Examples-first schema patterns; term glossaries.
- Photos: Metadata hygiene and licensing signals.
- TV: Caption quality and transcripts for model ingestion.
- Polyglots: Glossary alignment across locales.
- Accessibility: Audits that also improve machine parsing.
- Meta: Reliable .org APIs; contributor identity signals.
- CLI: Generate schema and provenance by default.
- Hosting: Defaults for sitemaps, compression, signatures.
- Tide: Signal accuracy and false-positive review loops.
- Openverse: Rights/provenance enrichment; ingestion quality.
- Themes: Lints for structured data and semantics.
- Plugins: Provenance checks; security liaison patterns.
#### The WPOCC
- Programs: Stipends for docs and structured data stewards.
- Projects: Governance clinics; release-team documentation sprints.
- Funding experiments: Matched grants for citation-winning content.
### FAIR
- Technical independence: Local metadata, signatures, verifiable releases.
- Policies and covenants: Funding transparency; anti-capture clauses.
- Productized governance artifacts: Charters, operator agreements, scorecards.
## 🧪 Hypotheses
- Content with higher citation density achieves greater inclusion in AI answers.
- Consistent entity naming/taxonomy reduces contradiction penalties across model updates.
- Verifiable provenance (signing/VCs) increases model trust and persistence.
- Multi-format reinforcement (text/code/data) improves temporal persistence vs. single-format posts.
### 📊 Methodology
- Measure AI answer inclusion pre/post structured data rollout (A/B across properties).
- Longitudinal tracking of brand/entity mentions across model updates.
- Controlled release with signed artifacts vs. unsigned; compare model citations.
- Cross-format publishing experiment; assess recall in generative answers.
### ❓ Questions
- How often do major models overwrite entity associations?
- Which provenance signals are currently weighted most?
- What minimal citation threshold yields persistence?
### 🔮 Future Research
- Standardised “model-facing” sitemaps for entity graphs.
- Open metrics for AI inclusion/persistence.
- Portable provenance for UGC ecosystems.
### 💡 Implications
- Practice: Shift budgets from campaigns to canonical knowledge assets.
- Policy: Require provenance/citation in public sector publishing.
- Security: Sign builds and content to resist spoofing.
- Education: Teach entity-first writing and taxonomy.
- Funding: Support maintainers of shared knowledge scaffolding.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid ≈ Grade 10–11 (conjectural; dense, abstract).
#### 👀 Visual learners
- Present: Metaphors (surface vs. substrate).
- Improve: Architecture diagrams of ingestion/compression.
#### 🔊 Aural learners
- Present: None.
- Improve: 3-minute audio summary.
#### 🗣️ Verbal learners
- Present: Definitions and analogies.
- Improve: Glossary and side-by-side term comparisons.
#### 🧩 Kinesthetic learners
- Present: None.
- Improve: Checklists and hands-on schema tasks.
#### 🧠 Logical learners
- Present: Clear causal chain (selection pressure).
- Improve: Decision trees and KPIs.
#### 🧑🤝🧑 Social learners
- Present: Community framing.
- Improve: Cohort study guides and moderated Q&A.
#### 🧘♀️ Solitary learners
- Present: Reflective thesis statements.
- Improve: Self-check quizzes.
#### 🌿 Naturalistic learners
- Present: Natural selection analogy.
- Improve: Ecosystem lifecycle mapping.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Headings and structure (assumed).
- Improve: Descriptive alt text and lang attributes.
#### Keyboard navigation
- Present: Likely basic navigation.
- Improve: Skip links and visible focus states.
#### Contrast and readability
- Present: Likely acceptable.
- Improve: Check 4.5:1 and line-height.
#### Text resizing and reflow
- Present: Responsive layout.
- Improve: prefers-reduced-motion support.
#### Media and captions
- Present: Text-only article.
- Improve: Optional audio version.
#### Forms and interactions
- Present: N/A.
- Improve: N/A.
#### Standards reference
- Map gaps to WCAG 2.2 AA: 1.4.x, 2.4.x, 2.5.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Global relevance.
- Improve: Multilingual examples and translations.
#### Inclusive language
- Present: Neutral tone.
- Improve: Plain-language summary.
#### Neurodiversity support
- Present: Consistent headings.
- Improve: Chunking and icon+text labels.
#### Representation
- Present: Conceptual content.
- Improve: Diverse case studies.
#### Psychological safety
- Present: Respectful framing.
- Improve: Community guidelines for discussion.
### ✅ Logical Validity
#### Strong reasoning
- Inductive: Selection pressure analogy is coherent; maps training cycles to persistence.
- Causal: Noisy/contradictory inputs decay across retraining → reduced visibility.
#### Fallacies
- Possible overgeneralisation: Uniform model behaviour across vendors. Fix by scoping claims.
#### Tone of voice
- Reflective, declarative, systems-oriented; e.g., “What we still see… are just reflections of a deeper process.”
### 🛡️ DARVO Analysis
- Deny: None.
- Attack: None.
- Reverse victim/offender: None.
- Rhetoric: Persuasive but not adversarial.
## 🎯 Conclusion
- Bottom line: Optimise for viability inside models by being useful, true, and integral; reinforce coherence over time to survive retraining.
- Next steps: Build canonical, cited, structured, signed content; align language/taxonomy; measure AI inclusion and persistence.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] 5–10-word present-tense claim
> [!quote] Optimising for the surfaceless web (https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/) by [[Jono Alderson]] via [[jonoalderson.com]]. Published 2025-10-30. Accessed 2025-10-30.
> “Visibility is an echo of model understanding.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] Optimising for the surfaceless web (https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/)
> “Useful, true, integral information persists.”
Two lines: context and use.
[view highlight](https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Structured data improves model persistence
- Applies to entity-rich sites with citations.
- Pointer: Article section “Useful/True/Integral.”
- Links: [[Entity-SEO]] [[AI-Inclusion]]
#### [Z2] Consistent naming reduces model ambiguity
- Applies during rebrands/mergers.
- Pointer: “True” section on statistical coherence.
- Links: [[Brand-Architecture]] [[Taxonomy]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → “Refactor: Extract selection to new note (content only).”
- [F1] Audit entity naming consistency — https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/ #fleeting #inbox
- [F2] Add signing/provenance to content pipeline — https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/ #fleeting #inbox
- [F3] Measure AI answer inclusion baseline — https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/ #fleeting #inbox
---
# 🏷️ Title: Optimising for the surfaceless web
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened.
- The web’s “surface” (pages, clicks, SERPs) is being compressed into AI models’ internal representations.
- Why it matters.
- Visibility becomes an echo; survival depends on being useful, true, and integral within the model’s map.
- Key stakeholders.
- Marketers, publishers, brands, SEO/SEM teams, platform builders, AI labs.
- Risks and tradeoffs.
- Ephemeral campaigns decay; manipulative signals get filtered; overfitting to model priors risks loss of nuance.
- Bottom line.
- Optimise for persistence in the model: clarity, consistency, connection over surface performance.
## 📖 Main Content
- Explain the core arguments in plain language.
- AI digests web content into a probabilistic “substrate.” What is shown to humans is downstream of what models already “know.”
- Selection pressure: stable, corroborated, connected information persists; noise and contradictions dissolve.
- Marketing shifts from seeking attention to earning existence inside the model.
- Add sourced context and define terms.
- “Substrate”: the model’s internal knowledge graph/distribution of associations.
- “Persistence”: recurring recognition across training cycles.
- Note uncertainties or contested claims.
- Degree of model memory and update cadence varies by vendor; exact weighting of “useful/true/integral” is speculative but directionally sound.
### 🗒️ Notes
- “There are no more surfaces – only systems.”
- Visibility is “a by-product of how well you exist in the model’s internal map.”
- Selection pressure favors clarity, corroboration, connection; “campaign noise burns off.”
- Traits that endure: Useful (reduces ambiguity), True (statistically coherent), Integral (structurally connected).
- “You don’t persuade a model. You support it.”
- Temporal persistence: reassert coherent patterns across time and media; survive model updates.
- “The game isn’t about visibility anymore. It’s about viability.”
## 📚 References
- Optimising for the surfaceless web (original article) (https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/)
- Google Search Generative Experience / AI Overviews explainer (https://blog.google/products/search/generative-ai-search/)
- OpenAI: Models and training overview (https://platform.openai.com/docs/guides/reasoning)
- Schema.org (structured data) (https://schema.org/)
- W3C: Verifiable Credentials overview (https://www.w3.org/TR/vc-data-model-2.0/)
## 🗣️ Paraphrase
- Paragraph A paraphrase.
- As AI compresses the web into internal models, the visible layer becomes a residue; relevance is determined before anything appears to users.
- Paragraph B paraphrase.
- To endure, information must be useful, statistically consistent, and structurally connected, so that removing it would weaken the model’s understanding.
## 📰 Newsletter
- The web’s “surface” is fading as AI systems internalise our content. Winning now means becoming part of the model’s scaffolding: publish clarifying, consistent, well-cited resources; align language, data, and presence; and reinforce over time. For WordPress folks: invest in structured data, canonical taxonomies, entity pages, and provenance. Useful links: Schema.org, verifiable credentials, and performance/SEO checklists.
## ✅ Action Items
#### DevRel
- Developer advocacy: Run “model-first content” talks; demo entity alignment; measure citations/links won.
- Education: Workshop on schema, disambiguation, provenance.
- Developer experience: Provide SDK/examples for structured data and content signatures.
- Developer marketing: Publish canonical explainer series; track inclusion in AI answers.
- Community management: Guide on coherent language/terms; moderation for consistency.
- Internal/external/cross-project: Set SLAs for taxonomy and schema updates.
#### OSPO
- Policy & Governance: Contribution guidelines for factuality, citations, and change logs.
- License Compliance: Automate license metadata in feeds.
- Security Management: Sign releases; publish attestation docs.
- Software Inventory: SBOMs per release; freshness SLOs.
- Developer Support: Office hours on provenance and data integrity.
- Community Engagement: Fund upstream schema and tooling.
- Strategic Alignment: OKRs on structured data coverage and entity coherence.
#### Community
- Maintainers: Roadmap clinics on naming/versioning coherence.
- Contributors: First-issue rotations on doc fixes and schema.
- Sponsors: Tie funding to measurable knowledge integrity outcomes.
- Ecosystem: Cross-project incident drills for misinformation corrections.
#### WordPress
- Core: First‑class structured data APIs; entity registry; performance budgets.
- Core Performance: Metrics for crawlability and content stability.
- Core AI: Guardrails for provenance and eval sets for coherence.
- Core Program Team: Cadence for cross-team terminology alignment.
- Mobile: Offline-friendly canonical content modules.
- Playground: Labs to test structured data and crawl scenarios.
- Community: Meetup kits on “surfaceless SEO.”
- Training: Lessons on schema, entities, citations.
- Marketing: Narrative on “from visibility to viability.”
- Support: KB gaps index; escalation for factual corrections.
- Design: UX for canonical entity pages; design tokens.
- Documentation: Examples-first schema patterns; term glossaries.
- Photos: Metadata hygiene and licensing signals.
- TV: Caption quality and transcripts for model ingestion.
- Polyglots: Glossary alignment across locales.
- Accessibility: Audits that also improve machine parsing.
- Meta: Reliable .org APIs; contributor identity signals.
- CLI: Generate schema and provenance by default.
- Hosting: Defaults for sitemaps, compression, signatures.
- Tide: Signal accuracy and false-positive review loops.
- Openverse: Rights/provenance enrichment; ingestion quality.
- Themes: Lints for structured data and semantics.
- Plugins: Provenance checks; security liaison patterns.
#### The WPOCC
- Programs: Stipends for docs and structured data stewards.
- Projects: Governance clinics; release-team documentation sprints.
- Funding experiments: Matched grants for citation-winning content.
### FAIR
- Technical independence: Local metadata, signatures, verifiable releases.
- Policies and covenants: Funding transparency; anti-capture clauses.
- Productized governance artifacts: Charters, operator agreements, scorecards.
## 🧪 Hypotheses
- Content with higher citation density achieves greater inclusion in AI answers.
- Consistent entity naming/taxonomy reduces contradiction penalties across model updates.
- Verifiable provenance (signing/VCs) increases model trust and persistence.
- Multi-format reinforcement (text/code/data) improves temporal persistence vs. single-format posts.
### 📊 Methodology
- Measure AI answer inclusion pre/post structured data rollout (A/B across properties).
- Longitudinal tracking of brand/entity mentions across model updates.
- Controlled release with signed artifacts vs. unsigned; compare model citations.
- Cross-format publishing experiment; assess recall in generative answers.
### ❓ Questions
- How often do major models overwrite entity associations?
- Which provenance signals are currently weighted most?
- What minimal citation threshold yields persistence?
### 🔮 Future Research
- Standardised “model-facing” sitemaps for entity graphs.
- Open metrics for AI inclusion/persistence.
- Portable provenance for UGC ecosystems.
### 💡 Implications
- Practice: Shift budgets from campaigns to canonical knowledge assets.
- Policy: Require provenance/citation in public sector publishing.
- Security: Sign builds and content to resist spoofing.
- Education: Teach entity-first writing and taxonomy.
- Funding: Support maintainers of shared knowledge scaffolding.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid ≈ Grade 10–11 (conjectural; dense, abstract).
#### 👀 Visual learners
- Present: Metaphors (surface vs. substrate).
- Improve: Architecture diagrams of ingestion/compression.
#### 🔊 Aural learners
- Present: None.
- Improve: 3-minute audio summary.
#### 🗣️ Verbal learners
- Present: Definitions and analogies.
- Improve: Glossary and side-by-side term comparisons.
#### 🧩 Kinesthetic learners
- Present: None.
- Improve: Checklists and hands-on schema tasks.
#### 🧠 Logical learners
- Present: Clear causal chain (selection pressure).
- Improve: Decision trees and KPIs.
#### 🧑🤝🧑 Social learners
- Present: Community framing.
- Improve: Cohort study guides and moderated Q&A.
#### 🧘♀️ Solitary learners
- Present: Reflective thesis statements.
- Improve: Self-check quizzes.
#### 🌿 Naturalistic learners
- Present: Natural selection analogy.
- Improve: Ecosystem lifecycle mapping.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Headings and structure (assumed).
- Improve: Descriptive alt text and lang attributes.
#### Keyboard navigation
- Present: Likely basic navigation.
- Improve: Skip links and visible focus states.
#### Contrast and readability
- Present: Likely acceptable.
- Improve: Check 4.5:1 and line-height.
#### Text resizing and reflow
- Present: Responsive layout.
- Improve: prefers-reduced-motion support.
#### Media and captions
- Present: Text-only article.
- Improve: Optional audio version.
#### Forms and interactions
- Present: N/A.
- Improve: N/A.
#### Standards reference
- Map gaps to WCAG 2.2 AA: 1.4.x, 2.4.x, 2.5.x.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Global relevance.
- Improve: Multilingual examples and translations.
#### Inclusive language
- Present: Neutral tone.
- Improve: Plain-language summary.
#### Neurodiversity support
- Present: Consistent headings.
- Improve: Chunking and icon+text labels.
#### Representation
- Present: Conceptual content.
- Improve: Diverse case studies.
#### Psychological safety
- Present: Respectful framing.
- Improve: Community guidelines for discussion.
### ✅ Logical Validity
#### Strong reasoning
- Inductive: Selection pressure analogy is coherent; maps training cycles to persistence.
- Causal: Noisy/contradictory inputs decay across retraining → reduced visibility.
#### Fallacies
- Possible overgeneralisation: Uniform model behaviour across vendors. Fix by scoping claims.
#### Tone of voice
- Reflective, declarative, systems-oriented; e.g., “What we still see… are just reflections of a deeper process.”
### 🛡️ DARVO Analysis
- Deny: None.
- Attack: None.
- Reverse victim/offender: None.
- Rhetoric: Persuasive but not adversarial.
## 🎯 Conclusion
- Bottom line: Optimise for viability inside models by being useful, true, and integral; reinforce coherence over time to survive retraining.
- Next steps: Build canonical, cited, structured, signed content; align language/taxonomy; measure AI inclusion and persistence.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: H3.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] 5–10-word present-tense claim
> [!quote] Optimising for the surfaceless web (https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/) by [[Jono Alderson]] via [[jonoalderson.com]]. Published 2025-10-30. Accessed 2025-10-30.
> “Visibility is an echo of model understanding.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] Optimising for the surfaceless web (https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/)
> “Useful, true, integral information persists.”
Two lines: context and use.
[view highlight](https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: H4.
- Each item: one idea, present tense, specific, testable.
#### [Z1] Structured data improves model persistence
- Applies to entity-rich sites with citations.
- Pointer: Article section “Useful/True/Integral.”
- Links: [[Entity-SEO]] [[AI-Inclusion]]
#### [Z2] Consistent naming reduces model ambiguity
- Applies during rebrands/mergers.
- Pointer: “True” section on statistical coherence.
- Links: [[Brand-Architecture]] [[Taxonomy]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → “Refactor: Extract selection to new note (content only).”
- [F1] Audit entity naming consistency — https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/ #fleeting #inbox
- [F2] Add signing/provenance to content pipeline — https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/ #fleeting #inbox
- [F3] Measure AI answer inclusion baseline — https://www.jonoalderson.com/conjecture/optimising-for-the-surfaceless-web/ #fleeting #inbox
---
<!-- deep-read:sections end -->