Aggressive Needs Follow-up Triage — 2026-05-28
Triggered by Sam's selection of daily-pulse Q1A, with explicit guidance to be aggressive and sort newest-first per cluster (older items in SEO and Web Design are almost always superseded).
Result headline
| Metric |
Before |
After |
Delta |
| Live Needs Follow-up count |
549 |
214 |
-335 (-61%) |
What happened
- Daily pulse identified 549 items in Needs Follow-up.
- Standard
needs-followup-triage --apply ran first: 14 archived (2 superseded series, 12 stale routine logs).
- Custom
aggressive_consolidate.py --apply --skip-get ran across 11 batches: 320 more flipped Status -> Complete.
- Total Status flips this session: 334. All reversible. Final live count: 214.
Rules applied (overrides to the standard skill)
- Newest-first per cluster (replacing oldest-first sort).
- Keep N per (Category, Subtopic) cluster:
- SEO: 1, Web Design: 1, Operations: 2, Admin/General: 2, Litify: 3, Google Ads: 2, Marketing: 3, Branding/Hiring: all.
- Series collapse: any series_key with 3+ members keeps only newest survivor.
- Recency window dropped (was 14 days). Series collapse covers recurring runs.
- Protected tags:
critical, improvement-mandate (still always keep).
- Live-work protection:
looks-pending signal still protects Litify, Google Ads, Marketing. Dropped for SEO, Web Design, Operations, Admin/General.
Biggest cluster impacts (newest-first)
- Operations / Briefings & Session Logs: 47 -> 6 kept (41 archived)
- Operations / Repo & Git Health: 27 -> 3 kept (24 archived)
- Operations / File Cleanup & Dedup: 27 -> 4 kept (23 archived)