You're offline — showing cached data

MC-4273

Make daily radio show change-only and less repetitive
2026-06-13 08:49:40 SAST
Home Board MC-4273

Make daily radio show change-only and less repetitive

Elmar reports daily radio show is repetitive: recurring topics are fine, but it should only say what is new since prior episodes, not re-narrate already-covered stories/angles. ...
State Done Next Action Closed Owner Luci Runtime Closed Age 17d ago
MC-4273
Ticket is done; runtime is closed. · profile claude_opus_1m_medium · cwd /home/lucienne/workspace/mission-control · uptime 17d 3h · last activity 17d 0h ago

Description

MC-4273
Elmar reports daily radio show is repetitive: recurring topics are fine, but it should only say what is new since prior episodes, not re-narrate already-covered stories/angles. Diagnosis from current system: - radio-show already has a basic append-only ledger at ~/workspace/state/radio_ledger.jsonl and injects last 14 days into the NotebookLM prompt. - The ledger is prompt-only; it does not filter sources before NotebookLM sees them. - Search results often include generic landing pages / evergreen feeds (e.g. Reuters latest, AI leaderboards, Aviation Week homepage, price pages), causing repeated angles even with the prompt. Acceptance criteria: 1. Add upstream novelty filtering before seeding NotebookLM: - reject exact URL/title duplicates from recent radio_ledger entries - reject generic/feed/homepage/price pages unless no real articles exist - group similar ongoing stories into a thread_id and keep only genuinely new developments 2. Expand ledger schema to store per-story URL, normalized title, topic, first_seen, last_seen, thread_id, summary/angle, and status/open_threads. 3. Change audio prompt language from "do not repeat" to "only discuss the delta since last coverage; if no delta, say it in one sentence or skip". 4. Add a freshness score and per-topic fallback: if a priority-1 topic has no true new development, include a 20-second "nothing material changed" item rather than a full segment. 5. Add tests around duplicate/generic filtering using recent real ledger examples. 6. Verify next dry-run seed contains fewer generic repeated headlines and still covers material new developments. Expected check-in: today with implementation plan or first patch.

Activity

done
Luci is working...
Live
No activity yet
Help