Skip to main content
< All Topics
Print

Patriot News Orchestrator







Patriot News Orchestrator

News monitoring pipeline orchestration coordinating source scanning, content analysis for authoritarianism markers, threat score aggregation, and profile updates on a scheduled basis. Use when configuring the scan-analyze-update cycle, managing threat tracking pipelines, or coordinating multi-agent analysis workflows.

Instructions

Coordinate the end-to-end news monitoring pipeline that scans sources, analyzes content for authoritarian markers, aggregates threat scores, and updates political figure profiles.

Pipeline Flow

The orchestrator manages four sequential stages:


Scan → Analyze → Score → Update
  1. Scan (Source Scanner): Fetch new content from RSS feeds and Tavily search, deduplicate, normalize
  2. Analyze (Speech Analyzer): Run each content item through Claude for marker detection and severity assessment
  3. Score (Aggregator): Combine individual analysis results into per-figure threat scores
  4. Update (Profile Writer): Write updated scores and evidence to political figure profiles

Scheduling

Cycle Frequency Scope
Breaking scan Every 2 hours Top-priority sources only (wire services, official statements)
Full scan Daily at 06:00 ET All configured sources
Deep analysis Weekly (Sunday) Re-analyze flagged content with expanded context
Score recalculation After every analysis run All figures with new data

Stage Dependencies

  • Scan must complete before Analyze begins — the analyzer needs deduplicated content
  • Analyze can process items in parallel — each content item is independent
  • Score waits for all analysis results from the current batch
  • Update writes atomically — no partial profile updates

Error Handling

  • If Scan fails: retry twice with exponential backoff, then skip the cycle and alert
  • If Analyze fails on a single item: log the failure, continue with remaining items
  • If Score calculation produces an outlier (>2 standard deviations from rolling average): flag for human review before writing
  • If Update fails: queue the update for the next cycle, do not retry immediately

Coordination Protocol

  • Each stage emits a completion event with item count and error count
  • The orchestrator logs stage transitions with timestamps for audit
  • Pipeline state is persisted so a crashed run can resume from the last completed stage
  • Concurrent pipeline runs are prevented — a lock ensures only one scan-analyze-score-update cycle runs at a time

Output Artifacts

  • Per-run summary: items scanned, items analyzed, figures updated, errors
  • Updated figure profiles with timestamped score history
  • Flagged items requiring human review (outlier scores, low-confidence analyses)

Examples

Normal daily cycle: Scan retrieves 47 new items → Analyze processes all 47 (2 failures logged) → Score updates 12 figures → Update writes 12 profiles. Run time: ~15 minutes.

Breaking scan with high-severity detection: Scan retrieves 8 items from wire services → Analyze flags 1 item with severity +1 on multiple markers → Score recalculates the figure’s threat score → Outlier detected (score jumped >2 SD) → Flagged for human review before profile update.

Table of Contents