About Services Tools Blog Contact us

Keeping a Knowledge Base Clean

A local model works through a to-do list of clean-up tasks for a knowledge base. It proposes plans for out-of-date facts and conflicting links, and a person approves each one.

  • Agentic Workflows
  • Professional services
  • Agent skill
  • Product
  • Local/private
  • 2026

The problem

A knowledge base that only takes in new material fills up with doubtful and conflicting claims. Nobody has time to check them all by hand. A model could check them, but it must not rewrite the database on a hunch. So the clean-up needs a model that proposes and a person who decides.

What it does

Fixed rules add a task for one clean-up skill, with a reason and a scope. The assistant takes one task, reads the related facts, and proposes lowering confidence, adding detail, keeping both versions or just reporting. The plan is posted as a trial that changes nothing. A person applies or dismisses it, and verified facts are never touched.

Outcomes

  • Bad links sit on a to-do list instead of piling up unseen.
  • A reviewer gets one plan per task and can accept or dismiss it.
  • Two contradicting claims stay side by side when both should remain.
  • The knowledge base changes only when a person applies a plan.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Housekeeping dry run only

2 open dry runs · 0 applied in this sitting · 2 ground-truth rows locked

HK-188 · contradiction sweep dry run

Packed subgraph: Halebrook supply · 2 edges · near-duplicate descriptions

Reed Mill supplies cloth to Halebrook.

0.82

Halebrook buys cloth from Reed Mill.

0.74

Proposed. The graph has not changed.

HK-204 · stale review dry run

Low confidence · last confirmed 14 Nov 2025 · no newer note

Reed Mill lead time is three days.

0.31

Proposed. The graph has not changed.

Apply
Waiting for a person. The agent cannot write.

Typed plans

What the agent posted not yet a write
TicketOpWhyState
HK-188 keep both Same supply, two directions dry run
HK-204 weaken −0.10 Confidence 0.31, no corroboration dry run
Not in either plan

No delete. No change of scope. No promotion to ground truth. A dismiss posts a note and leaves the edge as it was.

Epistemic lock

StatementLevelHygiene
Halebrook’s account with Reed Mill was signed in 2024.ground truthout of bounds
Reed Mill weaves cloth in West Yorkshire.ground truthout of bounds
Reed Mill lead time is three days.assertedin HK-204
Boundary check
Locked rows are visible so a reviewer can see them, not edit them.

How it works

  1. Add a task that names one skill, a reason and a scope.
  2. Take one task and gather the related facts.
  3. For an out-of-date or doubtful fact, propose lowering confidence, adding detail or reporting it.
  4. For near-duplicate or opposing links, propose lowering confidence with a clarification, or keep both.
  5. Post the plan as a trial that changes nothing.
  6. A person applies or dismisses the plan. Verified facts are not touched.

Pipeline

flowchart LR
  A[Trigger] --> B[Ticket]
  B --> C[Subgraph]
  C --> D[Stale review]
  C --> E[Contradiction check]
  D --> F[Dry-run plan]
  E --> F
  F --> G[Human apply]