watchlist-tracker

Automate watchlist monitoring by configuring a defined cadence in local.md and setting up YAML-based topic configurations. The system evaluates triggers, scores materiality, and delivers digest-ready summaries via email and the Cowork UI.

Yes, watchlist monitoring supports per-item triggers and materiality scoring across signals like news, regulatory activity, new entrants, funding, and earnings. YAML-based topic configuration persists these settings in local.md for easy rehydration.

Cadence-driven monitoring requires defining your schedule in local.md and configuring topics via YAML. The system then evaluates signals across news, regulatory activity, new entrants, funding, and earnings, delivering digests with actionable insights.

Yes, a defined cadence stored in local.md is required before generating digests. You must configure your cadence and topics, then prompt the system to generate the next digest for email or Cowork UI delivery.

YAML-based topic configuration persists monitoring settings in local.md, enabling easy rehydration of watchlist data. This approach stores cadence, triggers, and materiality scoring rules for consistent digest generation across sessions.

Scheduled watchlist monitoring requires a predefined cadence in local.md and YAML topic configuration. It relies on Cowork for delivery via email and UI, so digest generation depends on that environment's availability and configuration.