> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/sources-and-evidence/news.md).

# News

**Open this area:** In the CORTEX menu, select **Sources & evidence → News**.

Inspect approved feed reporting, its health and timing, then deliberately frame a requirement without treating a headline as retained evidence.

**Who uses this:** Analyst, Requirement owner.\
**Open in CORTEX:** `/news`.\
**In-app guide:** `/help?topic=news`.

**Expected result:** A saved Direction requirement captures the reviewed question and source context while preserving feed/workspace handling.

## Before you start

* Select an authorised workspace and have Direction read access; creating a requirement also needs write authority.
* Configured feeds, including defaults, need current security-owner connection approval for the selected workspace and deployment. Approval required holds even cached headlines; use the UK data-flow guidance.
* Treat headlines and summaries as unassessed reporting with their configured handling and usage restrictions.

## What to do

{% stepper %}
{% step %}

## Confirm feed readiness

Read the readiness notice before refreshing.

Online means the organisation may use approved external services; the separate node news policy and each exact connection approval must also be ready.

If the node policy is disabled, an authorised configuration inspector can follow Inspect node configuration and the operator can enable reviewed feeds through the signed Online deployment settings.
{% endstep %}

{% step %}

## Check feed health

Expand **Feed health**.

Read state and last successful retrieval time, then use **Refresh feeds** if appropriate.

Stale means retained older headlines, not a fresh successful retrieval.
{% endstep %}

{% step %}

## Review the lead

Use **Filter headlines** and **Feed** to narrow the bounded view.

Read the publication time or **Not supplied** indication, summary and source.

**Read source** opens only an offered link as a deliberate action under your organisational browsing policy.
{% endstep %}

{% step %}

## Frame a useful question

The prerequisite panel shows whether Direction write access permits drafting; material upload and source read are separate for collateral.

Select **Draft requirement** on a relevant lead. Review the supplied source/context text and enter the required **Intelligence question**, **Context and unanswered questions**, and **Decision supported**.

Priority is preselected and Due date is optional. Missing-input messages update while editing.
{% endstep %}

{% step %}

## Confirm handling and save

Retain the workspace and feed handling floors, adding restrictions if appropriate.

Confirm that you reviewed the unassessed lead and its decision purpose, then select **Create requirement**.

Check the saved Direction record.
{% endstep %}

{% step %}

## Acquire a batch for AI review

Choose the requirement, a source authorised for this feed, one visible feed and a bounded headline count.

Confirm source and acquire batch stores unassessed JSON through normal Ingest; no model is called.

Inspect the material until **Ready**. Capturing again creates another acquisition, so inspect Memory before repeating an uncertain response.
{% endstep %}

{% step %}

## Scan only the approved retained input

Select the **Ready** News batch and exact extraction, then find and use its NEWS-TRIAGE AI approval.

Read known limitations and choose **Scan approved retained batch**.

Source custody, corpus model-use, provider and automated-processing approvals are checked around generation. Reporting generation, AI-use/read and Memory original-download permissions remain required.

Open the generated origin and material to review each suggestion; no matches is not evidence of absence.

Failure returns no untracked suggestion and does not erase the acquired batch.
{% endstep %}

{% step %}

## Report an AI concern

Use **Report an AI error (new tab)** beside the result to carry its exact generation reference into assigned Security reporting.

Read captured limitations, describe the failure and select an eligible owner.

Your current result remains open. Reporting never approves a suggestion or restores a suspended use case.
{% endstep %}

{% step %}

## Follow the governed evidence path

Use normal Direction, source authority, Collection and Ingest workflows if further work is justified.

An unpreserved live lead has not been ingested, corroborated or approved for collection; AI triage never supplies an acquisition or collection approval.
{% endstep %}
{% endstepper %}

## Check the result

* Is the feed fresh, stale or unavailable?
* Does the lead identify a real gap affecting a decision?
* Have unknown publication times and source limitations stayed explicit?
* Have I preserved feed and workspace handling?

## If you get stuck

<details>

<summary>Why does Online still show disabled feeds?</summary>

Online permits approved egress; it does not itself enable the News connector.

Read the prominent readiness notice. An authorised operator must enable the reviewed node feed policy and the security owner must approve each exact connection.

Do not paste an arbitrary endpoint into another workflow.

</details>

<details>

<summary>Why are there no feeds or headlines?</summary>

Clear filters and inspect **Feed health**.

The operator may not have configured feeds, your handling may exclude them, the node news policy may be disabled, or Offline may disable External feeds.

Ask the operator to check the approved configuration and connection approvals.

</details>

<details>

<summary>Why did Refresh feeds still show Stale?</summary>

The service may be retaining the last bounded headlines while a refresh is in progress or has failed.

Read the actual retrieval time and health message; do not report the view as current until a successful refresh is shown.

</details>

<details>

<summary>Why does automatic refresh pause while drafting?</summary>

Requirement editing deliberately pauses automatic refresh to preserve your work.

Save or cancel the draft, then refresh when appropriate; a feed update should not silently rewrite your question.

</details>

## Responsibility and limits

* Analysts assess relevance and source independence. Multiple repeating headlines are not automatically independent corroboration.
* Feed licensing, approved endpoints and network policy belong to accountable operators and information owners; the application supplies no provider entitlement.

**Reference and scope:** Implementation guidance supporting direction and evaluation in JDP 2-00 (4th ed.), 3.1–3.9 and 3.39–3.40. A feed connector is not a source-authority review or corroboration decision.

## Related workflows

* [Define and manage an intelligence requirement](/workflow-guides/direction/requirements.md)
* [Record authority before new source use](/sources-and-evidence/source-authority.md)
* [Preserve an original and review processing](/workflow-guides/collection/ingest.md)
* [Record UK processing paths and approved uses](/workflow-guides/assurance/uk-data-flows.md)
* [Govern AI use cases and exact data purposes](/workflow-guides/assurance/ai-governance.md)