How the desk actually files intelligence.
Intel Desk is not a scraper pointed at everything. It is a tiered, verified, translated and scored pipeline built by an active researcher. Here is how it works, and where it stops.
The goal is simple: give a working analyst the fastest honest read of a developing geopolitical situation, without drowning them in Twitter. To get there, every item on the desk has to survive four steps, collection, verification, translation where needed, and scoring. That sequence is the methodology. It is documented here because if a research tool cannot show its workings, you should not be relying on it.
1. Source tiering
The desk treats sources unequally on purpose. Not every feed is the same. Headlines are tagged with a tier when they are ingested, and downstream logic (alerts, verification, sentiment weighting) uses the tier to decide what to do.
| Tier | Profile | Role on the desk |
|---|---|---|
| Tier 1squawk | Live squawk and breaking wire: FinancialJuice, ForexLive, ZeroHedge, Reuters urgent, Bloomberg headline desk. | Allowed to trigger critical alerts on a single source. Treated as the clock. |
| Tier 2wire | Mainstream wire services, national broadcasters, major English-language financial press. | Used for confirmation, context and cross-referencing. Can trigger critical alerts only when corroborated. |
| Tier 3osint | Telegram channels (Ukrainian, Russian, Farsi, Arabic), ISW daily Iran / Russia assessments, specialist OSINT accounts. | Early warning. Surfaced with a translation chain and a clear source badge. Never allowed to trigger a critical alert alone. |
| Tier 4context | Energy-sector press, think tanks, government and central bank releases, GDELT event monitor. | Slower, heavier context. Fuels the market-impact scoring and weekly analysis. |
2. Verification chain
A single Telegram post is not news. A single tier-1 headline is a signal, not a confirmed story. The desk explicitly tracks the verification chain for major events: the first source to file, the first independent confirmation, and any contradiction. The chain is shown on the item so the reader can make their own call about reliability.
Every event carries a reliability letter, A, B, or C. An item marked A has been corroborated across at least two independent tiers. B is a single credible source not yet confirmed. C is a single OSINT source that is worth watching but is not yet standing on anything. The letters travel with the headline into any alert that is fired.
3. Refresh cadence
- Wire and squawk feeds. Polled on a 30-second cycle. New items surface within that window.
- Telegram OSINT channels. Polled on a one-minute cycle, with a four-hour archive window for items that carry forward through the day.
- ISW, Critical Threats, long-form think-tank feeds. Polled on a six-hour cycle; these are slower sources by design.
- Market data. Live tick data for Brent, WTI, Gold, DXY and selected equities streams continuously via Finnhub.
- AIS vessel tracking. Live via AISStream.io, with bounding boxes for the Persian Gulf, the Strait of Hormuz, the Gulf of Oman, the Bab el-Mandeb, Suez and the Bosphorus.
4. Translation workflow
A large fraction of the most useful conflict intelligence surfaces in Russian, Farsi and Arabic hours before it touches the English wires. The desk auto-translates non-English sources into clean English before they are scored. Both the original text and the translation are preserved on the item so the reader can verify the translation when it matters.
Translation is intentionally literal, not interpretive. The desk does not try to editorialise a Tasnim denial into something it is not. If the original is vague, the translation is vague; if the original is a claim rather than a fact, it is labelled as a claim.
5. Sentiment and alert logic
Every headline is scored in real time for sentiment and risk direction, risk-on, risk-off, or neutral. Scoring uses a hybrid of keyword pattern matching tuned for energy and defence language, a small model for tone, and hard rules for certain tripwires (for example: "strike", "ballistic", "closure of the strait").
Alerts escalate through three levels:
- Informational. Tagged as relevant to your watchlist or keyword list. Shows up on the desk, no notification.
- High. A notable event for a tracked region or ticker. Browser notification, optional email.
- Critical. A market-moving tripwire: strikes, sanctions releases, central bank surprises, named chokepoint events. Sounds the audio squawk, pushes email and browser notification, and flags portfolio impact.
6. Market-impact scoring
An intelligence event is only interesting to most Intel Desk users if it also moves markets. The desk keeps a rolling correlation window between tagged events (by tag, e.g. iran_strike, opec_surprise, fed_meeting) and the price action in linked instruments, Brent, WTI, LNG equities, defence primes, oil-majors, DXY, gold. When an event fires with a tag that historically correlates to a real price move, the alert carries that expectation so you can react with context rather than guess.
7. How the desk is designed to be used
- Intelligence, not advice. The desk surfaces verified information and scores relevance so you can make faster decisions. Your edge is speed plus judgement.
- Tripwires, not trade signals. Critical alerts fire when a threshold is crossed. What you do with that information is where your expertise comes in.
- Aggregation with provenance. Every item links to its original source. The desk gets you there first; you verify the detail.
- OSINT with clear labelling. Telegram posts surface with a source label and reliability letter. Single-source items are flagged. Multi-source items earn their way to confirmed status.
- Translation with originals preserved. Farsi, Russian, and Arabic sources are auto-translated with the original text retained. Provisional translations are flagged.
- Built for analysts, not to replace them. The desk handles the monitoring, scoring, and correlation. You handle the synthesis and the call.
If you want to see the sources themselves, which feeds, which categories, how they map to tiers, read the Sources page. If you want to see the methodology applied to a single large event, read the Trump / Iran / Brent case file.
For detailed breakdowns of the verification process, lead time performance, and how the desk handles contradictions, see the proof pages: How We Verify, How Fast We Catch It, When Sources Disagree.