external-intel-provider-rollout

To safely replace mock intel providers with live external APIs, swap mock adapters with real data sources while preserving the existing scheduler, status tracking, and test harness. Enforce data mapping to internal shapes and maintain timeouts and retries for validated rollout.

Provider status tracking works by recording job and provider states through the set_provider_status function. This mechanism maintains consistent status reporting across news_briefing, eod_summary, and watch_poll paths during live external adapter integration.

The best way to normalize external intel data is to enforce strict mapping to internal shapes like NewsItem, Quote, and EodSummary. This maintains a consistent data contract across news, markets, and settings components during live integration.

Yes, you can use environment variables to drive rollout validation for external API integration. This approach allows you to perform provider interoperability checks and documentation alignment safely before completing the live data source rollout.

External intel adapters break scheduler semantics when the live replacement bypasses existing timeout, retry, and status tracking rules. Preserve these guardrails and map external data to NewsItem, Quote, and EodSummary shapes to prevent scheduler breaks.

Yes, you need to update tests and runbooks when rolling out live intel providers. The process keeps docs aligned and preserves test coverage to validate that real data sources integrate safely with the bot's scheduler and status reporting.