It depends: the base Docker deployment is supported, but Twitter/X is not ready to use out of the box.

• Quick Start documents running the full pipeline with docker compose run --rm horizon [OPTIONS].
• Supported Sources describes Twitter / X ingestion through Apify for user timelines and keyword searches, including reply summaries.
• The README explicitly warns that the twitter extra requires a Playwright browser and system packages, while the current Dockerfile does not install them. Enabling X directly may therefore fail at runtime.
• If your hard requirement is reliable X ingestion inside an unmodified Docker image, Horizon does not meet it. If you can extend the image and manage Apify access, the deployment remains viable.

The README does not provide a complete Dockerfile patch, Apify quota details, or recovery behavior for authentication and scraping failures.

Yes, because the requested sources, bilingual generation, and scheduled GitHub Actions execution are all covered by the README.

• Supported Sources lists RSS / Atom, Hacker News, GitHub, and Google News. Hacker News also supports fetching top comments.
• Features and Project Status state that Horizon generates English and Chinese briefings and can output Markdown.
• The Automate section provides a daily workflow template, but the template is disabled in the repository and must be renamed to daily-summary.yml before it runs.
• Reports are saved under data/summaries/ by default, which fits a CI or GitHub Pages publishing flow.

The README does not specify the actual GitHub Actions cost, retry behavior, or the default model configuration for Chinese generation.

Yes. The README provides an Agent Skill for Node.js 22.20+ users and explicitly supports having an AI assistant configure sources, customize profiles, and run Horizon.

• The Agent Skill section provides the installation command and requires Node.js 22.20+; afterward, the assistant can install and configure Horizon.
• How It Works says the full pipeline can run through the CLI, while an AI assistant can call individual stages through MCP.
• Project Status lists MCP integration and the setup wizard as supported, reducing the need to edit every configuration file manually.
• Agent Skill and MCP serve different roles: the Skill assists with installation and configuration, while MCP lets a client invoke pipeline stages. Model, source, and delivery settings still need to be configured.

The README does not identify supported AI-assistant clients, MCP permission boundaries, secret-injection methods, or whether generated profiles are automatically validated.

Yes. Horizon’s profile routing, per-profile thresholds, and profile-scoped deduplication fit a split workflow for financial and technology coverage.

• Features allow profiles to define scoring rubrics, individual thresholds, and duplicate-story merging within each profile.
• How It Works states that each item routes to one profile and that analysis, filtering, and deduplication happen before enrichment. This allows separate treatment for financial and technology content.
• Supported Sources lists OpenBB for financial company news by watchlist/provider, while RSS / Atom can supply technology feeds.
• OpenBB is optional. Quick Start requires uv sync --extra openbb; if the machine lacks compatible wheels, the README provides a binaries-only installation command.

The README does not specify supported OpenBB providers, the watchlist configuration format, financial-news coverage, or whether cross-source duplicates are always merged correctly.

Yes. The README explicitly treats webhook delivery and the GitHub Pages Daily Site as separate output channels, while also supporting English and Chinese briefings.

• Where Your Briefing Goes states that webhooks can push success or failure results to Feishu/Lark, DingTalk, Slack, Discord, or a custom endpoint.
• The same section says the GitHub Pages Daily Site copies generated Markdown into docs/ for a daily-updated Pages site.
• Features and Project Status confirm English and Chinese briefing generation, so separate language-specific pipelines are not required.
• The webhook description refers to result notifications, not necessarily rendering the full report inside the chat platform; Markdown or Pages can carry the report itself.

The README does not document the exact multi-channel configuration structure, notification payload schema, webhook signing, or repository permissions required for Pages deployment.

Yes. Horizon puts content-specific scoring, processing prompts, and category quotas into profiles and briefing generation.

• Why Horizon? explicitly contrasts “why it matters” for news with “what I can use” for engineering deep dives, showing that different reading goals are supported.
• Features support profiles, scoring rubrics, individual thresholds, and treatments such as summaries, context, solutions, and takeaways.
• The same Features section supports limiting total briefing length and each category’s share, preventing one popular topic from consuming the entire briefing.
• GitHub is a supported source that fetches user events and repository releases.

This is suitable for filtering and reading assistance, but the README does not explain the exact ranking algorithm when category quotas conflict, nor does it guarantee that generated “solutions” are safe to apply directly in engineering decisions.