Reactive Content

Reactive content is generated in response to a specific news item, giving your posts timely real-world context. It's generated during the daily workflow, in addition to your regular calendar-slot content.

How reactive content is generated

flowchart TD
    A[Daily workflow runs] --> B[NewsService fetches RSS feeds]
    B --> C[Score each news item for relevance]
    C --> D{Item above threshold?}
    D -- No --> E[Skip item]
    D -- Yes --> F[NewsService derives suggestedAngle]
    F --> G{Under max reactive cap?}
    G -- No --> E
    G -- Yes --> H[Generate reactive post via Claude]
    H --> I[Label as Reactive in queue]
    I --> J[Pending review / auto-approved]

The suggestedAngle

For each qualifying news item, NewsService derives a suggestedAngle: a short framing that guides the generation. It's derived from:

• The article's headline and summary
• Your brand's topic keywords
• The feed's relevance context

The suggestedAngle tells Claude what angle to take when writing about the news item. It's equivalent to the angle field on a regular topic, but generated dynamically from the article content.

Example news item: "OpenAI launches new model with 2x context length"

Example suggestedAngle: "React to context length increase from a practical developer perspective — what use cases this actually unlocks vs. what remains limited."

Controlling reactive posts per run

The Max reactive posts per run setting in Settings → Automation caps how many reactive posts can be generated in a single daily workflow run.

If multiple news items qualify on the same day, Borker picks the highest-scoring ones up to the cap. The rest are skipped (not queued for later).

Identifying reactive content in the approval queue

Reactive posts are labeled with a Reactive badge in the Approval Queue. The item detail shows:

• The source article (title + URL)
• The RSS feed it came from
• The suggestedAngle that was used

This lets you evaluate whether the reactive content is actually timely and relevant before approving it.

Manual review of reactive content

Even in auto-approval mode, reactive content deserves a second look. The suggestedAngle is AI-derived from the article, not hand-crafted by you. It may occasionally produce:

• A take that's technically accurate but not your brand's position
• Content that references a news item that's already outdated
• A response to a competitor that's more aggressive than you'd want

Recommendation: Keep reactive content in manual approval mode even if you use auto-approval for regular content. The suggestedAngle is good, but not as reliable as your hand-crafted topic angles.