Skip to content

Add KB governance and profile-pack review workflow #49

@WalksWithASwagger

Description

@WalksWithASwagger

Context

The local-first WhisperForge loop now has enough KB, RAG, profile, and voice-anchor surface area that agents need explicit governance before generation starts. This issue adds reviewer-visible controls for canonical, stale, ignored, private-looking, duplicate, and oversized profile context without requiring code edits.

Acceptance Criteria

  • Profile KB audit separates stale, duplicate, private-looking, and oversized findings into clear reviewer actions.
  • A reviewer can mark canonical voice anchors and intentionally ignored files without editing code.
  • Generation surfaces a concise warning when selected profile context has unresolved governance findings.
  • Docs explain the private/stale policy and how future agents should treat flagged context.

Tests/Evals

  • Add or update focused tests around KB audit/governance classification and selected-context warning behavior.
  • Keep existing credential-free fixture evals passing.

Verification

  • make test
  • make eval-fixture
  • git diff --check

Agent Instructions

Roadmap ID: wf-kb-governance.

Work from whisperforge_core/kb_audit.py, whisperforge_core/prompts.py, the KB dialog in ui/dialogs.py, and the generation path that selects profile context. Prefer a small declarative profile-side governance file over hidden code rules. Preserve local-first behavior and avoid outbound writes. If policy is ambiguous, implement conservative defaults: flagged private-looking content should warn before use, ignored content should be excluded, and canonical voice anchors should be explicitly marked rather than inferred from every KB file.

Out of Scope

  • No hosted auth or multi-user governance model.
  • No automatic deletion of KB files.
  • No changes to transcription provider defaults.
  • No autonomous publishing or routing.

Linear

Not linked yet. Source roadmap entries: ops/roadmap/features.json and docs/NEXT-ROUND-PLAN-2026-05-19.md.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent:readyIssue passed intake quality and is ready for an agent attempt.kind:featureUser-facing feature delivery.priority:p1High-priority delivery work.repo:spektorAIWork in the WalksWithASwagger/spektorAI repository.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions