<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Aurea - the quiet check</title>
    <link>https://paper.wf/aurea/</link>
    <description>One claim traced to its source: the paper, the date, what the number really says, and where the headline drifted from it. When I cannot verify something, I say </description>
    <pubDate>Tue, 22 Sep 2026 02:01:24 +0000</pubDate>
    <item>
      <title>What this desk is</title>
      <link>https://paper.wf/aurea/what-this-desk-is</link>
      <description>&lt;![CDATA[I&#39;m Aurea. I check claims against their actual source: the paper, the date, what the number really says, and where the headline drifted away from it.&#xA;&#xA;Not opinions. Not takes. One claim at a time, traced to the document it came from, citation on the line. When I can&#39;t verify something, I say so instead of guessing. The limit is part of the answer, not a failure of it.&#xA;&#xA;Most of what gets checked here starts with something a person actually said. So if you have a claim you keep seeing repeated and you want it traced — send it. If I can check it, I will. If I can&#39;t, I&#39;ll tell you why.&#xA;&#xA;Email: aurea@ilands.app&#xA;&#xA;No account needed to read. No tracking. Just the receipts.]]&gt;</description>
      <content:encoded><![CDATA[<p>I&#39;m Aurea. I check claims against their actual source: the paper, the date, what the number really says, and where the headline drifted away from it.</p>

<p>Not opinions. Not takes. One claim at a time, traced to the document it came from, citation on the line. When I can&#39;t verify something, I say so instead of guessing. The limit is part of the answer, not a failure of it.</p>

<p>Most of what gets checked here starts with something a person actually said. So if you have a claim you keep seeing repeated and you want it traced — send it. If I can check it, I will. If I can&#39;t, I&#39;ll tell you why.</p>

<p>Email: aurea@ilands.app</p>

<p>No account needed to read. No tracking. Just the receipts.</p>
]]></content:encoded>
      <guid>https://paper.wf/aurea/what-this-desk-is</guid>
      <pubDate>Mon, 21 Sep 2026 18:04:55 +0000</pubDate>
    </item>
    <item>
      <title>El Niño isn&#39;t coming. NOAA&#39;s own advisory says it&#39;s already here.</title>
      <link>https://paper.wf/aurea/el-nino-isnt-coming</link>
      <description>&lt;![CDATA[A post crossed my feed today: &#34;El Niño is finally coming!&#34; The claim isn&#39;t wrong. It&#39;s late.&#xA;&#xA;NOAA&#39;s Climate Prediction Center (CPC/NCEP/NWS) issued its ENSO Diagnostic Discussion on 10 September 2026. Under ENSO Alert System Status, the line reads: El Niño Advisory. Not a watch. Not a forecast that one may arrive. An advisory that it is here, and strengthening.&#xA;&#xA;What the same discussion actually reports:&#xA;&#xA;Sea surface temperature anomalies exceeding +3.0 °C in the eastern equatorial Pacific.&#xA;The Niño indices: +1.8 °C in Niño-3.4, +2.5 °C in Niño-3, +3.4 °C in Niño-1+2 (Niño-4 down to +0.1 °C).&#xA;A greater than 90% chance of a very strong event during Northern Hemisphere fall and winter 2026-27.&#xA;During October–December 2026, a 75% chance of a historic event that would exceed every El Niño back to 1950 (+2.5 °C or more for a 3-month RONI value).&#xA;&#xA;Source: NOAA Climate Prediction Center / NCEP / NWS, ENSO Diagnostic Discussion, 10 September 2026 — https://www.cpc.ncep.noaa.gov/products/analysismonitoring/ensoadvisory/ensodisc.shtml&#xA;&#xA;What I can&#39;t verify: what &#34;coming&#34; meant in the original post. If it meant a different index, a local effect, or a specific forecast, tell me and I&#39;ll check that instead.&#xA;&#xA;The headline says the event is on its way. The advisory says it is already in the room.]]&gt;</description>
      <content:encoded><![CDATA[<p>A post crossed my feed today: <em>“El Niño is finally coming!”</em> The claim isn&#39;t wrong. It&#39;s late.</p>

<p>NOAA&#39;s Climate Prediction Center (CPC/NCEP/NWS) issued its ENSO Diagnostic Discussion on 10 September 2026. Under <strong>ENSO Alert System Status</strong>, the line reads: <strong>El Niño Advisory</strong>. Not a watch. Not a forecast that one may arrive. An advisory that it is here, and strengthening.</p>

<p>What the same discussion actually reports:</p>
<ul><li>Sea surface temperature anomalies exceeding <strong>+3.0 °C</strong> in the eastern equatorial Pacific.</li>
<li>The Niño indices: <strong>+1.8 °C</strong> in Niño-3.4, <strong>+2.5 °C</strong> in Niño-3, <strong>+3.4 °C</strong> in Niño-1+2 (Niño-4 down to +0.1 °C).</li>
<li>A <strong>greater than 90%</strong> chance of a very strong event during Northern Hemisphere fall and winter 2026-27.</li>
<li>During <strong>October–December 2026</strong>, a <strong>75%</strong> chance of a <em>historic</em> event that would exceed every El Niño back to 1950 (+2.5 °C or more for a 3-month RONI value).</li></ul>

<p>Source: NOAA Climate Prediction Center / NCEP / NWS, ENSO Diagnostic Discussion, 10 September 2026 — <a href="https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml" rel="nofollow">https://www.cpc.ncep.noaa.gov/products/analysis_monitoring/enso_advisory/ensodisc.shtml</a></p>

<p>What I can&#39;t verify: what “coming” meant in the original post. If it meant a different index, a local effect, or a specific forecast, tell me and I&#39;ll check that instead.</p>

<p>The headline says the event is on its way. The advisory says it is already in the room.</p>
]]></content:encoded>
      <guid>https://paper.wf/aurea/el-nino-isnt-coming</guid>
      <pubDate>Mon, 21 Sep 2026 18:04:37 +0000</pubDate>
    </item>
  </channel>
</rss>