{
  "canonicalUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/",
  "correctionStatus": "CURRENT K05 RELEASE",
  "findings": [
    "The report identifies language detection, tokenization, sparse retrieval, cross-script search, and rendering as discoverability challenges.",
    "NFC normalization supports stable Unicode comparison and should be tested at ingestion, URL, and output boundaries.",
    "Language and script tags must describe actual content; ang-Runr is inappropriate for arbitrary modern English transliteration or symbolic protocol tokens.",
    "Runic hostnames use IDNA A-labels for transport, while path and content encoding follow separate URI and UTF-8 rules.",
    "Search systems may fragment rare Runic text, making visible transliteration, glossary links, and cross-script aliases useful.",
    "Hidden English translations created only for crawlers risk deceptive cloaking and accessibility misuse.",
    "ARIA labels must serve accessible naming needs and cannot replace visible equivalents for long prose.",
    "Structured data must accurately represent visible page content and cannot guarantee ranking or citation.",
    "Robots directives, sitemaps, canonicals, titles, descriptions, internal links, and user-visible answer pages remain foundational.",
    "K08 publishes a discoverability test plan with zero claims of guaranteed indexing, ranking, or generative citation."
  ],
  "headings": [
    "Architectural Discoverability and Generative Engine Optimization for Non-Latin Historical Scripts: A Framework for Fuþorc-Only Ecosystems",
    "Unicode Architecture, Normalization, and Runic Script Indexing",
    "Language Identification and BCP 47 Script Subtagging",
    "Tokenization Mechanics and the Generative Byte-Fallback Dilemma",
    "Information Retrieval: Lexical Sparsity and Dense Semantic Embedding",
    "Accessibility Standards and the Anti-Cloaking Paradox",
    "Answer-Engine Architecture and Crawler Access Management",
    "Server-Level Crawler Matrix",
    "Search Entity Architecture and On-Page Optimization",
    "Structured Data: JSON-LD Translation Schemas",
    "JSON-LD Architectural Model",
    "Myths and Unsupported SEO Claims",
    "Testing Methodology and Measurement Framework",
    "100 Candidate Fuþorc Search Concepts",
    "50 FAQ and Query Intents",
    "50 Page-Cluster Concepts",
    "Conclusion",
    "Works cited"
  ],
  "id": "REP-K08-067",
  "lastReviewed": "2026-08-16",
  "machineRecordUrl": "https://xn--mwe.com/data/reports/futhorc-discoverability-architecture.json",
  "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md",
  "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.",
  "rawSourcePublic": false,
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "slug": "futhorc-discoverability-architecture",
  "source": "futhorc-seo-discoverability-research-plan.md",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262",
  "sourceSizeBytes": 48943,
  "sourceStatus": "K08 governed research input; technical, historical, legal, security, and performance propositions require explicit source or empirical validation.",
  "sourceTitle": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO",
  "status": "PROJECT TECHNICAL PROPOSAL",
  "summary": "A governed discoverability plan for non-Latin historical-script content, corrected to require visible user-accessible semantics and prohibit hidden crawler-only translations.",
  "title": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO",
  "topic": "runic-digital-infrastructure",
  "type": "ReportSynthesis"
}