~/wiki
Récent+ Ajouter

Bookkeeping Automation

Confiance : high
bookkeeping-automationllm-wiki-patternmaintenance-automationcross-referencingconsistency-maintenanceandrej-karpathytedious-taskswiki-abandonment

The automation of tedious knowledge management tasks that typically cause humans to abandon personal wikis. Core insight behind andrej-karpathy's llm-wiki-pattern - LLMs excel at the systematic maintenance work that humans find burdensome but that's essential for knowledge base health.

The Abandonment Problem

Human Pattern: Start enthusiastic personal wiki → maintenance burden grows → abandon due to tedium Root Cause: "The maintenance burden grows faster than the value"

Tedious Tasks That Cause Abandonment

  • Updating cross-references when adding new information
  • Keeping summaries current as understanding evolves
  • Noting when new data contradicts old claims
  • Maintaining consistency across dozens of pages
  • Filing and organizing information systematically
  • Creating and maintaining category structures

LLM Advantages for Bookkeeping

No Boredom: LLMs don't get tired of repetitive maintenance tasks Perfect Memory: Never forget to update a cross-reference or flag a contradiction
Batch Processing: Can touch 15 files in one pass during integration Systematic Approach: Consistently apply rules and conventions across entire knowledge base Pattern Recognition: Identify maintenance needs humans might miss

Automated Bookkeeping Tasks

During ingest-workflow

  • Update entity pages when new sources mention existing entities
  • Create new entity pages for newly mentioned people/organizations/tools
  • Revise concept summaries with new information
  • Add cross-references between related topics
  • Flag contradictions with existing content
  • Update index and categorization

During query-workflow

  • File valuable answers as new wiki pages
  • Update existing pages with insights from queries
  • Create new cross-references discovered through questioning

During lint-workflow

  • Find and fix broken internal links
  • Identify orphan pages needing better integration
  • Suggest missing cross-references
  • Flag outdated claims for human review

Cost-Benefit Transformation

Traditional Wiki:

  • High human maintenance cost
  • Maintenance burden compounds with scale
  • Value growth plateaus while cost accelerates

LLM Wiki Pattern:

  • Near-zero maintenance cost (automated)
  • Value compounds while cost stays flat
  • Sustainable knowledge accumulation

Human-LLM Role Division

Human Responsibilities:

  • Curate sources (what to include)
  • Direct analysis (what to emphasize)
  • Ask good questions (what to explore)
  • Think about meaning (what it all means)

LLM Responsibilities:

  • All bookkeeping and maintenance
  • Cross-referencing and consistency
  • Systematic organization and filing
  • Routine updates and corrections

Implementation Strategy

The key is documenting bookkeeping requirements in the schema layer so LLMs can execute them consistently. This includes:

  • Cross-reference conventions
  • Page update triggers
  • Consistency checking rules
  • Integration workflows
  • Quality standards

See also