> For the complete documentation index, see [llms.txt](https://docs.flash.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flash.im/whitepaper/the-problem.md).

# The Problem

### 3.1 The Market Is Here, the News Is Elsewhere

Trading happens in contract screens and trading panels. The news is elsewhere: news sites, social media, search bars.

<figure><img src="/files/e2wLdTossKVr8aeOMH6h" alt="Trading screen and news, apart"><figcaption></figcaption></figure>

With the two on separate screens, users leave the trading screen to find their grounds. By the time they check and return, the price has already moved, and most trade without checking at all. The platform loses traffic, and the user loses timing.

{% hint style="warning" %}
The market and the news must move together on one screen.
{% endhint %}

### 3.2 Judgment Arrives Late

Major institutions and outlets publish thousands of articles a day. Headlines arrive in seconds, but the interpretation of what they mean and how much they matter arrives at human speed.

Markets move in that gap. Judgment must be as fast as the news.

### 3.3 Written for Human Readers

Articles are prose. Fields like importance, direction, and related assets do not exist; they are implied inside sentences.

Humans read and interpret. Agents and systems must parse and guess. Automation cannot be built on guesses.

<figure><img src="/files/wnqslBryHQUbro2YtsnR" alt="Prose article versus structured payload"><figcaption></figcaption></figure>

### 3.4 Every Outlet, a Different Scale

The same event is reported in dozens of duplicate articles, and every outlet weighs it differently. A consistent scale for what counts as today's news exists nowhere.

Reporting and promotion arrive mixed in one feed. To become a feed that mounts directly on a screen, someone has to filter and judge on one consistent standard.

<figure><img src="/files/pglHam9xgZKogFBN8QHC" alt="One event, reported again and again"><figcaption></figcaption></figure>

### 3.5 English First

Global platforms serve dozens of languages, but the news stays in English. Non-English users get less context on the same screen.

Markets are already global. The news layer should be too.

### 3.6 Known Problem, Hard Build

Platforms know all of this. That is why, until now, putting news on a screen meant running a newsroom you never signed up for.

```mermaid
flowchart LR
    A["Collect articles<br/>or take submissions"] --> B[Classify] --> C[Build metadata] --> D["Match to each page<br/>by hand"] --> E[Translate]
```

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><h4><i class="fa-file-contract" style="color:$primary;">:file-contract:</i></h4></td><td><strong>Licensing exposure at every step</strong></td><td>Collecting, storing, and republishing third-party text carries risk from the first stage to the last.</td></tr><tr><td><h4><i class="fa-arrows-rotate" style="color:$primary;">:arrows-rotate:</i></h4></td><td><strong>Maintenance outweighs the build</strong></td><td>Sources change, classification drifts, and matching breaks. The pipeline needs owners forever.</td></tr><tr><td><h4><i class="fa-globe" style="color:$primary;">:globe:</i></h4></td><td><strong>Multilingual multiplies it</strong></td><td>A global product needs translation infrastructure on top of everything above.</td></tr></tbody></table>

### 3.7 The Gap

Integration inside the trading screen, fast judgment, machine-readable structure, one consistent scale, every major language. No news infrastructure has offered all five.

{% hint style="success" %}
Many companies provide news data. FLASH is the only news intelligence layer that mounts instantly, with a single API call, on the screens where markets move.
{% endhint %}