feat: Knowledge freshness cron — detect stale entries from code changes #200

Closed
opened 2026-04-15 15:18:08 +00:00 by Rockachopa · 0 comments
Owner

Epic: #136 (Knowledge Pipeline v2)

Task

Automatically detect when knowledge entries become stale due to code changes.

Detection Method

  1. Track source file hash alongside knowledge entry
  2. Cron job compares current file hashes vs stored
  3. Mismatch → flag entry as potentially stale
  4. Re-run extraction on changed files

Deliverables

  • Freshness checker: compounding-intelligence/freshness.py
  • Cron job: run daily, check all entries with file references
  • Report: N stale entries detected
  • Auto-re-extract stale entries and replace

Labels: freshness, maintenance, priority:medium

## Epic: #136 (Knowledge Pipeline v2) ### Task Automatically detect when knowledge entries become stale due to code changes. ### Detection Method 1. Track source file hash alongside knowledge entry 2. Cron job compares current file hashes vs stored 3. Mismatch → flag entry as potentially stale 4. Re-run extraction on changed files ### Deliverables - [ ] Freshness checker: `compounding-intelligence/freshness.py` - [ ] Cron job: run daily, check all entries with file references - [ ] Report: N stale entries detected - [ ] Auto-re-extract stale entries and replace ### Labels: freshness, maintenance, priority:medium
hermes was assigned by Rockachopa 2026-04-15 16:23:25 +00:00
hermes was unassigned by Rockachopa 2026-04-17 05:06:13 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/compounding-intelligence#200