Tickers are not chosen at random. Every company or instrument shown by Geopolitics Alpha must have a labeled evidence path from the reporting to the market exposure.
We separate what the article explicitly says from what the system infers. That distinction remains visible on every story card.
Article titles and summaries are checked for legal company names, recognized brand names and explicit ticker formats. Public-company identity is resolved against the SEC-published company/ticker directory, with reviewed aliases for brands whose public name differs from the issuer name.
A company not named in the reporting may appear only when a defined relationship connects it to the event—for example sector exposure, supply-chain dependency, operating geography, commodity sensitivity or infrastructure ownership.
| Why it appears | Evidence required | Universe rule | Displayed label |
|---|---|---|---|
| Direct company mention | A legal name, recognized brand name or explicit ticker appears in the article metadata. | Always included | DIRECT |
| Related company exposure | A documented sector, supply-chain, geographic or operating relationship connects the company to the event. | Approved universe only | INFERRED |
| ETF / benchmark context | A sector fund, index, rate, currency or commodity provides market context for the transmission path. | Approved context set | CONTEXT |
| User watchlist match | An already-supported relationship overlaps a user-saved symbol. | Personalized emphasis | WATCH |
Retrieve public and official headline metadata, preserve source attribution and normalize text for comparison.
Cluster substantially similar reports and avoid treating syndicated copies as independent confirmation.
Match legal names, reviewed brands and explicit tickers. Direct public companies are added before any universe filter.
Apply reviewed event-to-sector and event-to-instrument rules for related exposures, benchmarks and commodities.
Score relevance, freshness, source quality and corroboration, then display direct and inferred relationships separately.
Verification describes the state of the reporting. It is not a forecast and it does not prove that an event caused a market move.
One publisher or upstream source is reporting the event.
An authoritative primary source reports the event.
At least two distinct upstream source lineages describe the same event.
Corroborated reporting and directly related market attention are both present.
The system found a disclosed direct identity match or a defined exposure relationship worth monitoring.
A recommendation, a price-direction forecast, proof of causation, or a claim that the list is complete. Company names, listings and relationships can change; ambiguous matches are withheld for review.