> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/algorithm-watch.md).

# Algorithm Watch

Algorithm Watch monitors known and observed platform signals across X, Instagram, and Facebook. When platforms shift what they reward, your strategy needs to shift with them; Algorithm Watch shortens the gap without turning any one signal into a mandate.

Open it from **Intelligence > Content Optimization > Algorithm Watch**.

### Tabs

Algorithm Watch has four tabs:

* **Signals** - source list, review reminders, and the status of algorithm context flowing into Content Forge.
* **Active Rules** - machine-derived algorithm rules with a status pill on each, refreshed on demand.
* **Org Updates** - logged platform changes with summaries, actionable notes, suggested tests, confidence, and source URLs.
* **Current Events** - read-only RSS items that provide current-event context to ForgeSays.

### Signals

Signal sources can be global or org-specific. Org-specific sources can be added for web pages, RSS feeds, GitHub repos, or APIs, then assigned to X, Instagram, Facebook, TikTok, LinkedIn, or all platforms.

Sources are reviewed manually on a two-week cadence. Mark a source as reviewed after you check it. Sources and logged updates are used as advisory context in Content Forge, but Brand Voice, factual accuracy, and your org identity take priority.

### Active Rules

Active Rules are algorithm rules derived automatically from your signal sources, so you get a distilled view of what platforms currently seem to reward without reading every source by hand. Each rule carries a status pill:

* **Active** - the rule still looks in force.
* **Weakened** - the signal behind it is fading and the rule may be losing effect.
* **Deprecated** - the rule no longer appears to hold and can be retired.

Use **Run scan** to refresh the rules from your latest sources. A scan re-reads the current signals and updates each rule's status. Treat rules as advisory input, not a mandate; Brand Voice and accuracy still take priority.

### Org Updates

Use Org Updates to record meaningful distribution changes you want the team to remember. Each update can include:

* Platform and surface
* Summary of the change
* Actionable note
* Suggested test
* Confidence level
* Source URL

Updates help connect observed platform changes to content decisions and [Experiments](/thecontentforge-docs/feature-guides/experiments.md).

### Current Events

The Current Events tab is a read-only view of the rolling RSS store. It lets you browse items that are available as grounding context for ForgeSays, filter by source or time range, and copy a current-events context packet when useful.

Items appear there as matching news is brought in for ForgeSays.

### Workflow

1. Check **Signals** weekly, or when something feels off in reach
2. Review due sources and mark them reviewed when checked
3. Open **Active Rules** and use **Run scan** to refresh the derived rules
4. Add an **Org Update** when you spot a meaningful platform change
5. Cross-reference [Patterns](/thecontentforge-docs/feature-guides/patterns.md) to see whether your own performance shifted
6. Test the response with an [Experiment](/thecontentforge-docs/feature-guides/experiments.md) so you have evidence, not assumption

### Tips

* Algorithm changes are noisy. Do not overhaul your strategy on a single signal
* Treat algorithm context as advisory input, not an instruction to override Brand Voice or accuracy
* Cross-reference Algorithm Watch with Patterns; your own data is the final word on whether a change is hitting you


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/algorithm-watch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.