LLM Wiki — Synaptic Lattice

Lint

Properties1
tagsconcept, workflow, guardrail, llm-wiki

Leitura de 3 min

Definition

Lint is the health check operation for the LLM Wiki. It scans the wiki for structural issues: orphan pages (no inbound links), broken wikilinks (links to non-existent pages), missing frontmatter, contradictions, and stale content. Regular linting ensures the knowledge base remains healthy and trustworthy.

Key Points

  • Karpathy defined three lint checks in his original gist: broken links, orphan pages, and contradictions
  • The Level Up Coding deep dive documented Oleg Ivanchenko’s wikilint Go CLI tool that enforces structural invariants
  • Additional checks: missing frontmatter fields, tags not in taxonomy, pages without 2+ outbound links
  • The principle: each batch must pass lint before being considered complete
  • Linting can also surface contradictions between sources that human readers missed
  • The error-book extends lint into a corrective feedback loop by recording recurring construction error patterns

Quality Scoring and Self-Healing

LLM Wiki v2 extends lint beyond detection into active repair. ^[raw/articles/llm-wiki-v2-rohitg00-2026.md] Every piece of content the LLM writes should get a quality score — the LLM self-evaluates or uses a second pass. Content below threshold gets flagged for review or rewritten.

Self-healing: lint should auto-fix what it can — orphan pages get linked or flagged, stale claims get marked, broken cross-references get repaired. The wiki should tend toward health on its own, not only when the human remembers to ask.

Implications

Self-healing transforms lint from a suggestion into an automated maintenance layer. However, critics caution that auto-fixing can silently accept bad LLM outputs — the trade-off is maintenance burden (human fixes) vs correctness risk (silent corruption). For this vault, auto-fix on simple issues (broken links pointing to renamed pages) is low-risk; auto-fix on semantic issues (claim reconciliation) requires more caution.

Format Baseline and Local Rules

The OKF v0.1 draft says consumers must tolerate missing optional metadata, unknown frontmatter, broken cross-links, and a missing index.md. This vault can still lint for those conditions as local quality and navigation rules; a lint finding is not, by itself, a claim that an OKF consumer must reject the bundle.

This vault’s local lint governance distinguishes an intended wiki reference from a literal link-syntax example used in explanatory prose. Only references meant to resolve to a vault page are reported as broken links; documentation examples are not navigation edges. This is a vault-specific interpretation rule, not behavior specified by the cited LLM Wiki sources.

Relationship to Connection Methods

Lint is the health-check component of the broader connection-methods ecosystem. While lint checks for broken links and orphans, the connection-methods comparison shows how other approaches (Wyndo guardrails, Wikilint CLI, OKF tolerance, graph/RAG layers) prevent decay before lint is needed or scale connections differently.

  • llm-wiki — Lint is one of the three core LLM Wiki operations
  • ingest — Lint follows ingest to verify the wiki is healthy
  • query — A well-linted wiki produces better query results
  • rule — Lint enforces the guardrails defined in the rules
  • connection-methods — How different tools create and validate connections

Sources

^[raw/articles/karpathy-llm-wiki-gist.md] ^[raw/articles/levelup-llm-wiki-deep-dive.md]

Visão de gráfico

Backlinks