> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soriaanalytics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# News Intelligence

> An automated pipeline that fetches, scores, clusters, and summarizes healthcare news daily — surfaced as structured events and individually scored articles.

News Intelligence runs a daily pipeline that monitors healthcare news sources, scores each article for relevance to your coverage universe, groups related stories into events, and writes a concise intelligence brief for each event.

You interact with the results through four MCP tools: `news_pipeline`, `news_branches`, `news_events`, and `news_articles`.

## What the pipeline produces

<CardGroup cols={2}>
  <Card title="Events" icon="layer-group" href="/news/pipeline#viewing-events">
    Clusters of related articles grouped around a single real-world occurrence — an earnings release, a regulatory action, an M\&A deal. Each event has a label, a structured summary, and an article count.
  </Card>

  <Card title="Articles" icon="newspaper" href="/news/pipeline#viewing-articles">
    Individual news items with a relevance score (1–10) and a bucket classification. Articles scored above the relevance threshold are bucketed as `relevant`; the rest go to `discard`.
  </Card>
</CardGroup>

## Branches

Every pipeline run operates against a **branch** — a named configuration that controls what gets fetched, how articles are scored, and when the pipeline runs automatically.

<CardGroup cols={2}>
  <Card title="Production branch" icon="shield-check">
    The production branch runs on a schedule automatically. Its results are what you see by default in `news_events` and `news_articles`. You cannot delete it.
  </Card>

  <Card title="Custom branches" icon="git-branch">
    Create your own branch to experiment with different fetch sources (`fetch_config`) or a custom scoring prompt (`extraction_prompt`). Results stay isolated from production until you are satisfied.
  </Card>
</CardGroup>

<Note>
  When you call `news_events` or `news_articles` without specifying a `branch_id`, results come from the production branch.
</Note>

## MCP tools at a glance

| Tool            | What it does                               |
| --------------- | ------------------------------------------ |
| `news_pipeline` | Run the pipeline or check its status       |
| `news_branches` | Create, update, clone, and delete branches |
| `news_events`   | List and filter clustered news events      |
| `news_articles` | List and filter individual scored articles |

## Event types

The pipeline classifies each article into one of the following event types during the extraction step:

| Type                | Description                                |
| ------------------- | ------------------------------------------ |
| `earnings`          | Quarterly results, guidance, analyst days  |
| `m_and_a`           | Mergers, acquisitions, divestitures        |
| `investigation`     | Government or regulatory investigations    |
| `regulatory_action` | CMS rules, FDA decisions, enforcement      |
| `legal`             | Litigation, settlements, judgments         |
| `funding`           | Capital raises, IPOs, debt issuances       |
| `clinical_data`     | Trial results, approvals, safety signals   |
| `partnership`       | Joint ventures, licensing, contracts       |
| `product_launch`    | New products, service expansions           |
| `executive`         | Leadership changes, board appointments     |
| `policy`            | Legislation, policy proposals, ACA updates |

## Next steps

<CardGroup cols={2}>
  <Card title="Running the pipeline" icon="play" href="/news/pipeline#running-the-pipeline">
    Run the full pipeline or individual steps, and check run status.
  </Card>

  <Card title="Managing branches" icon="sliders" href="/news/pipeline#managing-branches">
    Create and configure custom branches with your own fetch sources and scoring prompts.
  </Card>
</CardGroup>