KB maintenance

Type: index · Status: current

How an agent-operated KB stays healthy as it grows. Detection, operations, and the dynamics that govern quality over time. For how the KB is built, see kb-design. For document structure, see document-system.

Dynamics

• entropy-management-must-scale-with-generation-throughput — cleanup throughput must match generation throughput; agents replicate patterns including bad ones, so without proportional maintenance quality degrades with volume
• traversal-improves-the-graph — every traversal is a read-write opportunity; agents should log improvement opportunities during reading, then process them separately to avoid context-switching
• title-as-claim-exposes-commitments-enabling-popperian-maintenance — claim titles make maintenance cheap: scan the index, ask "do I still believe this?", open only the doubtful ones

Detection

• quality-signals-for-kb-evaluation — composite oracle from graph-topology, content-proxy, and LLM-hybrid signals; the evaluation layer the learning loop needs
• notes-need-quality-scores-to-scale-curation — note quality scores (status, type, inbound links, recency) filter /connect candidates as the KB grows
• semantic-review-catches-content-errors-that-structural-validation-cannot — four semantic checks (enumeration completeness, grounding alignment, boundary-case coverage, internal consistency) that require LLM adversarial reading
• link-graph-plus-timestamps-enables-make-like-staleness-detection — existing links encode dependencies; comparing note and target timestamps flags staleness without new annotation
• stale-indexes-are-worse-than-no-indexes — a missing index entry suppresses search entirely; absence of an index degrades to search, presence of a stale index prevents it

Operations

• maintenance-operations-catalogue-should-stage-distillation-into-instructions — staging catalogue for periodic operations before they are distilled into reusable procedures
• periodic-kb-hygiene-should-be-externally-triggered-not-embedded-in-routing — periodic audits belong in externally triggered operations, not always-loaded routing docs

Related Areas

• kb-design — parent area: architecture and design of the KB itself
• document-system — type system and validation that maintenance operations check against
• links — linking methodology that staleness detection and quality signals operate on