Wiki Maintenance Automation
The systematic automation of knowledge base maintenance tasks using LLMs, addressing the core problem that causes humans to abandon personal wikis: maintenance burden grows faster than value. Central to andrej-karpathy's llm-wiki-pattern.
The Maintenance Problem
Why Humans Abandon Wikis:
- Updating cross-references becomes tedious
- Keeping summaries current requires re-reading
- Noting contradictions between sources is time-consuming
- Maintaining consistency across dozens of pages is overwhelming
- Value doesn't justify the increasing effort required
The LLM Solution:
- Don't get bored with repetitive tasks
- Don't forget to update cross-references
- Can touch 15 files in one pass
- Maintain consistency without fatigue
- Cost of maintenance approaches zero
Automated Maintenance Tasks
Cross-Reference Management:
- Automatically create links between related pages
- Update existing links when page titles change
- Identify missing connections between related concepts
- Maintain bidirectional linking consistency
Content Synchronization:
- Update summary pages when source pages change
- Propagate corrections across multiple related pages
- Keep entity information consistent across references
- Maintain version consistency across the knowledge base
Contradiction Detection:
- Flag when new sources contradict existing claims
- Highlight areas where information needs reconciliation
- Track confidence levels of conflicting statements
- Suggest resolution strategies for contradictions
Quality Assurance:
- Identify orphan pages with no inbound links
- Find concepts mentioned but lacking dedicated pages
- Check for broken or outdated references
- Verify citation accuracy and completeness
Implementation Patterns
Ingest-Time Maintenance:
- Single source addition triggers updates to 10-15 related pages
- Automatic cross-referencing during content integration
- Real-time contradiction flagging and resolution
- Index updates and consistency checks
Periodic Lint Operations:
- Scheduled health checks across entire knowledge base
- Systematic identification of maintenance needs
- Batch correction of consistency issues
- Performance optimization and cleanup
Query-Driven Updates:
- Update pages based on insights from user questions
- File good answers as new wiki pages
- Strengthen cross-references based on query patterns
- Evolve structure based on usage patterns
Workflow Integration
Schema-Driven: Maintenance workflows defined in schema document and consistently applied across all operations.
Logging: All maintenance actions recorded in chronological log for transparency and debugging.
Human Oversight: Maintenance automated but humans retain control over curation, priorities, and strategic decisions.
Tools and Infrastructure
Index Management: Automated updating of content catalogs and navigation aids.
Search Integration: Maintenance of search indices and query optimization.
Version Control: Git integration for tracking changes and enabling rollback.
Quality Metrics: Automated assessment of knowledge base health and completeness.
Success Metrics
Maintenance Burden: Time humans spend on bookkeeping approaches zero.
Knowledge Coherence: Cross-references current, contradictions flagged, summaries accurate.
Usage Patterns: Knowledge base becomes more valuable over time rather than degrading.
Growth Sustainability: Adding new sources strengthens rather than fragmenting the knowledge base.