<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jason Wang</title>
    <description>The latest articles on DEV Community by Jason Wang (@jason_waaang).</description>
    <link>https://dev.to/jason_waaang</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3823129%2F276c6c05-ca3b-4c91-8b35-ae0ba3678fd6.png</url>
      <title>DEV Community: Jason Wang</title>
      <link>https://dev.to/jason_waaang</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jason_waaang"/>
    <language>en</language>
    <item>
      <title>I spent 6 months thinking about this problem. Then built the solution in a day.</title>
      <dc:creator>Jason Wang</dc:creator>
      <pubDate>Sat, 14 Mar 2026 00:41:43 +0000</pubDate>
      <link>https://dev.to/jason_waaang/i-spent-6-months-thinking-about-this-problem-then-built-the-solution-in-a-day-3c8l</link>
      <guid>https://dev.to/jason_waaang/i-spent-6-months-thinking-about-this-problem-then-built-the-solution-in-a-day-3c8l</guid>
      <description>&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;We're drowning in information. News, reports, expert opinions, policy documents — all of it arriving faster than we can process.&lt;br&gt;
Every time I asked an LLM to help me reason through something complex, I'd get one of two responses:&lt;/p&gt;

&lt;p&gt;A confident, well-structured answer that was subtly (or not so subtly) wrong&lt;br&gt;
A meandering response that contradicted itself halfway through&lt;/p&gt;

&lt;p&gt;I tried multi-agent debate setups. Same problem, just more expensive.&lt;br&gt;
Then I realized: the core issue isn't information overload. It's that cause-and-effect relationships are invisible.&lt;br&gt;
LLMs are great at pattern matching. They're terrible at causal reasoning — and they don't know it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;After sitting on this idea for six months, I vibe coded CurioCat in a day using Claude Code.&lt;br&gt;
CurioCat is an open-source causal reasoning engine. Drop in any text — policy analysis, investment thesis, competitive intelligence, industry trends — and it maps out the causal structure, sources evidence for every claim, and quantifies how confident you should actually be in each conclusion.&lt;br&gt;
Not a chatbot. Not a summarizer. A reasoning X-ray.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frajxirpctxeg3ozswf45.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frajxirpctxeg3ozswf45.png" alt="Graph Demo" width="800" height="413"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How It Works
&lt;/h2&gt;

&lt;p&gt;The pipeline has six stages:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Atomic Claim Decomposition
Breaks text into the smallest meaningful units and labels each one: fact, assumption, prediction, or opinion.&lt;/li&gt;
&lt;li&gt;Causal Direction Inference
Uses embedding-based filtering + LLM judgment to identify which claims drive which outcomes and map the transmission mechanisms.&lt;/li&gt;
&lt;li&gt;Adversarial Dual-Search
For every causal edge, it searches for both supporting and contradicting evidence simultaneously. No cherry-picking.&lt;/li&gt;
&lt;li&gt;Cognitive Bias Detection
Flags 8 common reasoning failures: correlation-causation confusion, survivorship bias, anchoring effects, narrative fallacy, and more.&lt;/li&gt;
&lt;li&gt;Iterative Evidence Expansion
Mines evidence to surface facts not mentioned in the original text, iterating until the graph converges.&lt;/li&gt;
&lt;li&gt;Noisy-OR Belief Propagation
Propagates confidence scores along the DAG in topological order. Zero evidence = zero propagation. No hallucination can sneak through without a paper trail.
The output is an interactive causal graph. Click any edge to see the evidence, bias warnings, and strength scores behind it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Three Design Decisions Worth Explaining
&lt;/h2&gt;

&lt;p&gt;Evidence-Modulated Propagation&lt;br&gt;
Confidence can only flow downstream if there's evidence supporting the edge. An unsupported causal link has zero propagation power — which means hallucinations can't compound through the graph.&lt;br&gt;
Adversarial Evidence&lt;br&gt;
Every edge gets both a supporting search and a contradicting search. Single-source claims get penalized up to 30%. This is the core anti-echo-chamber mechanism.&lt;br&gt;
Scenario Branching&lt;br&gt;
Change the strength of any causal edge, and confidence scores propagate in real time. Lets you ask "what if this assumption is wrong?" and see exactly what breaks downstream.&lt;/p&gt;

&lt;h2&gt;
  
  
  On Vibe Coding
&lt;/h2&gt;

&lt;p&gt;This idea sat in my head for six months. I kept thinking about the right architecture, the right approach, whether it was even worth building.&lt;br&gt;
Then I just opened Claude Code and started. First line of code to open-source: one day.&lt;br&gt;
I used to think "figure it out before you start" was the right move. Now I think some problems only become clear once you're in them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fi4lqwlyofh66jvpn5prg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fi4lqwlyofh66jvpn5prg.png" alt="App Preview" width="800" height="413"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Try It
&lt;/h2&gt;

&lt;p&gt;CurioCat is open source on GitHub — includes a demo dataset so you can run it without spending any tokens.&lt;br&gt;
👉 &lt;a href="https://github.com/coolgenerator/CurioCat" rel="noopener noreferrer"&gt;https://github.com/coolgenerator/CurioCat&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Star it, fork it, open an issue. I'm especially curious about use cases I haven't thought of yet — I've had conversations about geopolitical analysis, investment research, and competitive intelligence, but I suspect there are weirder and more interesting applications out there.&lt;/p&gt;

&lt;p&gt;What's the hardest information environment you deal with in your work? Drop it in the comments — genuinely curious.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
