<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[wudwerd]]></title><description><![CDATA[wudwerd]]></description><link>https://inteldesk.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 20:23:43 GMT</lastBuildDate><atom:link href="https://inteldesk.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How a free desk called a 12% Brent move 88 seconds before the wires]]></title><description><![CDATA[On 23 March 2026, Brent crude fell about 12% in ninety minutes. The trigger was a single line: Trump had instructed his team to postpone military strikes…]]></description><link>https://inteldesk.hashnode.dev/how-a-free-desk-called-a-12-brent-move-88-seconds-before-the-wires</link><guid isPermaLink="true">https://inteldesk.hashnode.dev/how-a-free-desk-called-a-12-brent-move-88-seconds-before-the-wires</guid><category><![CDATA[trading, ]]></category><category><![CDATA[finance]]></category><category><![CDATA[OSINT]]></category><dc:creator><![CDATA[wudwerd]]></dc:creator><pubDate>Fri, 10 Jul 2026 11:39:37 GMT</pubDate><content:encoded><![CDATA[<p>On 23 March 2026, Brent crude fell about 12% in ninety minutes. The trigger was a single line: Trump had instructed his team to postpone military strikes on Iran. If you were long the oil risk premium, those ninety minutes mattered a great deal.</p>
<p>Here is the part worth studying. The first credible source carried that line at 11:05:32 GMT. Mainstream coverage arrived at 11:07:00. That gap, 88 seconds, is a long time when a chokepoint premium is unwinding in front of you.</p>
<p>I know the exact numbers because a desk I built logged the whole thing, second by second, while it happened. This is the story of what it recorded, and why the method behind it matters more than the speed.</p>
<h2>The chain, with timestamps</h2>
<p>The desk does not treat a headline as true because it is loud. It logs the source, the reliability tier, and the exact second, then waits for corroboration before it calls anything confirmed.</p>
<p>On 23 March the chain looked like this, all times GMT:</p>
<ul>
<li><p>11:05:32. FinancialJuice, first: strikes postponed.</p>
</li>
<li><p>11:05:55. A second source corroborates. Talks described as "very good and productive." Two-source threshold met. The desk fires a critical alert.</p>
</li>
<li><p>11:06:12. Critical alert logged, with direct exposure flagged: LNG, Shell, Brent.</p>
</li>
<li><p>11:07:00. ForexLive publishes.</p>
</li>
<li><p>11:07:28. Reuters.</p>
</li>
<li><p>11:09. BBC.</p>
</li>
<li><p>11:55. Tasnim, Iran, contradicts: "There have been no talks. Psychological warfare."</p>
</li>
</ul>
<p>Two things stand out. The desk had a corroborated, actionable read 88 seconds before the first mainstream article. And the Iranian denial fifty minutes later did not reverse the price move, but it mattered to anyone still holding the thesis. The desk kept that contradiction on screen rather than smoothing it away.</p>
<h2>Proof over vibes</h2>
<p>Most market-news tools optimise for one thing: speed. Speed without provenance is how desks get burned on a spoofed headline.</p>
<p>The desk I built, Intel Desk, is built the other way round. Every source is tiered A to D on a NATO Admiralty-style reliability scale. A single Telegram post never becomes "confirmed" on its own. When two sources disagree, the disagreement stays visible as a contested state instead of being resolved prematurely. Market impact sits beside the claim as evidence, not as a recommendation.</p>
<p>The result is slower to say "confirmed" and much harder to mislead. And because there is a public replay archive and a scorecard, the track record is auditable rather than asserted. You do not have to trust it. You can check it.</p>
<h2>Why it is free</h2>
<p>The honest answer is the best part. It is free because it is a one-person project in early access, and because the proof is public. A free tool asking for your attention should be checkable, not just cheap. The scorecard grades the desk in the open. The replay archive shows what hit first, what confirmed, and what faded.</p>
<p>Under the hood it runs 199 named sources on a 120-second cycle, real-time AIS vessel tracking through the Strait of Hormuz with a computed corridor-pressure index, and market data cross-validated across providers. There is a web desk and an iOS app.</p>
<h2>See for yourself</h2>
<p>The full 23 March case file, with every timestamp, is here: <a href="https://www.inteldesk.app/case-file/trump-iran-brent-2026-03-23">https://www.inteldesk.app/case-file/trump-iran-brent-2026-03-23</a></p>
<p>The live desk is here: <a href="https://www.inteldesk.app/dashboard">https://www.inteldesk.app/dashboard</a></p>
<p>Intel Desk is an intelligence aggregation tool. It surfaces publicly available information and scores it. It is not financial advice, and it is not a trade recommendation. Always do your own research.</p>
]]></content:encoded></item><item><title><![CDATA[Building a geopolitical signal desk: AIS corridor pressure, multi-source price cross-validation, and corroboration logic]]></title><description><![CDATA[I am an energy and macro trader, and I built a real-time geopolitical decision desk because I was tracking Iran, Hormuz shipping and OPEC-adjacent moves…]]></description><link>https://inteldesk.hashnode.dev/building-a-geopolitical-signal-desk-ais-corridor-pressure-multi-source-price-cross-validation-and-corroboration-logic</link><guid isPermaLink="true">https://inteldesk.hashnode.dev/building-a-geopolitical-signal-desk-ais-corridor-pressure-multi-source-price-cross-validation-and-corroboration-logic</guid><category><![CDATA[OSINT]]></category><category><![CDATA[trading, ]]></category><category><![CDATA[websockets]]></category><category><![CDATA[datascience]]></category><dc:creator><![CDATA[wudwerd]]></dc:creator><pubDate>Fri, 10 Jul 2026 10:46:26 GMT</pubDate><content:encoded><![CDATA[<p>I am an energy and macro trader, and I built a real-time geopolitical decision desk because I was tracking Iran, Hormuz shipping and OPEC-adjacent moves out of a dozen browser tabs with no reliable way to judge source quality under time pressure. This is a write-up of the parts other builders might find useful. Feedback on the weak points is welcome, that is mostly why I am posting.</p>
<h2>Source tiering and the two-source threshold</h2>
<p>The desk ingests 199 named feeds. Each is tiered A to D on a NATO Admiralty-style reliability scale. Tier A is wire agencies and official government sources. Tier D is monitored but low reliability, labelled and never allowed to drive an alert on its own.</p>
<p>The core rule: a claim needs a second independent source, or a corroborating market signal, before it flips from "developing" to "confirmed." A single Telegram post stays labelled. This one rule removes most of the false-positive noise that catches speed-only feeds.</p>
<h2>Contradictions as first-class state</h2>
<p>When two sources conflict, the desk does not pick a winner and hide the loser. It holds a contested state with both receipts visible until a third source or the tape breaks the tie. In practice this is what stops a clean-looking summary from quietly deleting the most important information in a fast-moving story.</p>
<h2>AIS corridor-pressure index</h2>
<p>Vessel tracking runs on a real-time AISStream WebSocket feed. On top of raw positions the desk does three things:</p>
<ul>
<li><p>Transit-direction inference through the Strait of Hormuz.</p>
</li>
<li><p>Floating-storage detection.</p>
</li>
<li><p>OFAC SDN screening against the US Treasury sanctions list.</p>
</li>
</ul>
<p>The output is not a map widget. It is a computed corridor-pressure index, derived from transit volume, AIS signal gaps (vessels going dark), and news-cluster intensity in the same window. The interesting failure mode, and the one I would most like critique on, is spoofed or manipulated AIS. Suggestions on robust anomaly detection there are very welcome.</p>
<h2>Market data cross-validation</h2>
<p>Price data flows through a fallback chain: Yahoo Finance v7 quotes, then v8 spark as a fallback, then the chart API, with a Twelve Data cross-check. If two providers disagree by more than 5%, the desk flags it and takes the consensus rather than trusting a single feed. Commodities are validated this way: Brent, WTI, gold, natural gas, heating oil, silver, plus a customisable equity and FX watchlist.</p>
<h2>Signal correlation, not just aggregation</h2>
<p>Feed items are cross-referenced against the market tape. The desk tracks narrative velocity (how fast a story propagates across independent sources), detects when multiple independent sources report the same event, and attaches the market move that occurred in the same window. Aggregation tells you what was said. Correlation tells you whether it mattered.</p>
<h2>Known limitations, up front</h2>
<ul>
<li><p>Market data is a 10-second poll, not tick-by-tick. This is context for event trading, not a Bloomberg tick feed replacement.</p>
</li>
<li><p>Sentiment is keyword and source-weight derived, not a transformer model. It works on high-signal geopolitical events and will miss nuance in ambiguous diplomatic language.</p>
</li>
<li><p>ACLED conflict data depends on upstream availability. When it lags, the map falls back to GDELT and FIRMS hotspot data.</p>
</li>
<li><p>It is a one-person project. Sources go stale, upstreams change, things break. There is a public status page.</p>
</li>
</ul>
<h2>Why I am telling you this</h2>
<p>Because the whole design principle is auditability. There is a public replay archive and a scorecard, so the track record can be checked rather than asserted. On 23 March the desk flagged the Iran-strikes reversal 88 seconds before mainstream coverage, and Brent moved 12% in the next ninety minutes. The full timestamp chain is public.</p>
<p>It is free, web and iOS. Not financial advice, it is an intelligence tool. Try to break the corroboration logic and tell me where it fails: <a href="https://www.inteldesk.app">https://www.inteldesk.app</a></p>
]]></content:encoded></item></channel></rss>