Skip to content

Add knowledge-base inventory and health audit #14

Description

@WalksWithASwagger

Context

The KK knowledge base is now large enough to be a product asset and a product risk. WhisperForge needs to show what exists, what changed, and what may be stale, duplicate, private, or confusing.

Source: docs/WHISPERFORGE-MASTER-PLAN-2026-05-18.md (wf-kb-inventory, Phase 2).

Linear: BC-222.

Acceptance Criteria

  • Add an inventory command or UI panel for profile knowledge-base files with filename, size, modified time, rough token count, and detected role.
  • Flag likely stale, duplicate, empty, oversized, or private/sensitive files using conservative heuristics.
  • Summarize profile-level health in a compact report that can be exported or copied.
  • Keep existing profile loading behavior unchanged for valid current profiles.
  • Document how agents should use the audit before changing prompts or KB docs.

Tests/Evals

  • Unit tests with fixture KB folders for empty, duplicate, stale, and oversized cases.
  • No external API calls required.

Verification

  • make test
  • python3 -m json.tool ops/roadmap/features.json
  • git diff --check

Agent Instructions

Use structured filesystem metadata and existing prompt/profile helpers where possible. Avoid judging content quality too aggressively; surface signals, not absolute truth.

Out of Scope

Do not rewrite or delete knowledge-base files automatically.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind:featureUser-facing feature delivery.priority:p0Critical or first-wave delivery work.repo:spektorAIWork in the WalksWithASwagger/spektorAI repository.review-readyAgent-created PR is ready for human review.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions