alive-prune

Weekly log maintenance for walnuts is automated by a scheduled prune job that scans all walnuts weekly to detect oversized logs and stale insights, then outputs non-destructive recommendations for review. It validates inputs and respects draft statuses before presenting actions.

Identifying stale bundles and oversized logs across multiple walnuts is handled by a weekly review process that evaluates each walnut's entries to surface candidates for archiving or synthesis, presenting a prioritized list of maintenance actions to keep knowledge bases healthy.

A scheduled prune job suggests maintenance actions without deleting data by operating non-destructively, proposing guided actions for review rather than executing them. It validates all inputs and respects draft statuses to ensure historical integrity of logs and insights.

The weekly prune process supports draft statuses and validates inputs before recommending actions. It respects draft statuses to avoid premature archiving and validates all input data to ensure maintenance recommendations are accurate and safe for each walnut's logs and insights.

You need to run a prune job for walnut logs and insights when maintenance is required to keep entries current and readable. The weekly schedule detects oversized logs, unreferenced insights, and stale bundles, surfacing them as actionable candidates for synthesis or archiving.