<?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: Uttam Kumar</title>
    <description>The latest articles on DEV Community by Uttam Kumar (@uttamofficial).</description>
    <link>https://dev.to/uttamofficial</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3958070%2F1f293864-7806-4e99-9f9a-6f78f2160d8d.jpg</url>
      <title>DEV Community: Uttam Kumar</title>
      <link>https://dev.to/uttamofficial</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/uttamofficial"/>
    <language>en</language>
    <item>
      <title>What If Your Documentation Could Argue With Itself? Meet TruthLayer.</title>
      <dc:creator>Uttam Kumar</dc:creator>
      <pubDate>Sat, 03 Oct 2026 11:14:51 +0000</pubDate>
      <link>https://dev.to/uttamofficial/what-if-your-documentation-could-argue-with-itself-meet-truthlayer-2bck</link>
      <guid>https://dev.to/uttamofficial/what-if-your-documentation-could-argue-with-itself-meet-truthlayer-2bck</guid>
      <description>&lt;p&gt;This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I Built&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;What if your documentation could check itself for contradictions?&lt;/p&gt;

&lt;p&gt;That was the idea behind TruthLayer.&lt;/p&gt;

&lt;p&gt;As documentation grows, information can quietly drift apart. One page might say an API supports 100 requests per minute, while another says 500. Both pages look perfectly fine on their own — until someone has to decide which one to trust.&lt;/p&gt;

&lt;p&gt;TruthLayer is an AI-powered knowledge health system built with Next.js and Sanity that looks for these inconsistencies across structured documentation.&lt;/p&gt;

&lt;p&gt;When it finds a potential conflict, it doesn't automatically rewrite anything. Instead, it creates a structured conflict in Sanity and sends it to a human review workflow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The flow is simple:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Sanity Content → AI Analysis → Conflict Detection → Human Review → Resolution&lt;/p&gt;

&lt;p&gt;This makes TruthLayer less like an AI writer and more like a spell-checker for organizational knowledge.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Demo&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🚀 Live Demo:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://truth-layer-five.vercel.app/" rel="noopener noreferrer"&gt;https://truth-layer-five.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The live application includes:&lt;/p&gt;

&lt;p&gt;• Knowledge Health Dashboard&lt;br&gt;
• Document Browser&lt;br&gt;
• Conflict Detection&lt;br&gt;
• Conflict Inspection&lt;br&gt;
• Human Review Workflow&lt;br&gt;
• Approve / Reject / Investigate actions&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fy6sc8rpax6b9nj49wzng.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fy6sc8rpax6b9nj49wzng.png" alt=" " width="800" height="403"&gt;&lt;/a&gt;&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpjzz3ykh68ya9rdr2zws.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpjzz3ykh68ya9rdr2zws.png" alt=" " width="800" height="403"&gt;&lt;/a&gt;&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffy4k2kz0uacvqrj1y5ci.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffy4k2kz0uacvqrj1y5ci.png" alt=" " width="800" height="403"&gt;&lt;/a&gt;&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjr6haf29o2tzz3veom6a.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjr6haf29o2tzz3veom6a.png" alt=" " width="800" height="403"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Code&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub Repository:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/uttamofficial/truth-layer" rel="noopener noreferrer"&gt;https://github.com/uttamofficial/truth-layer&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Built with Next.js, TypeScript, and Sanity.&lt;/p&gt;

&lt;p&gt;My Build Process&lt;/p&gt;

&lt;p&gt;I built TruthLayer using Google Antigravity.&lt;/p&gt;

&lt;p&gt;I started with the core idea and used the coding agent to turn it into a working product — from the Sanity schemas and frontend to the AI analysis API and review workflow.&lt;/p&gt;

&lt;p&gt;The Sanity content model is centered around three types:&lt;/p&gt;

&lt;p&gt;• knowledgeDocument — the actual documentation&lt;br&gt;
• contentConflict — detected inconsistencies&lt;br&gt;
• review — human decisions about those conflicts&lt;/p&gt;

&lt;p&gt;One interesting part of the build was the review workflow.&lt;/p&gt;

&lt;p&gt;The first version could display review actions, but I wanted those actions to actually affect the underlying Sanity data. I iterated on the implementation until approving, rejecting, or investigating a conflict became a real workflow rather than just UI buttons.&lt;/p&gt;

&lt;p&gt;I also tested the production build, Sanity connectivity, conflict detection, and review transitions.&lt;/p&gt;

&lt;p&gt;The biggest takeaway from vibe-coding this project:&lt;/p&gt;

&lt;p&gt;Getting an AI-generated app to compile is easy. Getting the workflow to actually make sense requires testing, breaking things, and giving the agent better instructions.&lt;/p&gt;

&lt;p&gt;Sanity Project Details&lt;/p&gt;

&lt;p&gt;Project ID:&lt;/p&gt;

&lt;p&gt;YOUR_SANITY_PROJECT_ID = NEXT_PUBLIC_SANITY_PROJECT_ID&lt;/p&gt;

&lt;p&gt;Dataset:&lt;/p&gt;

&lt;p&gt;production&lt;/p&gt;

&lt;p&gt;Main schemas:&lt;/p&gt;

&lt;p&gt;• knowledgeDocument&lt;br&gt;
• contentConflict&lt;br&gt;
• review&lt;/p&gt;

&lt;p&gt;Sanity isn't just being used as a database here. It holds the documentation, detected conflicts, and human review decisions as structured content.&lt;/p&gt;

&lt;p&gt;Agent Session&lt;/p&gt;

&lt;p&gt;Built and iterated using Google Antigravity.&lt;/p&gt;

&lt;p&gt;I used the coding agent for scaffolding, Sanity schema creation, UI development, AI integration, workflow implementation, debugging, and production testing.&lt;/p&gt;

&lt;p&gt;I don't currently have a suitable public Agent Session transcript to share.&lt;/p&gt;

&lt;p&gt;Why TruthLayer?&lt;/p&gt;

&lt;p&gt;Documentation rarely becomes wrong all at once.&lt;/p&gt;

&lt;p&gt;It becomes wrong one outdated page at a time.&lt;/p&gt;

&lt;p&gt;TruthLayer explores a simple idea:&lt;/p&gt;

&lt;p&gt;What if we could detect those inconsistencies before someone discovers them the hard way?&lt;/p&gt;

&lt;p&gt;That's the problem I wanted to explore with Sanity.&lt;/p&gt;

&lt;p&gt;A few alternative titles&lt;/p&gt;

&lt;p&gt;If you want something even more attention-grabbing:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;What If Your Documentation Could Argue With Itself? Meet TruthLayer.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;I Built an AI That Checks Whether Your Docs Agree With Each Other&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Your Docs Are Lying to You. TruthLayer Wants to Know Why.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;I Gave Sanity a Memory — Now It Can Find Contradictions&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;When Your Docs Disagree, Who's Right? I Built TruthLayer.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;I Vibe-Coded a Spell-Checker for Organizational Knowledge&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Your Documentation Has Contradictions. This AI Finds Them.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My pick: “What If Your Documentation Could Argue With Itself? Meet TruthLayer.”&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>sanitychallenge</category>
      <category>sanity</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
