> 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-embedded-news-layer.md).

# The Embedded News Layer

The solution. One API call renders news and judgment inside the screen where trading happens.

### 4.1 One Call, One Layer

FLASH solves this with an embedded news layer. Inside the very screen where trading happens, one API call renders the news and the judgment together. Users never leave the screen, and partners never build a newsroom.

What the layer carries is intelligence. Every event arrives as a single card with the judgment complete.

<figure><img src="https://747652094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXF7WB8PYgl8c5gX0ps3D%2Fuploads%2Fwv9hgR9MbwFoJwnweHKm%2FV4-5_live-wall-product.png?alt=media&#x26;token=843f5222-5700-4645-b23e-6f62d83a84e3" alt="The layer rendered in a live screen"><figcaption></figcaption></figure>

### 4.2 One Card, Every Judgment

Every event arrives as one card. A card has three parts.

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><h4><i class="fa-newspaper" style="color:$primary;">:newspaper:</i></h4></td><td><strong>Content</strong><br>What happened</td><td><code>headline</code> <code>summary</code> <code>body</code></td></tr><tr><td><h4><i class="fa-brain" style="color:$primary;">:brain:</i></h4></td><td><strong>Intelligence</strong><br>What the event is and how much it matters</td><td><code>impact</code> <code>impactScore</code> <code>eventType</code> <code>whyItMatters</code> <code>entitySentiment</code></td></tr><tr><td><h4><i class="fa-link" style="color:$primary;">:link:</i></h4></td><td><strong>Source and joins</strong><br>Where it came from and what it connects to</td><td><code>source</code> <code>sourceUrl</code> <code>sourceHeadline</code> <code>sourceImageUrl</code> <code>entities</code> <code>categories</code> <code>cluster</code> <code>cover</code></td></tr></tbody></table>

The content is a rewrite synthesized from multiple outlets' reporting, and every card carries a link to an original article.

### 4.3 impact

`impact` answers how much this event matters. On screen it renders as dots, and the number of dots is the value.

<figure><img src="https://747652094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXF7WB8PYgl8c5gX0ps3D%2Fuploads%2F5AGDEr8jO5jW4veV8UzV%2FV4-1_impact-scale-gate.png?alt=media&#x26;token=447d500a-70ea-4a23-b909-7d288d1a919a" alt="The impact scale and the publishing gate"><figcaption></figcaption></figure>

Within one impact tier, `impactScore` (0 to 100) sets the order.

{% hint style="info" %}
`impact` 1 does not exist in the feed. Sponsored content, press releases, and out-of-domain noise are filtered at publication.
{% endhint %}

### 4.4 Entity sentiment

Sentiment is attached to each entity, not to the card. One event can help one party and hurt another, and a single card-level label cannot carry that. Every entity therefore carries `entitySentiment`: `Positive`, `Neutral`, `Negative`, or `null`.

`Neutral` is a judgment that the event was weighed and found not to move that entity. `null` means there is nothing to weigh: a place, a policy instrument, an indicator.

{% hint style="warning" %}
Values are produced across all categories, including politics and geopolitics. There, sentiment describes standing and not merit: whether a named party gained or lost ground in the event as reported. It is a description of a reported event, not a prediction of price or outcome.
{% endhint %}

### 4.5 eventType

`eventType` answers what kind of event this is, in a fixed classification of 18 types.

| Family                  | eventType                                        |
| ----------------------- | ------------------------------------------------ |
| Policy, regulation, law | policy-decision, regulation-action, legal-action |
| Elections, appointments | election, appointment                            |
| Data                    | data-release, data-point                         |
| Corporate, funding      | corporate-action, funding-deal                   |
| Security                | security-incident                                |
| Disaster                | disaster                                         |
| Geopolitics, diplomacy  | geopolitical-event, diplomatic-event             |
| Statements, commentary  | official-statement, analysis-commentary          |
| Market, operations      | market-move, ops-notice, digest                  |

The classification has a hierarchy. What an authority did outweighs what an authority said, and coverage of an event outweighs commentary about it. Full definitions of the 18 types are in the Appendix.

### 4.6 entities

`entities` answers who is involved in this event. Each subject is recorded in three layers: full name, aliases, and ticker. Federal Reserve and Fed, Bitcoin and BTC are the same subject in different spellings, and the card knows all three.

<figure><img src="https://747652094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXF7WB8PYgl8c5gX0ps3D%2Fuploads%2FV7eo2Pf3J3EsBd7zY8Cp%2FV4-3_entities-join.png?alt=media&#x26;token=d7746e17-6f4a-4170-bd16-73b36be18816" alt="entities as the join key"><figcaption></figcaption></figure>

These three layers are FLASH's join key. Prediction market contracts, exchange asset pages, and cover images connect instantly on top of entities. Each entity also carries its own sentiment (4.4); the join runs on the three layers only.

### 4.7 whyItMatters

`whyItMatters` answers why this event matters today, in two or three sentences: what the event changes for something the reader holds, pays, or watches, the mechanism that carries it there, and the next checkpoint that will show whether the effect holds. It is generated only for cards at impact 4 and above.

It is the only field that carries narrative reasoning, and it is delivered as a separate field. Partners choose whether to take it.

### 4.8 Cluster

The same event is reported many times by many outlets. FLASH converges them into one event and delivers one representative card with a related-coverage count.

<figure><img src="https://747652094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXF7WB8PYgl8c5gX0ps3D%2Fuploads%2F61qC4rX6X9yfAwO87e20%2FV4-4_cluster-merge.png?alt=media&#x26;token=bbf689c4-54f4-4737-ac2a-9f15af936ac2" alt="Many reports converge into one card"><figcaption></figcaption></figure>

Duplication disappears, and the breadth of coverage remains as evidence of trust.

### 4.9 Sixteen Languages, One Judgment

Content fields are delivered in 16 languages simultaneously. Judgment values are identical across languages: impact 4 is 4 on a Korean screen and on a Japanese screen alike.

Every translation is a rendition of FLASH's own text, never of the source article.