<?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: Aditya D</title>
    <description>The latest articles on DEV Community by Aditya D (@adityaanenenu5).</description>
    <link>https://dev.to/adityaanenenu5</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2F99mvlsfu5tfj9m7ku25d.png</url>
      <title>DEV Community: Aditya D</title>
      <link>https://dev.to/adityaanenenu5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adityaanenenu5"/>
    <language>en</language>
    <item>
      <title>Samajh — a reader for the letters my mother couldn't read</title>
      <dc:creator>Aditya D</dc:creator>
      <pubDate>Fri, 02 Oct 2026 23:31:33 +0000</pubDate>
      <link>https://dev.to/adityaanenenu5/samajh-a-reader-for-the-letters-my-mother-couldnt-read-2emg</link>
      <guid>https://dev.to/adityaanenenu5/samajh-a-reader-for-the-letters-my-mother-couldnt-read-2emg</guid>
      <description>&lt;h1&gt;
  
  
  Samajh — a reader for the letters my mother couldn't read
&lt;/h1&gt;

&lt;h2&gt;
  
  
  The letter
&lt;/h2&gt;

&lt;p&gt;Every few weeks, an official letter arrives at home — a bank notice, an insurance renewal, a hospital bill, or another document written in formal English.&lt;/p&gt;

&lt;p&gt;My mother can understand the underlying idea, but the language of the document makes the important part difficult to follow.&lt;/p&gt;

&lt;p&gt;The problem is not always complexity. Sometimes one sentence determines whether something needs to be paid, when it is due, or what action is expected.&lt;/p&gt;

&lt;p&gt;I kept seeing someone else read and explain these documents.&lt;/p&gt;

&lt;p&gt;Understanding depended on another person.&lt;/p&gt;

&lt;p&gt;I wanted to build something that could help with that first step.&lt;/p&gt;

&lt;p&gt;That became &lt;strong&gt;Samajh&lt;/strong&gt;.&lt;/p&gt;




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

&lt;p&gt;&lt;strong&gt;Samajh&lt;/strong&gt; is a document reader and explainer designed for people who may understand their own language better than the formal language used in official documents.&lt;/p&gt;

&lt;p&gt;You provide a document, and Samajh explains it in simple language and in the reader's preferred language.&lt;/p&gt;

&lt;p&gt;Instead of producing one large AI-generated summary, it focuses on five things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;What is this?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What is the gist?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What does it want from me, and by when?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What numbers and dates matter?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What is easy to miss, and what is uncertain?&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Every factual explanation is connected back to the source document.&lt;/p&gt;

&lt;h3&gt;
  
  
  Input formats
&lt;/h3&gt;

&lt;p&gt;Samajh can work with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Plain text&lt;/li&gt;
&lt;li&gt;&lt;code&gt;.txt&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;.csv&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;PDF documents&lt;/li&gt;
&lt;li&gt;Photos/images when the configured AI model supports image input&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It supports multiple languages, including English and Telugu, so the explanation can be presented in the reader's own language.&lt;/p&gt;

&lt;p&gt;There is also deliberately no account, dashboard, or document history.&lt;/p&gt;

&lt;p&gt;The goal is simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Understand the document first.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Why quotes matter
&lt;/h2&gt;

&lt;p&gt;Large language models can produce fluent answers while still being wrong.&lt;/p&gt;

&lt;p&gt;That becomes a serious problem when the document contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;payment amounts&lt;/li&gt;
&lt;li&gt;deadlines&lt;/li&gt;
&lt;li&gt;dates&lt;/li&gt;
&lt;li&gt;policy conditions&lt;/li&gt;
&lt;li&gt;instructions&lt;/li&gt;
&lt;li&gt;warnings&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So Samajh does not treat the model's explanation as the final truth.&lt;/p&gt;

&lt;p&gt;For each factual claim, the system tries to preserve evidence from the original document.&lt;/p&gt;

&lt;p&gt;The flow is roughly:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Claim → Source quote → Verification&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The quote is independently checked against the extracted document text.&lt;/p&gt;

&lt;p&gt;If the system cannot verify the claim, it should not quietly present it as a fact.&lt;/p&gt;

&lt;p&gt;Instead, it can mark information as uncertain or leave it out.&lt;/p&gt;

&lt;p&gt;This was one of the most important design decisions in the project.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The goal is not to make AI sound confident. The goal is to make the result checkable.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;



&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
    A[Upload document] --&amp;gt; B[Extract text]
    B --&amp;gt; C[Structured AI analysis]
    C --&amp;gt; D[Validate model output]
    D --&amp;gt; E[Normalize and recover output]
    E --&amp;gt; F[Ground claims to source]
    F --&amp;gt; G[Reader-friendly explanation]&lt;/code&gt;&lt;/pre&gt;



</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>hf26challenge</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
