Skip to content

Feature: Knowledge decay / freshness scoring #32

@bwl

Description

@bwl

Use Case

Knowledge bases rot silently. Notes captured a year ago may be outdated, wrong, or irrelevant. No competitor actively fights knowledge decay — Forest should.

Nodes should age. Old, unvisited nodes get flagged for review or archival. Edge weights could decay over time, making stale connections weaker.

Current Workaround

None. All nodes are treated as equally fresh regardless of age or access.

Proposed Solution

  • Track `last_accessed` timestamp on nodes (updated on read/search hit)
  • `forest stale` — list nodes that haven't been accessed in N days
  • `forest stale --review` — interactive triage: keep, archive, update, delete
  • Optional: decay function on edge scores — edges between stale nodes lose weight over time
  • Optional: freshness indicator in search results

Context

  • Forest node: `d653` (roadmap), `8e3e` (competitive analysis)
  • Competitive edge: NO PKM tool does this — genuinely novel

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions