Linking, Connections, Backlinks, and Smart Links in LLM Wiki

Filed answer: how connections work in the LLM Wiki ecosystem — from wikilinks to knowledge graphs to forward-only linking.

The fundamental unit of connection in the LLM Wiki pattern is the wikilink (backtick-wrapped syntax). During ingest, the LLM reads a source, identifies entities and concepts, and creates links between the new page and existing pages. The result is an implicit knowledge graph: pages are nodes, wikilinks are edges.

The core value is not storage — it is that the LLM discovers correlations between sources you saved separately that you would never have drawn yourself. The canonical example: two independent sources where one references the other, and the LLM creates the cross-link automatically. ^[raw/transcripts/sozai-fable-llm-wiki-video.md] As Nate Herk put it: “I didn’t have to connect these concepts at all.”

The Five Connection Methods

The connection-methods comparison page documents five distinct approaches:

  1. Karpathy Lint — post-ingest checks for broken links, orphan pages (zero inbound links), and contradictions. No external tooling required. The LLM does the checking.

  2. Wyndo Production Guardrails — proactive prevention: link cap of 5-8 per page, twice-referenced entity rule (only create entity pages after 2+ mentions), forward-only linking (never retroactively add links to old pages), edit ceiling of 2-5 pages per ingest.

  3. Wikilint CLI — Oleg Ivanchenko’s Go tool that enforces structural invariants: no orphan pages, no broken wikilinks, no duplicate slugs, every page has exactly one H1 and required sections. Each batch must pass wikilint: OK.

  4. OKF Consumer Tolerance — the v0.1 draft specifies that consumers MUST NOT reject a bundle for broken cross-links, missing index.md, or unknown frontmatter. This is a baseline for interop, not a prohibition on stricter local lint.

  5. Graph/RAG Layer — systems like LightRAG, HippoRAG, and GraphRAG that build explicit graph structures from text. Useful at scale when the wiki outgrows manual navigation. Premature for small vaults.

Backlinks are the inverse of wikilinks: which pages point to a given page. The lint operation checks for orphan pages — pages with zero backlinks. The vault rule requiring 2+ outbound links per page exists precisely to prevent orphans. In obsidian, the backlinks panel shows this visually; in the LLM workflow, the lint pass catches it automatically.

Forward-Only Linking

A critical guardrail from the Wyndo production setup: during ingest, the LLM never retroactively adds links to old pages. This bounds the cost of each batch to a maximum of 5 existing pages updated. Without this rule, each ingest could cascade into touching dozens of pages.

Open Knowledge Format uses relative Markdown paths ([Orders](/tables/orders.md)) rather than Obsidian-style wikilinks (backtick-wrapped syntax). Both serve the same purpose — connecting knowledge units — but use different syntax. An OKF bundle can be converted to wikilinks for Obsidian consumption, or wikilinks can be converted to relative paths for OKF export. The vault uses wikilinks natively and OKF frontmatter for structure.

In the LLM Wiki pattern, the primary connection mechanism is the explicit link written by the LLM — not vector similarity. Embeddings play a secondary role: routing queries to the right page, suggesting potential new links, and initial clustering of sources. But the “glue” of the system is the deliberate wikilink, not cosine similarity.

Graph Layer (Optional)

Some implementations add an explicit graph layer beyond wikilinks. Denser.ai’s compiler, for example, produces nodes.jsonl, edges.jsonl, graph.sqlite, and graph.graphml alongside the wiki — enabling graph algorithms and visualization. ^[raw/articles/denser-llm-wiki-analysis.md] LightRAG and HippoRAG build graph structures from entity-relation extraction for retrieval, not navigation.

Practical Rules for This Vault

Based on the synthesis above, this vault follows:

  • Wikilinks as primary mechanism — the LLM creates them during ingest
  • Link cap of 5-8 per page — prevents hub pages
  • Forward-only linking — ingest never backfills
  • 2+ outbound links per page — prevents orphans
  • Lint after every batch — checks for broken links, orphans, contradictions
  • OKF-tolerant baseline — we lint locally but don’t break on tolerance violations
  • No graph layer yet — premature for 36 pages; revisit at 100+

Sources

^[raw/articles/karpathy-llm-wiki-gist.md] ^[raw/articles/genai-unplugged-llm-wiki.md] ^[raw/articles/levelup-llm-wiki-deep-dive.md] ^[raw/articles/google-okf-spec.md] ^[raw/articles/venturebeat-llm-wiki.md] ^[raw/transcripts/sozai-fable-llm-wiki-video.md] ^[raw/papers/pesquisa-aprofundada-padrao-llm-wiki.md]