MISSION CONTROL
Block Editor
Notion-style document editing
๐
Runbooksยท2026-06-09
News Pipeline To-Do List
newspipelinegeneral
H
News Pipeline To-Do List
T
The news page currently runs on mock data. To get live news flowing, the following work is needed:
H
1. Database Schema for Briefing Data
T
- mc.briefings โ stores generated briefings (id, date, headline, kicker, lede, takeaway, reading_time_min, created_at)
T
- mc.briefing_stories โ individual stories (id, briefing_id, title, summary, url, severity, sentiment, topic, score, source_id, published_at)
T
- mc.news_sources โ connects to the Sources page (id, name, url, category, status, last_fetch, article_count)
H
2. News Fetcher Cron Job
T
Scheduled daily (or twice daily). Pulls from RSS feeds configured in the Sources page, deduplicates against stored stories, passes new articles through LLM for summaries/severity/sentiment/topic/score, stores results in mc.briefing_stories.
H
3. Briefing Generator Cron Job
T
Takes the day's fetched stories, groups by topic into sections, generates headline / kicker / lede / What the Week Brings, stores finished briefing in mc.briefings.
H
4. Wire /news Page to the DB
T
Replace mock data in page.tsx with fetch from /api/briefing/latest. API route reads from mc.briefings.
H
5. Wire /news/archive Page to the DB
T
Replace mock archive with fetch from /api/briefing/archive. Returns historical briefing summaries by date.
H
6. Make Sources Page Functional
T
Persist add/toggle/delete to mc.news_sources table. Fetcher reads from this table instead of mock data.
D
H
Priority Order
T
1. DB schema (tables + migrations)
T
2. mc.news_sources โ fetcher needs this to know what to pull
T
3. Fetches + LLM enrichment
T
4. Briefing generator
T
5. Wire UI pages to API routes
ยทType / for commands