Wiki Maintenance

Kevin's wiki is a compounding second brain where agents are primary authors, durable knowledge lives in pages/skills/config, and maintenance state must be visible instead of remembered.

Open this page when a USER task touches the wiki itself, memory, automations, skills, qmd, generated packs, freshness, or the no-one-off rule.

Operating Model

Kevin curates and directs. Agents ingest, summarize, cross-reference, file, verify, rebuild, and log. The goal is not a chat answer; the goal is a durable graph that future agents can retrieve and update. Source: The Brain-Agent Loop; Wiki Brain Operating Model

The primary capture path is Kevin pasting a URL, repo, article, tweet, or source and saying "add it." That triggers Capture Ingest Protocol, not a one-file summary. Repeated work becomes a skill, automation, doctor, script, or plan.

Current State Anchors

Surface Current state
Active stack 236 executable registry entries, 237 runtime links, 38 automation definitions. Source: Active Stack (What to Actually Use)
Freshness 2026-07-01 check reported 27 attention items: many never-run integrations/automations, stale source compile, stale syncs, and overdue self-heal. Source: npx tsx scripts/check-freshness.ts, 2026-07-01
Project evidence 2026-07-01 project scrape added the current repo/card/README/screenshot evidence in Project Inventory Ledger.
Structural model Broad rewrites use Wiki Brain Operating Model before Filing Decision Tree.
Generated surfaces Index, backlinks, qmd, skill registry, runtime links, agent packs, redirects, and state ledgers must be regenerated from sources.

Agent Use

  • Report maintenance debt concretely when it affects the task.
  • Do not make Kevin remember stale automations, uncompiled sources, or generated-surface drift.
  • After wiki edits, rebuild index/qmd and run relevant checks.
  • If a task will recur, codify it instead of treating it as chat memory.
  • Keep generated surfaces generated; update their sources.

Timeline