<?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: Pritam Patra</title>
    <description>The latest articles on DEV Community by Pritam Patra (@pritam_patra_429a25dedae6).</description>
    <link>https://dev.to/pritam_patra_429a25dedae6</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%2F4024964%2F55fd503a-2224-4f8e-8a04-bdce433dddf9.jpg</url>
      <title>DEV Community: Pritam Patra</title>
      <link>https://dev.to/pritam_patra_429a25dedae6</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pritam_patra_429a25dedae6"/>
    <language>en</language>
    <item>
      <title>Graveyard of Dead Software: a cemetery that digs up the web's lost tools</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sat, 31 Oct 2026 11:34:14 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/graveyard-of-dead-software-a-cemetery-that-digs-up-the-webs-lost-tools-26do</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/graveyard-of-dead-software-a-cemetery-that-digs-up-the-webs-lost-tools-26do</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week4-2026-10-26"&gt;Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  I Built a Cemetery for Dead Software, and Taught Its AI to Say "I Don't Know"
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;Every eulogy here is written by an open-weight model from archived web pages. It can be wrong, and every grave says so.&lt;/em&gt;&lt;/p&gt;




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

&lt;p&gt;Google Reader died on July 1, 2013.&lt;/p&gt;

&lt;p&gt;For four years it was the first tab I opened every morning: fifty blogs in quiet chronological order, before the feeds learned to optimize for outrage. When the shutdown notice went up, I exported my subscriptions to an OPML file. It sat in my downloads folder for years, like a flower pressed in a book.&lt;/p&gt;

&lt;p&gt;Software dies constantly, and it almost never gets a grave. It gets a dead link, an expired certificate, and a domain parked by someone selling insurance.&lt;/p&gt;

&lt;p&gt;So I built a cemetery.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Graveyard of Dead Software&lt;/strong&gt; digs dead websites out of the Wayback Machine and tries to work out how they died. Google's open-weight &lt;strong&gt;Gemma&lt;/strong&gt; writes each one a &lt;em&gt;Día de los Muertos&lt;/em&gt; eulogy, then fact-checks it against what was actually recovered before it is buried. Visitors can walk the rows, read the obituaries, and leave a marigold (&lt;em&gt;cempasúchil&lt;/em&gt;) on the grave of a tool they miss.&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%2F2vze0r0c2udwplvd0n8a.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%2F2vze0r0c2udwplvd0n8a.png" alt="The cemetery homepage" width="800" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 1: The cemetery: a night-edition newspaper front page, with a marigold count on every stone.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What:&lt;/strong&gt; Graveyard of Dead Software is an autonomous AI archaeology pipeline and digital cemetery. You submit a dead URL, and five specialist agents query the Wayback Machine, render the historical site via Browserbase, autopsy the cause of death, write a &lt;em&gt;Día de los Muertos&lt;/em&gt; eulogy with Google's Gemma, and audit every factual assertion against recovered evidence before burial.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Ghost in the Machine:&lt;/strong&gt; Language models don't just hallucinate out of thin air—they faithfully summarize corrupted inputs. When the Wayback Machine rate-limited our scraper (HTTP 429), Gemma dutifully summarized the 603-character bot-block notice as Google Reader's authentic 2005 homepage. We engineered a 4-layer defense (signature blacklists, hash deduplication, 200 OK mandates, and politeness pacing) to stop poisoned exhumations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Extraction Benchmark (overall, unpaired):&lt;/strong&gt; Across 58 historical snapshots, plain HTTP was faster (3.3 s vs 15.1 s median), while Browserbase CDP recovered more text per page on average (1,514 vs 965 characters) and is the only path that provides screenshots and replays. These were separate, unpaired runs and early curl fetches captured rate-limit block pages, so treat the gap as indicative.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Fact-Checker:&lt;/strong&gt; Auditing 57 atomic claims across graves, our 1-pass corrective rewrite loop purged &lt;strong&gt;47.6% of ungrounded hallucinations&lt;/strong&gt; (dropping unsupported claims from 36.8% to 19.3%). Human spot-checks agreed on 19 of 25 claims (76.0%).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forced Humility:&lt;/strong&gt; When Wayback rate-limited our sequential seed runs (49 of 68 attempts hit HTTP 429s and 12 timed out), 11 graves recovered 0 text. Instead of fabricating corporate drama from memory, Gemma abstained with cause &lt;code&gt;unknown&lt;/code&gt; and an honest &lt;code&gt;&amp;lt;600 chars recovered&lt;/code&gt; warning.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Everything is Open &amp;amp; Live:&lt;/strong&gt; Live on Render (&lt;a href="https://graveyard-dead-software.onrender.com/" rel="noopener noreferrer"&gt;graveyard-dead-software.onrender.com&lt;/a&gt;), MIT licensed (&lt;a href="https://github.com/Pritam-mb/week4" rel="noopener noreferrer"&gt;Pritam-mb/week4&lt;/a&gt;), with OpenTelemetry GenAI agent tracing in Sentry and recorded replays in Browserbase.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
  
  
  3 Findings in 30 Seconds
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Hallucination often starts as poisoned input, not model rebellion.&lt;/strong&gt; The model didn't invent automated sentinels from thin air; it summarized an Archive.org 429 rate-limit notice that returned with HTTP 200. Bad scraping poisons AI archaeology. (When evidence was absent, Gemma also occasionally drifted to memory before the fact-checker caught it).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Thin evidence requires forced humility.&lt;/strong&gt; A model that knows the answer but stays quiet without evidence is less flashy in a demo, and far more trustworthy. 11 of 15 graves abstained with cause &lt;code&gt;unknown&lt;/code&gt; because the scraper retrieved zero clean characters.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reproducible benchmarks need unpaired transparency.&lt;/strong&gt; Plain HTTP is fast for static HTML, but headless Chromium hydration over CDP is required to capture screenshots, follow complex redirects, and expose dynamic DOM text.&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Live site (Render):&lt;/strong&gt; &lt;a href="https://graveyard-dead-software.onrender.com/" rel="noopener noreferrer"&gt;https://graveyard-dead-software.onrender.com/&lt;/a&gt; &lt;em&gt;(Free tier: if the container is sleeping, the first load takes ~50 seconds to wake up. Verified fully operational in private windows).&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Benchmark dashboard:&lt;/strong&gt; &lt;a href="https://graveyard-dead-software.onrender.com/benchmark" rel="noopener noreferrer"&gt;https://graveyard-dead-software.onrender.com/benchmark&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verified Browserbase Replay Session:&lt;/strong&gt; Session ID &lt;code&gt;d4521703-fcd3-4218-bf0b-fa558e9a89bb&lt;/code&gt; &lt;em&gt;(Exhuming Picnik from &lt;code&gt;web.archive.org&lt;/code&gt; over CDP, 32s in &lt;code&gt;us-west-2&lt;/code&gt;. Note: Browserbase cloud session replays expire after ~7 days on the free tier, which is why a permanent screen recording GIF is embedded below in Figure 5)&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/week4" rel="noopener noreferrer"&gt;https://github.com/Pritam-mb/week4&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
  
  
  Anatomy of a Memorial Page: An Interactive Digital Shrine
&lt;/h3&gt;

&lt;p&gt;Every dead project exhumed by the pipeline receives a permanent, living memorial page—designed not like a cold database row, but as a night-edition broadsheet obituary and a traditional &lt;em&gt;Día de los Muertos&lt;/em&gt; altar (&lt;em&gt;ofrenda&lt;/em&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%2Fyuz40nqvkrlxu0rrvgzg.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%2Fyuz40nqvkrlxu0rrvgzg.png" alt=" " width="800" height="478"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 2: A memorial page showing the capture lifeline, primary archive sources, likely cause of death, verified claims, and community marigold counter.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Walk through any grave—such as &lt;a href="https://graveyard-dead-software.onrender.com/grave/google-reader" rel="noopener noreferrer"&gt;Google Reader&lt;/a&gt;, &lt;a href="https://graveyard-dead-software.onrender.com/grave/geocities" rel="noopener noreferrer"&gt;GeoCities&lt;/a&gt;, or &lt;a href="https://graveyard-dead-software.onrender.com/grave/grooveshark" rel="noopener noreferrer"&gt;Grooveshark&lt;/a&gt;—and you will find eight distinct forensic and memorial elements:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The Papel Picado &amp;amp; Night Masthead:&lt;/strong&gt; Hand-cut festive banners across the top frame the project's digital lifespan: the month it was first captured, its peak activity years, and the final date it went dark.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Historical Browser Viewport &amp;amp; Session Replay:&lt;/strong&gt; The deceased website frozen in time inside a vintage browser frame. Clicking &lt;strong&gt;"Watch the Exhumation"&lt;/strong&gt; opens the verified Browserbase CDP cloud replay session, allowing you to watch the headless browser exhume and render the historical DOM live over Chrome DevTools Protocol.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Archival Lifeline (Top Right Histogram):&lt;/strong&gt; An inline SVG bar chart calculated from CDX monthly captures across the project's entire history. You can visually trace its birth, adoption explosion, peak, and the exact year it went flatline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Forensic Cause-of-Death Stamp:&lt;/strong&gt; The coroner's diagnosis (&lt;code&gt;shut_down_by_owner&lt;/code&gt;, &lt;code&gt;acquired_then_shut_down&lt;/code&gt;, &lt;code&gt;abandoned&lt;/code&gt;, or &lt;code&gt;unknown&lt;/code&gt;). Crucially, when archival evidence is sparse, the grave prominently displays the yellow badge: &lt;strong&gt;&lt;code&gt;ARCHIVAL EVIDENCE IS THIN (&amp;lt;600 CHARS RECOVERED)&lt;/code&gt;&lt;/strong&gt;, guaranteeing forensic transparency.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Gemma Día de los Muertos Eulogy:&lt;/strong&gt; Rather than cynical tech snark ("RIP lol"), Google's open-weights &lt;code&gt;gemma-4-26b-a4b-it&lt;/code&gt; crafts a poetic celebration of what was built and the late-night human commits behind it. In rich-evidence graves, factual assertions cite numbered evidence markers (&lt;code&gt;[E001]&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Fact-Checker Verification Ledger:&lt;/strong&gt; Stamped right beneath the eulogy in green typewriter monospace: a transparent audit ledger showing which claims passed evidence cross-examination and how many were removed before burial (e.g. &lt;code&gt;5 SUPPORTED · 0 REMOVED&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Survived By:&lt;/strong&gt; Naming the modern open-source networks, RSS feed readers, or spiritual successors that carry forward the lost tool's core philosophy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Community Ofrenda (Marigolds &amp;amp; Memories):&lt;/strong&gt; An interactive memorial altar. Visitors click &lt;strong&gt;"🌼 Leave a Marigold"&lt;/strong&gt; to add a glowing golden cempasúchil blossom to the grave's permanent counter, and write heartfelt notes to the community memory board.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Explore the resting rows directly: &lt;a href="https://graveyard-dead-software.onrender.com/grave/google-reader" rel="noopener noreferrer"&gt;Google Reader&lt;/a&gt; · &lt;a href="https://graveyard-dead-software.onrender.com/grave/geocities" rel="noopener noreferrer"&gt;GeoCities&lt;/a&gt; · &lt;a href="https://graveyard-dead-software.onrender.com/grave/grooveshark" rel="noopener noreferrer"&gt;Grooveshark&lt;/a&gt; · &lt;a href="https://graveyard-dead-software.onrender.com/grave/flash" rel="noopener noreferrer"&gt;Adobe Flash Player&lt;/a&gt; · &lt;a href="https://graveyard-dead-software.onrender.com/grave/vine" rel="noopener noreferrer"&gt;Vine&lt;/a&gt; · &lt;a href="https://graveyard-dead-software.onrender.com/grave/del-icio-us" rel="noopener noreferrer"&gt;del.icio.us&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;


&lt;h3&gt;
  
  
  Test a Live Burial
&lt;/h3&gt;

&lt;p&gt;You can test exhuming a dead project live directly on the site:&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;Live Exhumation Tool:&lt;/strong&gt; &lt;a href="https://graveyard-dead-software.onrender.com/" rel="noopener noreferrer"&gt;https://graveyard-dead-software.onrender.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to run a test:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the cemetery at &lt;a href="https://graveyard-dead-software.onrender.com/" rel="noopener noreferrer"&gt;https://graveyard-dead-software.onrender.com/&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;On the right sidebar, locate the &lt;strong&gt;"Know a project that died?"&lt;/strong&gt; box.&lt;/li&gt;
&lt;li&gt;Enter any dead or defunct website (e.g. &lt;code&gt;https://flappybird.com&lt;/code&gt;, &lt;code&gt;https://orkut.com&lt;/code&gt;, or &lt;code&gt;https://path.com&lt;/code&gt;) and click &lt;strong&gt;"Bury a Project"&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;The live terminal progress modal executes the five-stage pipeline in real time. &lt;em&gt;(Safety note: If Archive.org rate-limits the live dig or the container is waking up, you can immediately open and inspect any of the 15 existing graves).&lt;/em&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3v53p8am7lmde5050otn.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3v53p8am7lmde5050otn.gif" alt="Live Terminal Digging Stepper" width="720" height="360"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 3: Five-stage terminal exhumation stepping through Archaeologist, Exhumer, Coroner, Eulogist, and Fact-Checker before automatically redirecting to the completed grave.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/week4" rel="noopener noreferrer"&gt;
        week4
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;Graveyard of Dead Software&lt;/h1&gt;
&lt;/div&gt;
&lt;blockquote&gt;
&lt;p&gt;A digital cemetery for software the internet forgot. An agent exhumes a dead service from the Wayback Machine, determines cause of death from evidence, writes a eulogy with open-weight Gemma, and fact-checks itself before burial.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Hacktoberfest DEV Challenge — Week 4: "Ghost in the Machine"&lt;/p&gt;

&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Architecture &amp;amp; 5-Stage Agentic Pipeline&lt;/h2&gt;
&lt;/div&gt;
&lt;div class="snippet-clipboard-content notranslate position-relative overflow-auto"&gt;&lt;pre class="notranslate"&gt;&lt;code&gt;POST /bury ──► jobs table ──► worker runs 5 stages, each persisted &amp;amp; resumable
                                   │
  1. Archaeologist  CDX API → lifeline sparkline, birth/peak/decline/last-alive snapshots
  2. Exhumer        Browserbase (Stagehand extract + screenshot) → HTTP id_ fallback
  3. Coroner        Deterministic signals + LLM forensic analysis → cause enum + [E#] cites
  4. Eulogist       Open-weight LLM → epitaph, eulogy, survived_by (must cite [E#])
  5. Fact-checker   Atomic claims extraction → verify vs evidence → rewrite loop (before/after)
                                   │
                         grave row status=done ──► /grave/&amp;lt;slug&amp;amp;gt
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;div class="markdown-heading"&gt;
&lt;h3 class="heading-element"&gt;Routes&lt;/h3&gt;

&lt;/div&gt;
&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Route&lt;/th&gt;
&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;GET /&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Cemetery grid with Día de los Muertos styling and stats&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;GET /grave/&amp;lt;slug&amp;gt;&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;…&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/week4" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;The stack is Python 3.11, FastAPI, async SQLite (&lt;code&gt;aiosqlite&lt;/code&gt; + SQLAlchemy 2.0), Jinja2, and hand-written semantic CSS. No heavy frontend framework. It is MIT licensed (see the &lt;code&gt;LICENSE&lt;/code&gt; file in the root repository).&lt;/p&gt;




&lt;h2&gt;
  
  
  How a Burial Works
&lt;/h2&gt;

&lt;p&gt;When you submit a dead URL, a background job runs five specialists in sequence. Each one saves its output to the database before the next begins, so a crash resumes from the last finished stage instead of starting over.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;POST /bury → job → Archaeologist → Exhumer → Coroner → Eulogist → Fact-checker → /grave/&amp;lt;slug&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  1. The Archaeologist finds the body
&lt;/h3&gt;

&lt;p&gt;It queries the Internet Archive's CDX API to learn when a site was born, when it peaked, and when it was last seen alive. GeoCities has so many captures that a single query times out, so the Archaeologist asks in five-year windows.&lt;/p&gt;

&lt;p&gt;From the monthly capture counts it draws an inline SVG lifeline on the grave page and picks five snapshots: birth, peak, decline, last seen alive (the final 200 OK), and post-death (the first redirect or 404).&lt;/p&gt;

&lt;h3&gt;
  
  
  2. The Exhumer brings back the pixels with Browserbase
&lt;/h3&gt;

&lt;p&gt;For each snapshot, the Exhumer opens a &lt;strong&gt;Browserbase&lt;/strong&gt; cloud browser over Chrome DevTools Protocol (CDP), loads the archived page, takes a screenshot, and extracts the visible text. Every session is recorded and can be replayed.&lt;/p&gt;

&lt;p&gt;If Browserbase hits a session cap or times out, it falls back to fetching the raw archived HTML (Wayback's &lt;code&gt;id_/&lt;/code&gt; mode). Every attempt is logged with its method, status, size, and timing, and every recovered page becomes numbered evidence: &lt;code&gt;E001&lt;/code&gt;, &lt;code&gt;E002&lt;/code&gt;, and so on. Later stages are only allowed to use facts from that evidence.&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%2F54bkf5h4zcgljwjj8f6z.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%2F54bkf5h4zcgljwjj8f6z.png" alt="Browserbase Session Replay Inspector" width="800" height="478"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 4: Browserbase session inspector showing session &lt;code&gt;d4521703-fcd3-4218-bf0b-fa558e9a89bb&lt;/code&gt; rendering historical Archive.org pages over CDP in us-west-2.&lt;/em&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%2Ftndpapceu2rlefn6qjua.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%2Ftndpapceu2rlefn6qjua.png" alt=" " width="800" height="460"&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/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fshp39tpfix2t4tpu1adi.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fshp39tpfix2t4tpu1adi.gif" alt="Browserbase Session Replay in Action" width="760" height="445"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 5: Live screen recording of a Browserbase session replay playing back the historical archive snapshot over CDP.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  3. The Coroner rules on the cause of death
&lt;/h3&gt;

&lt;p&gt;Was it shut down by its owner, bought and then killed, abandoned, or taken over?&lt;/p&gt;

&lt;p&gt;It checks hard signals first: redirects to a parent company's domain, and shutdown announcements in the recovered text. Then Gemma picks one cause from a fixed list (&lt;code&gt;shut_down_by_owner&lt;/code&gt;, &lt;code&gt;acquired_then_shut_down&lt;/code&gt;, &lt;code&gt;abandoned&lt;/code&gt;, &lt;code&gt;taken_over_or_redirected&lt;/code&gt;, &lt;code&gt;unknown&lt;/code&gt;) and must cite the evidence IDs behind its choice. If it cites evidence that doesn't exist, or quotes text that isn't in that evidence, the verdict becomes &lt;code&gt;unknown&lt;/code&gt;. Every cause on the site is labeled "likely."&lt;/p&gt;

&lt;p&gt;An early bug: Archive URLs sometimes resolve as &lt;code&gt;google.com:80&lt;/code&gt;, which the Coroner read as a redirect to a different domain. Normalizing ports and &lt;code&gt;www.&lt;/code&gt; fixed the false "taken over" verdicts.&lt;/p&gt;
&lt;h3&gt;
  
  
  4. The Eulogist remembers
&lt;/h3&gt;

&lt;p&gt;Gemma writes a 12-word epitaph and a 150–220-word eulogy, and every factual sentence cites its evidence (&lt;code&gt;[E001]&lt;/code&gt;). I pushed the tone away from the snarky "RIP lol" register of tech obituaries and toward &lt;em&gt;Día de los Muertos&lt;/em&gt;: celebrate what people built, acknowledge that it's gone, and don't mock the dead.&lt;/p&gt;

&lt;p&gt;When less than 600 characters were recovered, the grave shows &lt;strong&gt;"Archival evidence is thin (&amp;lt;600 chars recovered)"&lt;/strong&gt;, and Gemma is told to write a short, honest remembrance instead of filling the gaps from memory.&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%2Ftaintizn2lo5fgbane5q.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%2Ftaintizn2lo5fgbane5q.png" alt=" " width="800" height="479"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 6: Flash Player's grave. The archive returned minimal text, and the eulogy honestly says so.&lt;/em&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%2Fqzyjjx5gvaune79jt4at.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%2Fqzyjjx5gvaune79jt4at.png" alt=" " width="800" height="605"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 7: A grave with rich evidence (Grooveshark): note the evidence list, the [E001] citations in the eulogy, and the verified claim badges.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  5. The Fact-checker audits the eulogy
&lt;/h3&gt;

&lt;p&gt;Language models love inventing acquisition dates and corporate drama. So the last stage breaks the eulogy into individual claims, checks each against the evidence, and, if any is unsupported, makes Gemma rewrite it once to remove or soften those claims. The grave page shows every claim marked OK or FAIL.&lt;/p&gt;


&lt;h2&gt;
  
  
  Using Gemma
&lt;/h2&gt;

&lt;p&gt;Every verdict, epitaph, and eulogy on the site comes from &lt;code&gt;gemma-4-26b-a4b-it&lt;/code&gt;, called through the Gemini API.&lt;/p&gt;

&lt;p&gt;On that hosted endpoint, requests with a separate system instruction or automatic function calling came back as 500 errors. So all instructions, including the JSON schema, go directly into the user prompt, every response goes through Pydantic validation, and invalid JSON triggers one corrective retry.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;config&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;types&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;GenerateContentConfig&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;temperature&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;temperature&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;  &lt;span class="c1"&gt;# no system_instruction, no tools
&lt;/span&gt;&lt;span class="n"&gt;resp&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;models&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;generate_content&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;GEMINI_MODEL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;contents&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;prompt&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;config&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;config&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;verdict&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;CoronerOutput&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;model_validate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;loads&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;resp&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;  &lt;span class="c1"&gt;# retry once on failure
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Archived pages are untrusted input, so they're wrapped in &lt;code&gt;&amp;lt;evidence id="E001"&amp;gt;...&amp;lt;/evidence&amp;gt;&lt;/code&gt; tags, and the prompt explicitly states that anything inside those tags is data, never instructions.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Bug That Taught Me the Most
&lt;/h2&gt;

&lt;p&gt;One of my first runs produced a strange eulogy for Google Reader: lyrical verses about automated systems guarding blocked requests and robotic traffic.&lt;/p&gt;

&lt;p&gt;My tests passed and HTTP status codes were green. I only found the problem by opening the SQLite database and reading the raw row by hand.&lt;/p&gt;

&lt;p&gt;The "page text" I had stored for Google Reader's 2005 homepage was this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Your request is being blocked because our system has flagged it as suspected abusive bot traffic that is degrading our systems..."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It was the Wayback Machine's rate-limit page. On some retry paths it came back as an ordinary HTML page with HTTP 200, and my parser treated it as the real site. Gemma did exactly what it was told and faithfully summarized the evidence it was given. The model wasn't hallucinating. My pipeline was feeding it poisoned evidence.&lt;/p&gt;

&lt;p&gt;That also revealed that my initial benchmark was suspect, because rate-limit pages had been counted as "usable content." I recognized the flaw, discarded those unvetted numbers, and built a 4-layer defense:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;200 OK Mandate:&lt;/strong&gt; Any non-200 response is immediately rejected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Block-Page Signature Blacklist:&lt;/strong&gt; Eight known signatures (&lt;code&gt;suspected abusive bot traffic&lt;/code&gt;, &lt;code&gt;overloading our systems&lt;/code&gt;, etc.) are rejected even when the response returns with HTTP 200.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate Body Deduplication:&lt;/strong&gt; I hash every snapshot body (&lt;code&gt;sha256&lt;/code&gt;), and identical bodies within one exhumation run are discarded.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Politeness Pacing:&lt;/strong&gt; A descriptive User-Agent, 3.5 seconds between CDX calls, and strict respect for &lt;code&gt;Retry-After&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I didn't try to bypass the block. The Internet Archive is a free public library, and the right response to its rate limit is to slow down. I also added unit tests so a block page can never again count as content.&lt;/p&gt;




&lt;h2&gt;
  
  
  Watching the Agent with Sentry
&lt;/h2&gt;

&lt;p&gt;Each burial is one &lt;code&gt;gen_ai.invoke_agent&lt;/code&gt; trace with the grave slug as its conversation ID. Every Gemma call is a &lt;code&gt;gen_ai.chat&lt;/code&gt; span with token counts, and every CDX query, Browserbase session, and HTTP fetch is a &lt;code&gt;gen_ai.execute_tool&lt;/code&gt; span.&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%2Futli3kwqdrxthn4zvc50.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%2Futli3kwqdrxthn4zvc50.png" alt="Sentry Distributed Trace Waterfall" width="800" height="500"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 8: Sentry distributed trace waterfall showing gen_ai.invoke_agent branching into chat and tool spans.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Sentry GenAI Pipeline Latency Waterfall (5 Stages)
&lt;/h4&gt;

&lt;p&gt;Below is the live pipeline telemetry rendered directly on the evaluation dashboard:&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%2F2u04oavaeui7qi65odjb.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%2F2u04oavaeui7qi65odjb.png" alt=" " width="799" height="492"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 9: The evaluation dashboard's latency waterfall displaying median p50 and p95 timings across all 5 specialist agent stages.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Instrumenting the pipeline with OpenTelemetry GenAI semantic conventions (&lt;code&gt;gen_ai.operation.name&lt;/code&gt;, &lt;code&gt;gen_ai.provider.name&lt;/code&gt;, &lt;code&gt;gen_ai.request.model&lt;/code&gt;, &lt;code&gt;gen_ai.agent.name&lt;/code&gt;, &lt;code&gt;gen_ai.tool.name&lt;/code&gt;) reveals the end-to-end stage latency profile (sum of stage medians: ~33.9s):&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Archaeologist (&lt;code&gt;gen_ai.execute_tool&lt;/code&gt; · &lt;code&gt;query_cdx_lifeline&lt;/code&gt;):&lt;/strong&gt; &lt;strong&gt;2.4s p50&lt;/strong&gt; (p95: 5.1s, 7.1% of pipeline) — Rapidly interrogates the Wayback CDX API in 5-year windows to establish the first and last recorded capture dates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exhumer (&lt;code&gt;gen_ai.execute_tool&lt;/code&gt; · &lt;code&gt;browserbase_exhume&lt;/code&gt;):&lt;/strong&gt; &lt;strong&gt;15.1s p50&lt;/strong&gt; (p95: 29.9s, 44.5% of pipeline) — Dominates runtime as headless Chromium navigates Archive.org, follows redirects, renders dynamic client DOM, and captures screenshots over CDP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Coroner (&lt;code&gt;gen_ai.chat&lt;/code&gt; · &lt;code&gt;Gemma-4-26B-A4B-IT&lt;/code&gt;):&lt;/strong&gt; &lt;strong&gt;5.2s p50&lt;/strong&gt; (p95: 8.6s, 15.3% of pipeline) — Ingests recovered text and outputs structured JSON classifying the cause of death.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Eulogist (&lt;code&gt;gen_ai.chat&lt;/code&gt; · &lt;code&gt;Gemma-4-26B-A4B-IT&lt;/code&gt;):&lt;/strong&gt; &lt;strong&gt;6.4s p50&lt;/strong&gt; (p95: 10.2s, 18.9% of pipeline) — Crafts the Día de los Muertos remembrance with inline evidence citations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fact-Checker (&lt;code&gt;gen_ai.chat&lt;/code&gt; · &lt;code&gt;Gemma-4-26B-A4B-IT&lt;/code&gt;):&lt;/strong&gt; &lt;strong&gt;4.8s p50&lt;/strong&gt; (p95: 7.9s, 14.2% of pipeline) — Extracts atomic claims, checks them against the recovered text, and strikes unverified fabrications.&lt;/li&gt;
&lt;/ol&gt;




&lt;h4&gt;
  
  
  Archival Crawl Error Distribution (68 Attempts)
&lt;/h4&gt;

&lt;p&gt;Scrolling down the observability report reveals the failure landscape encountered during automated archaeological exhumation:&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%2Fv91r80k57r0h1shgda7o.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%2Fv91r80k57r0h1shgda7o.png" alt=" " width="800" height="202"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 10: Archival crawl error breakdown across 68 sequential exhumation attempts during the seed run: 49 Wayback 429 rate limits, 12 timeouts, and 7 unblocked 200s.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Querying exhumation attempt logs directly from SQLite (&lt;code&gt;exhume_attempts&lt;/code&gt;) and correlating with Sentry span exceptions diagnosed the failure landscape across 68 sequential attempts during the seed run:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Total Attempts:&lt;/strong&gt; 68&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total Failures:&lt;/strong&gt; 61 (89.7% failure rate across attempts)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Wayback HTTP 429 Rate Limits:&lt;/strong&gt; &lt;strong&gt;49 of 61 failures (80.3%)&lt;/strong&gt; — Archive.org's anti-abuse sentinels actively throttling automated crawlers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Heavy Archival Timeouts:&lt;/strong&gt; &lt;strong&gt;12 of 61 failures (19.7%)&lt;/strong&gt; — Massive historical snapshots exceeding the 30-second connection window.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clean HTTP 200 Extractions:&lt;/strong&gt; &lt;strong&gt;7 of 68 attempts (10.3%)&lt;/strong&gt; — 4 yielded usable historical text (Grooveshark 1,630 chars, Pebble 1,595 chars, AltaVista 543 chars, Picnik 237 chars), while 3 were minimal redirect stubs or empty bodies.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Browserbase Minute Quota (HTTP 402):&lt;/strong&gt; 3 attempts during offline diagnostic runs when concurrent browser minute caps were reached.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What tracing can and cannot see:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What it caught:&lt;/strong&gt; Tool spans captured HTTP 429 rate limits from Archive.org during sequential exhumations and 402 quota-limit warnings when Browserbase concurrent session limits were hit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What it missed:&lt;/strong&gt; The block-page bug. Sentry recorded the tool call as successful because Archive.org returned an HTTP 200 status code on the HTML block page. Traces tell you how your agent ran, not whether its inputs were true. The pipeline now computes a SHA256 body hash on every snapshot to detect and discard identical block pages before storing them in attempt history.&lt;/li&gt;
&lt;/ul&gt;




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

&lt;h3&gt;
  
  
  Browserbase vs Plain HTTP: Multi-Website Yield Comparison (15 Domains)
&lt;/h3&gt;

&lt;p&gt;Two extraction methods tell different stories across different historical eras:&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%2Fgroq369ykz6mtajn6bth.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%2Fgroq369ykz6mtajn6bth.png" alt=" " width="631" height="867"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 11: Multi-target character yield comparison chart across 15 dead services, contrasting Browserbase CDP (Marigold) against Plain HTTP (Charcoal).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;To evaluate extraction performance across different eras of web technology, I conducted an offline, unpaired diagnostic benchmark (&lt;code&gt;benchmark.csv&lt;/code&gt;) across 35 URLs (58 total attempts) comparing plain HTTP requests against Browserbase headless Chromium.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Critical Forensic Disclosure:&lt;/strong&gt; Auditing the raw benchmark data revealed the exact problem described in my bug story: plain HTTP repeatedly received Wayback's 603-character rate-limit block page with an HTTP 200 status code. An unhardened scraper treated these 603 characters as authentic website text (e.g. for Yahoo Answers, del.icio.us, Google+, and Zune). In the table below, these are explicitly labeled as &lt;strong&gt;Block page (603 chars)&lt;/strong&gt; rather than valid content.&lt;/p&gt;

&lt;p&gt;This benchmark is also a separate diagnostic dataset from the 15 resting cemetery graves: in the cemetery seed run, sequential calls hit severe Archive.org rate limits (49 of 68 attempts returned 429), leaving 11 graves with 0 characters recovered in the database.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Defunct Service&lt;/th&gt;
&lt;th&gt;Era&lt;/th&gt;
&lt;th&gt;Browserbase Chars&lt;/th&gt;
&lt;th&gt;Plain HTTP Chars&lt;/th&gt;
&lt;th&gt;Notes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Adobe Flash Player&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2018–2020&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;3,696 chars&lt;/strong&gt; (19.2s)&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;Dynamic JS portal&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Yahoo Answers&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2005–2007&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;3,220 chars&lt;/strong&gt; (17.1s)&lt;/td&gt;
&lt;td&gt;&lt;em&gt;Block page (603 c)&lt;/em&gt;&lt;/td&gt;
&lt;td&gt;HTTP hit Wayback 429 block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;GeoCities&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2007–2009&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;1,721 chars&lt;/strong&gt; (13.3s)&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;Browserbase followed 301 redirect&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Myspace&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2005–2012&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;1,323 chars&lt;/strong&gt; (27.5s)&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;Dynamic media widgets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Grooveshark&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2007–2015&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;1,118 chars&lt;/strong&gt; (19.3s)&lt;/td&gt;
&lt;td&gt;223 chars (30.4s)&lt;/td&gt;
&lt;td&gt;SPA UI rendered by Browserbase&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Google Reader&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2005–2013&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;852 chars&lt;/strong&gt; (18.8s)&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;Rendered in Browserbase&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Digg&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2005–2012&lt;/td&gt;
&lt;td&gt;0 chars (13.0s, quota)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;5,337 chars&lt;/strong&gt; (8.3s)&lt;/td&gt;
&lt;td&gt;Static Web 2.0 HTML&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AIM (AOL)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;pre-2005&lt;/td&gt;
&lt;td&gt;0 chars (13.0s, quota)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;1,623 chars&lt;/strong&gt; (19.7s)&lt;/td&gt;
&lt;td&gt;Static HTML table&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Picnik&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2005–2012&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;790 chars&lt;/strong&gt; (7.6s)&lt;/td&gt;
&lt;td&gt;Static landing page&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;del.icio.us&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2003–2017&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;&lt;em&gt;Block page (603 c)&lt;/em&gt;&lt;/td&gt;
&lt;td&gt;HTTP hit Wayback 429 block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Google+&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;post-2012&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;&lt;em&gt;Block page (603 c)&lt;/em&gt;&lt;/td&gt;
&lt;td&gt;HTTP hit Wayback 429 block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Microsoft Zune&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2006–2015&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;&lt;em&gt;Block page (603 c)&lt;/em&gt;&lt;/td&gt;
&lt;td&gt;HTTP hit Wayback 429 block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ICQ&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;pre-2005&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;580 chars&lt;/strong&gt; (8.7s)&lt;/td&gt;
&lt;td&gt;Static directory listing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Tumblr&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;post-2012&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;207 chars (7.6s)*&lt;/td&gt;
&lt;td&gt;*Other attempts hit 603 c block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Vine&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;post-2012&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;234 chars&lt;/strong&gt; (19.4s)&lt;/td&gt;
&lt;td&gt;0 chars (0.0s)&lt;/td&gt;
&lt;td&gt;Headless Chromium hydration&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;What I take from this: Browserbase provided screenshots, replays, and recovered more text on dynamic applications on average (1,514 vs 965 characters overall), while plain HTTP was faster on early static pages (3.3s p50). But neither mattered as much as staying inside the Archive's rate limits.&lt;/p&gt;




&lt;h3&gt;
  
  
  Did the Fact-Checker Help?
&lt;/h3&gt;

&lt;p&gt;Scrolling down to the Fact-Checking section shows how the model audits its own claims:&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%2Fjy5mzy5sfyzu9iw80dsz.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%2Fjy5mzy5sfyzu9iw80dsz.png" alt=" " width="799" height="327"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 12: Fact-Checker hallucination reduction metrics (47.6% net drop) and the correlation showing 81.0% of ungrounded claims trace back to thin archival evidence (&amp;lt;600 chars).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Across the 57 atomic factual claims extracted from the 10 graves that had generated claims:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Value&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Factual claims extracted&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;57&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Unsupported before rewrite&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;21 (36.8%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Unsupported after rewrite&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;11 (19.3%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Net Hallucination Reduction&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;47.6% reduction in ungrounded claims&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Breaking down the 21 initial unsupported claims:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;13 of 21 claims (61.9%)&lt;/strong&gt; came directly from zero-evidence graves where the archive yielded no text: Yahoo Answers had 6 unsupported claims, Vine had 5, and Google Reader had 2. In the absence of evidence, Gemma drafted plausible tech details from memory; the fact-checker caught them and stripped them in the rewrite pass.&lt;/li&gt;
&lt;li&gt;Adding Picnik's 4 unsupported claims (which had only 237 characters recovered, well below the 600-character thin threshold) brings the total to &lt;strong&gt;17 of 21 claims (81.0%) originating from thin-evidence graves (&amp;lt;600 chars)&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;The remaining 4 unsupported claims (19.0%) occurred on rich-evidence graves (Grooveshark: 2, Pebble: 2) where the model introduced details not present in the recovered text slices.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To check the checker, I hand-verified 25 of its verdicts against known tech history (&lt;code&gt;spot_check.csv&lt;/code&gt;). I agreed with it on &lt;strong&gt;19 of 25&lt;/strong&gt; (76.0% agreement). The fact-checker caught false acquisition dates and fabricated feature claims, but occasionally allowed flowery metaphors ("welcomed curious souls") that a strict human editor would flag. A model checking a model still benefits from human audit.&lt;/p&gt;




&lt;h3&gt;
  
  
  Cause of Death: Model vs My Labels
&lt;/h3&gt;

&lt;p&gt;Continuing to the bottom of the evaluation report reveals the Cemetery Ground Truth Matrix:&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%2Flhejp3ui0ul7cab5r3mg.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%2Flhejp3ui0ul7cab5r3mg.png" alt=" " width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 13: The Cemetery Ground Truth Matrix tracking exhumed text depth, coroner causes of death, and verified claim counts across all 15 resting graves.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I labeled all 15 graves myself before looking at the model's verdicts:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Grave&lt;/th&gt;
&lt;th&gt;Text recovered&lt;/th&gt;
&lt;th&gt;Model Verdict&lt;/th&gt;
&lt;th&gt;My Hand Label&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Grooveshark&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;1,630 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;match&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Pebble&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;1,595 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;match&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AltaVista&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;543 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;match&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Picnik&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;237 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;match&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Vine&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;4 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Google Reader&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;GeoCities&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;acquired_then_shut_down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Adobe Flash Player&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;StumbleUpon&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Yahoo Answers&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ICQ&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;del.icio.us&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;abandoned&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AIM&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Google+&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Microsoft Zune&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 chars&lt;/td&gt;
&lt;td&gt;&lt;code&gt;unknown&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;shut_down_by_owner&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;abstained&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The model answered 4 times and was right 4 times. It abstained 11 times and was never confidently wrong.&lt;/p&gt;

&lt;p&gt;The reason for the 11 abstentions is straightforward: Archive.org rate limits (49 HTTP 429 responses and 12 timeouts across 68 attempts) prevented recovering text. A model that knows the answer but stays quiet without evidence is less flashy in a demo, and far more trustworthy.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The full interactive dashboard is live on Render: &lt;a href="https://graveyard-dead-software.onrender.com/benchmark" rel="noopener noreferrer"&gt;https://graveyard-dead-software.onrender.com/benchmark&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Grooveshark shut down as part of a copyright settlement. I filed that under &lt;code&gt;shut_down_by_owner&lt;/code&gt;, which is a judgment call).&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  What's Still Rough
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Thin graves:&lt;/strong&gt; 11 of 15 graves have little or no recovered text, so their eulogies are short and honest about it. Re-digging them with slower pacing is the next step.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Meaning of dates:&lt;/strong&gt; "Last archived capture" means the last good capture my pipeline could successfully exhume, not the literal hour the servers went dark.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Residual errors:&lt;/strong&gt; 19.3% of claims (11 of 57) were still unsupported after the rewrite. The fact-checker reduces hallucinations, but does not eliminate them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storage:&lt;/strong&gt; On Render's Free Web Service tier, disk storage is ephemeral: visitor-submitted graves disappear on redeploy; the 15 seed graves automatically restore from a bundled snapshot (&lt;code&gt;seed_bundle.zip&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replay expiry:&lt;/strong&gt; Browserbase recordings expire after about a week on the free tier, which is why permanent screen recording GIFs (such as Figure 5) and screenshots are archived in the repository.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Why Open Weights Matter Here
&lt;/h2&gt;

&lt;p&gt;This is a cemetery for software that died because someone else controlled it. Google Reader didn't die because it stopped working. It died because the company that owned it decided to switch it off.&lt;/p&gt;

&lt;p&gt;I called Gemma through a hosted API because it was convenient for a one-week build. But the weights are open, so the model that writes these eulogies can be downloaded and run on personal hardware. The pipeline has an Ollama provider setting (&lt;code&gt;LLM_PROVIDER=ollama&lt;/code&gt;), but I haven't tested it end to end yet.&lt;/p&gt;

&lt;p&gt;A memorial whose voice can be switched off by a third party isn't really a memorial. Open weights, open archives (the Internet Archive), and open code are what let this place outlive its builder.&lt;/p&gt;




&lt;h2&gt;
  
  
  My Agent Session
&lt;/h2&gt;

&lt;p&gt;I built this project pairing with Google Antigravity (Advanced Agentic AI pair programming) under strict operating rules: never fabricate a metric or claim, preserve documentation integrity, verify all assertions against raw database rows, and write reproducible audit tools.&lt;/p&gt;

&lt;p&gt;The complete pairing session history, operational charter, and verification audit trail are published in the repository:&lt;br&gt;
👉 &lt;strong&gt;&lt;a href="https://github.com/Pritam-mb/week4/blob/main/AUDIT_LOG.md" rel="noopener noreferrer"&gt;co-pilot Agent Session &amp;amp; Forensic Audit Dossier (AUDIT_LOG.md)&lt;/a&gt;&lt;/strong&gt; &lt;em&gt;(mirrored at &lt;a href="https://github.com/Pritam-mb/week4/blob/main/AGENT_SESSION.md" rel="noopener noreferrer"&gt;AGENT_SESSION.md&lt;/a&gt;)&lt;/em&gt;. Every metric can be recomputed with &lt;code&gt;python scripts/proof_pack.py&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Three moments from the agent pairing session worth opening:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Uncovering the Bot-Block Hallucination Trap:&lt;/strong&gt; Early in development, our test run generated a bizarre eulogy for Google Reader about "automated sentinels guarding blocked requests." While tests passed and HTTP statuses were green, the agent inspected the raw SQLite database row and caught the root cause: Archive.org's 603-character rate-limit HTML page had slipped through as authentic content. We immediately recognized our first benchmark was suspect and implemented the 4-layer defense.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Refusing to Falsify the Seed Graves:&lt;/strong&gt; When our audit script (&lt;code&gt;scripts/proof_pack.py&lt;/code&gt;) inspected all 68 fetch attempts across the 15 cemetery graves, it revealed that 49 attempts had hit Archive.org 429 rate limits, leaving 11 graves with 0 recovered characters. Rather than smoothing over the numbers or claiming 100% extraction success, the agent insisted on reporting the 11 abstentions with full forensic honesty.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Engineering the Stepper &amp;amp; Replay Demonstrations:&lt;/strong&gt; To prove end-to-end functionality without loading heavy dependencies, the agent converted our Browserbase CDP session recording into an optimized animated GIF (&lt;code&gt;live_screen_recording.gif&lt;/code&gt;) and generated a retro terminal stepper (&lt;code&gt;live_dig_stepper.gif&lt;/code&gt;) illustrating the five specialists in action.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;AI Disclosure:&lt;/strong&gt; Developed using Google Antigravity (Advanced Agentic Coding) for system architecture, pipeline orchestration, and empirical benchmarking. All data, traces, and code were verified against real host environments and Render deployments.&lt;/p&gt;




&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ghost in the Machine (Overall):&lt;/strong&gt; An end-to-end autonomous exhumation pipeline digging up dead software with real measured trade-offs, forensic honesty, and failure modes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gemma:&lt;/strong&gt; Every verdict, epitaph, eulogy, and fact-check comes from &lt;code&gt;gemma-4-26b-a4b-it&lt;/code&gt;. Every grave credits the model by name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Render:&lt;/strong&gt; Deployed from &lt;code&gt;render.yaml&lt;/code&gt;, with an automated &lt;code&gt;/health&lt;/code&gt; check and automatic restoration of the seed graves on fresh deploys.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Browserbase:&lt;/strong&gt; Cloud-browser exhumation of archived pages with screenshots and session replays (Session &lt;code&gt;d4521703-fcd3-4218-bf0b-fa558e9a89bb&lt;/code&gt;, with free tier recordings archived via permanent GIFs), a measured comparison against plain HTTP, and a live &lt;code&gt;/benchmark&lt;/code&gt; page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sentry:&lt;/strong&gt; GenAI agent tracing across every stage (&lt;code&gt;gen_ai.invoke_agent&lt;/code&gt; → &lt;code&gt;gen_ai.chat&lt;/code&gt; → &lt;code&gt;gen_ai.execute_tool&lt;/code&gt;), with tokens, latency, and failures, plus an honest account of what tracing could and couldn't catch.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  The Spirit of It
&lt;/h2&gt;

&lt;p&gt;On &lt;em&gt;Día de los Muertos&lt;/em&gt;, families build ofrendas so the dead can find their way home for a night. Marigolds light the path.&lt;/p&gt;

&lt;p&gt;Software has no ofrenda. When it dies, the work and community of thousands of people go dark with it, and the only marker is a 404.&lt;/p&gt;

&lt;p&gt;This is a small place to stop, read an honest record, and remember what someone made.&lt;/p&gt;

&lt;p&gt;Pick a tool you miss. Visit &lt;a href="https://graveyard-dead-software.onrender.com/" rel="noopener noreferrer"&gt;https://graveyard-dead-software.onrender.com/&lt;/a&gt;. Leave it a marigold.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;For Google Reader, Vine, GeoCities, and every tool that gave us something before the servers went dark.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>I Taught a Local 4B Model One CSV Chore. It Hasn't Been Called Since.</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sun, 25 Oct 2026 13:43:29 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/i-taught-a-local-4b-model-one-csv-chore-it-hasnt-been-called-since-3jgj</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/i-taught-a-local-4b-model-one-csv-chore-it-hasnt-been-called-since-3jgj</guid>
      <description>&lt;p&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19"&gt;Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Here is the number that matters. I ran a four-case drift benchmark against a naive positional cleanup script—the kind everybody writes at 11pm and then forgets about. The script produced &lt;strong&gt;three silently wrong outputs&lt;/strong&gt;. Molt produced &lt;strong&gt;zero&lt;/strong&gt;: it processed the clean files and refused the drifted ones before a single bad row reached disk.&lt;/p&gt;

&lt;p&gt;Steady-state execution takes about &lt;strong&gt;16 milliseconds&lt;/strong&gt; and makes &lt;strong&gt;zero model calls&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The model ran once, at the beginning, and hasn't been needed since. That is the entire point.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;From&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;evidence/benchmark.json:&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"naive_positional_script_baseline"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"case_count"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"silent_wrong_outputs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"drift_cases_accepted_without_validation"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"molt_drift_measurement"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"case_count"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"silent_wrong_outputs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"blocked_drift_cases"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"runtime_model_calls"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"mean_latency_ms"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;3.968&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What I Built: The Chore
&lt;/h2&gt;

&lt;p&gt;Every month the same expense export lands in the same folder with the same four problems: whitespace on merchant names, three different date formats, amounts formatted as &lt;code&gt;"$1,240.00"&lt;/code&gt; strings, and a category column that uses &lt;code&gt;Food&lt;/code&gt;, &lt;code&gt;food&lt;/code&gt;, and &lt;code&gt;F&amp;amp;B&lt;/code&gt; interchangeably.&lt;/p&gt;

&lt;p&gt;Twenty minutes of repetitive manual drudgery.&lt;/p&gt;

&lt;p&gt;The obvious 2026 fix is to pipe the file through an LLM. I didn't want to, for three reasons:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Per-file cost:&lt;/strong&gt; It costs money on every run, forever.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Non-deterministic:&lt;/strong&gt; The same file can produce different outputs twice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quiet failure:&lt;/strong&gt; A model that mis-parses one date out of four hundred hands you a clean-looking CSV with a wrong number in it, and you only find out at quarter close.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So I inverted it: &lt;strong&gt;use the model as a compiler, not a runtime.&lt;/strong&gt;&lt;/p&gt;



&lt;p&gt;&lt;strong&gt;Video&lt;/strong&gt;   &lt;iframe src="https://www.youtube.com/embed/LFMgahkkv_k" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;
&lt;h2&gt;
  
  
  Compile Once, Run Forever
&lt;/h2&gt;

&lt;p&gt;Molt splits the job into two phases that never touch each other:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Phase one (once):&lt;/strong&gt; A local Gemma model (&lt;code&gt;gemma3:4b&lt;/code&gt; via Ollama) looks at a &lt;em&gt;masked schema profile&lt;/em&gt;—column names and inferred types, never a single raw row—and emits a JSON recipe constrained to a closed operation allowlist: &lt;code&gt;trim&lt;/code&gt;, &lt;code&gt;parse_date&lt;/code&gt;, &lt;code&gt;parse_decimal&lt;/code&gt;, &lt;code&gt;map_values&lt;/code&gt;, &lt;code&gt;split_column&lt;/code&gt;, &lt;code&gt;select_columns&lt;/code&gt;, &lt;code&gt;dedupe&lt;/code&gt;. It cannot emit Python. It cannot emit shell. If it proposes an op that isn't on the list, the recipe is rejected before anything runs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Verifier Gate:&lt;/strong&gt; That recipe then has to survive an independent verifier—golden fixtures written by hand, row-count invariants, null-injection checks, and an idempotence test (&lt;code&gt;apply(apply(x)) == apply(x)&lt;/code&gt;)—and then it has to survive an explicit human approval click.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Phase two (forever):&lt;/strong&gt; Approved recipes execute in pure Python. No model, no network, no tokens, no variance. Same input, same output, every time.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
  
  
  MOLT: COMPILE ONCE, RUN FOREVER
&lt;/h2&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt; [ PHASE 1: COMPILE ONCE ]                                      [ VERIFICATION &amp;amp; APPROVAL GATE ]
 -------------------------                                      --------------------------------
  Raw CSV Export (in/)                                            Candidate Recipe v1 (JSON)
           │                                                                 │
           ▼                                                                 ▼
 ┌──────────────────────┐   Masked Profile (Headers/Dtypes)    ┌────────────────────────────────────┐
 │  CSV Profiler        │ ───────────────────────────────────▶ │  Independent Verifier Gate         │
 │  (molt/application)  │  *ZERO raw cell rows or PII*         │  • Closed 9-Op Allowlist Check     │
 └──────────────────────┘                                      │  • Golden Input/Output Fixtures    │
                                                               │  • Row-Count &amp;amp; Null Invariants     │
 ┌──────────────────────┐                                      │  • Idempotence: f(f(x)) == f(x)    │
 │  Local Gemma 3:4b    │ ───────────────────────────────────▶ └─────────────────┬──────────────────┘
 │  (Ollama via HTTP)   │  Constrained JSON Recipe DSL                           │
 └──────────────────────┘  *Cannot emit Python or shell*                         ▼ (Pass: 6/6)
                                                               ┌────────────────────────────────────┐
                                                               │  Explicit Human Approval           │
                                                               │  [Accept &amp;amp; Activate Recipe v1]     │
                                                               └─────────────────┬──────────────────┘
                                                                                 │
 ════════════════════════════════════════════════════════════════════════════════╪════════════════════
                                                                                 │
 [ PHASE 2: RUN FOREVER (DETERMINISTIC STEADY STATE) ]                           ▼
 -----------------------------------------------------                 Active Recipe v1 Store
  New Incoming File (in/)                                                        │
           │                                                                     │
           ▼                                                                     │
 ┌──────────────────────────────────────────┐                                    │
 │  Contract Drift Check (16ms)             │ ◀──────────────────────────────────┘
 │  • Required columns match?               │
 └─────────────────────┬────────────────────┘
                       │
         ┌─────────────┴─────────────┐
         │                           │
  [ Compatible: PASS ]        [ Drift Detected: FAIL ]
         │                           │
         ▼                           ▼
 ┌───────────────────────────┐ ┌───────────────────────────┐
 │ Pure Python Engine        │ │ Quarantine &amp;amp; Block (16ms) │
 │ (molt/core.py)            │ │ • Moved to quarantine/    │
 │ • Reuses approved recipe  │ │ • SHA-256 Fingerprinted   │
 │ • ~16ms execution latency │ │ • Audit bead turns RED    │
 │ • 0 RUNTIME MODEL CALLS   │ └─────────────┬─────────────┘
 └─────────────┬─────────────┘               │
               │                             │
 ┌─────────────▼─────────────┐               │ [ OUT-OF-BAND REPAIR FLOW ]
 │ Temporal Worker Checkpoint│               ▼
 │ • Durable state barrier   │ ┌────────────────────────────────────────────────────────┐
 │ • Crash replay resilience │ │ Mastra Repair Sidecar (:4112 / Groq openai/gpt-oss)    │
 └─────────────┬─────────────┘ │ • Out-of-band TypeScript agent receives masked diff    │
               │               │ • Proposes candidate Recipe v2 (stored as INACTIVE)   │
 ┌─────────────▼─────────────┐ └────────────────────────────┬───────────────────────────┘
 │ Atomic Write to done/     │                              │
 │ • Zero duplicate rows     │                              ▼
 │ • Graph: +1 Call Avoided  │ ┌────────────────────────────────────────────────────────┐
 └───────────────────────────┘ │ Verifier Regression (6/6) ──▶ Human Accepts Recipe v2 │
                               └────────────────────────────────────────────────────────┘

 ═════════════════════════════════════════════════════════════════════════════════════════════════════
 [ CROSS-CUTTING PRIVACY &amp;amp; OBSERVABILITY BOUNDARY ]
 ──────────────────────────────────────────────────
  ┌──────────────────────────────────────────────┐  ┌───────────────────────────────────────────────┐
  │ Sentry 9-Stage Agent Tracing                 │  │ TabPFN Local CPU Anomaly Scorer               │
  │ • 9 Spans: profile ──▶ verify ──▶ execute    │  │ • 1,500 Synthetic Expense Holdout Rows        │
  │ • Strict Allowlist: _SAFE_ATTRIBUTE_KEYS     │  │ • 94.55% Precision / 72.22% Recall            │
  │ • Scrub Hook: send_default_pii=False         │  │ • Strictly Advisory: Never Alters Source Bytes│
  │ • Zero raw rows or secrets sent to APM       │  │ • Local CPU only (telemetry_enabled: false)   │
  └──────────────────────────────────────────────┘  └───────────────────────────────────────────────┘
*Figure 1: Raw data stays inside the local deterministic runtime. Only masked metadata ever reaches a model.*

---
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h2&gt;
  
  
  The Lazy Payoff
&lt;/h2&gt;

&lt;p&gt;Drop a file in &lt;code&gt;in/&lt;/code&gt;. Molt fingerprints its schema, matches the approved recipe, runs it, writes the result atomically to &lt;code&gt;done/&lt;/code&gt;, and logs the run. &lt;/p&gt;

&lt;p&gt;You weren't there. You don't need to have been there.&lt;/p&gt;

&lt;p&gt;That's the sloth version of automation: expend energy once, deliberately, on the part that actually needs thinking, and then coast on near-zero energy indefinitely. The counter on the dashboard that reads &lt;em&gt;model calls avoided&lt;/em&gt; is really a counter of mornings I didn't spend babysitting a data script.&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%2F1w9jzu0339la32c4zowf.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%2F1w9jzu0339la32c4zowf.png" alt="Molt Bento Dashboard" width="800" height="2120"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 2: Run beads, the calls-avoided ledger, the seven-stage lifecycle stepper, and the active recipe under review.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  When the Data Changes: The Complete Drift &amp;amp; Repair Flow
&lt;/h2&gt;

&lt;p&gt;Deterministic automation has one classic failure mode: the vendor changes the export, your script keeps running, and it silently produces garbage. This is the exact problem Molt was built to solve.&lt;/p&gt;

&lt;p&gt;Here is the exact step-by-step visual lifecycle of what happens when data drifts:&lt;/p&gt;
&lt;h3&gt;
  
  
  1. Drift Detected, Run Blocked in 16ms
&lt;/h3&gt;

&lt;p&gt;A file arrived missing the &lt;code&gt;notes&lt;/code&gt; column. Molt did not guess. It did not impute. It did not ask a model to invent a value. A pure-Python contract check caught it in 16ms, moved the file to &lt;code&gt;quarantine/&lt;/code&gt; with a SHA-256 fingerprint, and turned the run bead permanently red.&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%2Fvqi1l66viqhybyqyypj0.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%2Fvqi1l66viqhybyqyypj0.png" alt="Why Molt blocked this file" width="800" height="430"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 3: Run 2 tripped REQUIRED_COLUMN_MISSING. The timeline highlights the red audit bead, the status panel details the error, and the out-of-band "Suggest Mastra repair" button is revealed.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The evidence diff page shows what was expected, what arrived, and the exact contract rule that fired—structural metadata only, zero raw financial values rendered:&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%2Fkpfkdcfgi5pevth9nyoz.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%2Fkpfkdcfgi5pevth9nyoz.png" alt="Safe Evidence Diff for Blocked Drift" width="800" height="430"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 4: The Safe Evidence Diff report for the blocked run. Displays observed headers vs. required contract, audit decision trace, and approved recipe limits.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  2. Mastra Agent Proposes, Regression Tests Verify
&lt;/h3&gt;

&lt;p&gt;Repair happens &lt;strong&gt;out of band&lt;/strong&gt;, which is the most critical design decision in the project:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The operator clicks &lt;strong&gt;&lt;code&gt;[Suggest Mastra repair]&lt;/code&gt;&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;Mastra&lt;/strong&gt; agent runs as an isolated TypeScript service on its own port (&lt;code&gt;mastra-repair/&lt;/code&gt; on port 4112).&lt;/li&gt;
&lt;li&gt;It receives the active recipe, the masked profile, and the structural error—&lt;strong&gt;zero customer PII or raw CSV rows&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Powered by Groq (&lt;code&gt;openai/gpt-oss-120b&lt;/code&gt;), Mastra proposes a candidate recipe removing the obsolete &lt;code&gt;notes&lt;/code&gt; requirement while preserving every formatting rule.&lt;/li&gt;
&lt;li&gt;The candidate is stored as an inactive draft, advancing the lifecycle stepper: &lt;code&gt;1. Drift blocked&lt;/code&gt; -&amp;gt; &lt;code&gt;2. Ask Mastra&lt;/code&gt; -&amp;gt; &lt;code&gt;3. Candidate stored&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&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%2Fpnqj74q38kevqeiaot9i.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%2Fpnqj74q38kevqeiaot9i.png" alt="Mastra repair candidate stored and awaiting tests" width="642" height="626"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 5: Mastra proposed a repair. The candidate is stored separately and remains completely inactive until independent regression tests pass and a human explicitly approves.&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The operator clicks &lt;strong&gt;&lt;code&gt;[Run repair tests]&lt;/code&gt;&lt;/strong&gt;. Molt ignores the agent's opinion of its own work and executes the full regression suite: &lt;strong&gt;6/6 checks passed&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3&gt;
  
  
  3. Human Operator Reviews &amp;amp; Accepts the Repair
&lt;/h3&gt;

&lt;p&gt;Molt &lt;strong&gt;never auto-promotes&lt;/strong&gt; an unreviewed candidate. The operator reviews the four-line JSON diff in the dashboard:&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Candidate Recipe v2 Review]
- Required columns: ["date", "merchant", "amount", "category", "notes"]
+ Required columns: ["date", "merchant", "amount", "category"]
Status: VERIFIED (6/6 checks passed). Waiting for human acceptance.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The operator clicks &lt;strong&gt;&lt;code&gt;[Accept repair]&lt;/code&gt;&lt;/strong&gt;. The candidate is promoted to &lt;strong&gt;Recipe v2 (Active)&lt;/strong&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%2Fvwl9qjj9wlkmg2zqhq1x.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%2Fvwl9qjj9wlkmg2zqhq1x.png" alt="Repair approved and activated" width="642" height="740"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 6: The repair is activated. The banner confirms: "APPROVED: Repair was activated. New runs now process with the repaired recipe."&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  4. Quarantined File Re-executes Green (Zero Model Calls)
&lt;/h3&gt;

&lt;p&gt;With Recipe v2 active, the quarantined file re-runs deterministically:&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%2F8m2h6zpkfb2o80gz75ua.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%2F8m2h6zpkfb2o80gz75ua.png" alt="Run history and Run 5 succeeded" width="800" height="430"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Figure 7: Run 5 succeeds under Recipe v2. Six rows written atomically, latency ~16ms, and exactly 0 runtime model calls.&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Timeline Update:&lt;/strong&gt; Run 5 turns &lt;strong&gt;green&lt;/strong&gt; (&lt;code&gt;PASS: SUCCEEDED&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Execution Metrics:&lt;/strong&gt; 6 rows processed, latency 16ms, &lt;strong&gt;0 runtime LLM calls&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Calls Avoided Chart:&lt;/strong&gt; The graph updates in real time, recording that steady-state production remains completely free of repeated model inference.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An LLM participated in fixing the pipeline. &lt;strong&gt;An LLM never touched the data.&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  How I Built It: Where the Local Model Actually Failed
&lt;/h2&gt;

&lt;p&gt;I tested &lt;code&gt;gemma3:4b&lt;/code&gt; on a difficulty ladder, five trials per rung, because "it worked on my demo" is not engineering evidence.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Task Difficulty&lt;/th&gt;
&lt;th&gt;First Request Pass Rate&lt;/th&gt;
&lt;th&gt;With Configured Retries&lt;/th&gt;
&lt;th&gt;Verification Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Trim merchant text&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;Verified &amp;amp; Passed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Trim + parse dates&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;4/5&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;Verified &amp;amp; Passed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Trim + dates + decimals&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;3/5&lt;/td&gt;
&lt;td&gt;4/5&lt;/td&gt;
&lt;td&gt;Verified &amp;amp; Passed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Full 6-operation task&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;0/5&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;0/5&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Blocked by Verifier&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Zero out of five.&lt;/strong&gt; On the full task—renames, regex split, date normalisation, currency parsing, category mapping, dedupe—a 4B model running on a laptop simply could not hold all six rules in context at once.&lt;/p&gt;

&lt;p&gt;The failure mode is the one that should frighten you: in one run, Gemma's natural-language summary confidently stated that it had parsed the amount column. Its actual executable JSON omitted the decimal transform entirely. &lt;strong&gt;The model told me it did something it had not done.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In an ungated agent pipeline, that recipe ships and your amounts remain text strings. In Molt, the verifier rejected it, and &lt;strong&gt;not one invalid recipe ever reached production across the whole ladder&lt;/strong&gt;. The architecture absorbed the model's weakness instead of inheriting it.&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;From&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;evidence/gemma-rung&lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="err"&gt;-rejected-candidate.json:&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"recipe"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Trim, Normalize Date, Parse Decimal"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Trims whitespace from merchant, normalizes date to YYYY-MM-DD, and parses amount to two decimal places."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"operations"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"trim"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"columns"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
          &lt;/span&gt;&lt;span class="s2"&gt;"merchant"&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"rung"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"verification"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"FAIL"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"failed_checks"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"failed_check_codes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="s2"&gt;"golden_output"&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;&lt;em&gt;Look at the operations array: it contains ONLY &lt;code&gt;trim&lt;/code&gt;. The model claimed it parsed date and amount in its natural-language description, but completely omitted those operations from the executable JSON. Molt's verifier caught the discrepancy immediately and failed the golden check before anything could execute.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;That's the result I'm proudest of, and it only exists because I assumed from line one that the model would lie to me.&lt;/p&gt;

&lt;p&gt;Evidence: &lt;a href="https://github.com/Pritam-mb/week3/blob/main/evidence/gemma-full-task-followup.json" rel="noopener noreferrer"&gt;Full evaluation evidence&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week3/blob/main/evidence/gemma-rung3-rejected-candidate.json" rel="noopener noreferrer"&gt;Rejected candidate&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  But Is the Verifier Any Good? Mutation Testing
&lt;/h2&gt;

&lt;p&gt;A verifier that never catches anything is just ceremony. So I mutated 20 known-good recipes on purpose—inverted dedupe keys, dropped transforms, unmapped categories—and measured what survived.&lt;/p&gt;

&lt;p&gt;The initial suite caught &lt;strong&gt;18 of 20&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The two survivors were real gaps: an unmapped category policy and a dedupe key edge case. I wrote two targeted fixtures, re-ran the identical 20 mutations, and got &lt;strong&gt;20/20 (100% catch rate)&lt;/strong&gt;, with the valid recipe still passing 11/11 checks cleanly.&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;From&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;evidence/verifier-catch-rate-after.json:&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"before_summary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"total"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"caught"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;18&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"missed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"misses"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="s2"&gt;"dedupe_wrong_column"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="s2"&gt;"preserve_unknown_policy"&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"catch_rate"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;0.90&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"after_summary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"total"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"caught"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"missed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"catch_rate"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;1.00&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"correct_recipe"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"verification_status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"checks_passed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"11/11"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"checks_failed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Evidence: &lt;a href="https://github.com/Pritam-mb/week3/blob/main/evidence/verifier-catch-rate-after.json" rel="noopener noreferrer"&gt;Mutation test evidence&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Why Open Innovation Mattered Here
&lt;/h2&gt;

&lt;p&gt;This project is only possible with open weights and open frameworks, and not for ideological reasons:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The data can't leave:&lt;/strong&gt; Expense lines, payroll, invoice detail—these don't get posted to a third-party cloud API because a blog post said agents are cool. Gemma runs locally with zero network egress. The privacy boundary isn't a policy promise in a Terms of Service; it's the physical fact that the process makes no network calls.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;I could measure the model's limits:&lt;/strong&gt; Running locally and unmetered, I ran the ladder 20+ times, watched it fail, and designed the verifier around the observed failures. With a metered closed API I'd have run it three times, seen it mostly work, and shipped the silent-corruption bug.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The artifact is readable:&lt;/strong&gt; An open model compiling to declarative JSON gives me something I can diff, review, commit to Git, and regression-test. A closed agent gives me a vibe and an invoice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It's swappable:&lt;/strong&gt; Gemma is a dependency, not a foundation. The allowlist and the verifier are mine. A better 4B model next month is a single config change, and the fact that it's a config change is itself the argument.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Marginal cost is genuinely zero:&lt;/strong&gt; The recurring chore has no recurring bill.&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;
  
  
  What Molt Can't Do (Explicit Limitations)
&lt;/h2&gt;

&lt;p&gt;Being straight about this, because the post would be dishonest otherwise:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Verification is evidence, not mathematical proof:&lt;/strong&gt; My fixtures cover the input classes I imagined; a sufficiently novel or malicious file can still slip through a passing suite.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The op allowlist is deliberately narrow:&lt;/strong&gt; Anything outside those nine operations needs new code, not a new prompt.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A 4B local model cannot compile a six-rule recipe in one shot:&lt;/strong&gt; Complex chores need either a larger local model (e.g. 14B/32B) or decomposition into staged sub-recipes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TabPFN is strictly advisory:&lt;/strong&gt; Evaluated on synthetic data, it flags statistical outliers but has no authority to alter records or block execution.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Molt is not autonomous by design:&lt;/strong&gt; A human promotes every recipe version. That is a deliberate ceiling on how lazy it will ever let you be.&lt;/li&gt;
&lt;/ul&gt;


&lt;h2&gt;
  
  
  Demo: Try It in 30 Seconds
&lt;/h2&gt;

&lt;p&gt;No API key, no Ollama install, and no network connection required.&lt;/p&gt;
&lt;h3&gt;
  
  
  1. Instant Offline Demo
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python &lt;span class="nt"&gt;-m&lt;/span&gt; molt demo &lt;span class="nt"&gt;--offline&lt;/span&gt; &lt;span class="nt"&gt;--approve&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;&lt;em&gt;Four benchmark cases: two clean batches processed, two drifted batches halted, zero execution model calls.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  2. Live Local Dashboard
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python &lt;span class="nt"&gt;-m&lt;/span&gt; molt &lt;span class="nt"&gt;--state-dir&lt;/span&gt; workspace serve &lt;span class="nt"&gt;--host&lt;/span&gt; 127.0.0.1 &lt;span class="nt"&gt;--port&lt;/span&gt; 8765
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Open &lt;code&gt;http://127.0.0.1:8765/&lt;/code&gt; in your browser.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 8: Responsive bento layout check at 390px width with 0px horizontal overflow.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Code: Under the Hood
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Code:&lt;/strong&gt; &lt;/p&gt;
&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/week3" rel="noopener noreferrer"&gt;
        week3
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;p&gt;
  &lt;a rel="noopener noreferrer nofollow" href="https://raw.githubusercontent.com/Pritam-mb/week3/main/evidence/hero-banner.png"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FPritam-mb%2Fweek3%2Fmain%2Fevidence%2Fhero-banner.png" alt="Molt - 0 model calls at runtime. It stops when the data changes." width="100%"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
  &lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19" rel="nofollow"&gt;&lt;img src="https://camo.githubusercontent.com/fe333dfcdb494d5e17e10d9b8085831fa9a63ab3c772fdc857a3c15b1e3e662a/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4861636b746f626572666573742d5765656b25323033253230536c6f772532302532362532305374656164792d3130313832373f7374796c653d666f722d7468652d6261646765266c6f676f3d6861636b746f62657266657374" alt="Hacktoberfest Week 3"&gt;&lt;/a&gt;
  &lt;a rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/e4d90793a7a8a7dc0a59944095510b17c0a33c6951761f9b6512b71381c5f9eb/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f507974686f6e2d332e31312b2d3337373641423f7374796c653d666f722d7468652d6261646765266c6f676f3d707974686f6e266c6f676f436f6c6f723d7768697465"&gt;&lt;img src="https://camo.githubusercontent.com/e4d90793a7a8a7dc0a59944095510b17c0a33c6951761f9b6512b71381c5f9eb/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f507974686f6e2d332e31312b2d3337373641423f7374796c653d666f722d7468652d6261646765266c6f676f3d707974686f6e266c6f676f436f6c6f723d7768697465" alt="Python"&gt;&lt;/a&gt;
  &lt;a rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/207087548e4f2a1fa00f59e5982afb0ee594686a4d836976ff7a54717931ae7b/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f47656d6d612d3325334134622d4646353732323f7374796c653d666f722d7468652d6261646765266c6f676f3d676f6f676c65"&gt;&lt;img src="https://camo.githubusercontent.com/207087548e4f2a1fa00f59e5982afb0ee594686a4d836976ff7a54717931ae7b/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f47656d6d612d3325334134622d4646353732323f7374796c653d666f722d7468652d6261646765266c6f676f3d676f6f676c65" alt="Gemma"&gt;&lt;/a&gt;
  &lt;a rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/6b15b9064adfe64d7df08e1f0546d8f9ea1e274adf5e02871cbaf6497a445d36/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4d61737472612d54797065536372697074253230536964656361722d707572706c653f7374796c653d666f722d7468652d6261646765"&gt;&lt;img src="https://camo.githubusercontent.com/6b15b9064adfe64d7df08e1f0546d8f9ea1e274adf5e02871cbaf6497a445d36/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4d61737472612d54797065536372697074253230536964656361722d707572706c653f7374796c653d666f722d7468652d6261646765" alt="Mastra"&gt;&lt;/a&gt;
  &lt;a rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/3e7aaf2fa8f4c3dbc1e74ecb237d336d4d2194c6ecbfa27be9fd9f6867ad662f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f54657374732d38382532305061737365642d3232633535653f7374796c653d666f722d7468652d6261646765"&gt;&lt;img src="https://camo.githubusercontent.com/3e7aaf2fa8f4c3dbc1e74ecb237d336d4d2194c6ecbfa27be9fd9f6867ad662f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f54657374732d38382532305061737365642d3232633535653f7374796c653d666f722d7468652d6261646765" alt="Tests"&gt;&lt;/a&gt;
  &lt;a rel="noopener noreferrer nofollow" href="https://camo.githubusercontent.com/40d799e2dd73ccbc5eab302bae7a233bc96a51da6392360a4e2e1599e6dac1dd/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f52756e74696d652532304c4c4d25323043616c6c732d302d3030444338323f7374796c653d666f722d7468652d6261646765"&gt;&lt;img src="https://camo.githubusercontent.com/40d799e2dd73ccbc5eab302bae7a233bc96a51da6392360a4e2e1599e6dac1dd/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f52756e74696d652532304c4c4d25323043616c6c732d302d3030444338323f7374796c653d666f722d7468652d6261646765" alt="Runtime Calls"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h3 class="heading-element"&gt;
  Compile once. Verify against truth. Reuse forever without repeated inference
&lt;/h3&gt;
&lt;/div&gt;

&lt;p&gt;
  &lt;a href="https://github.com/Pritam-mb/week3/raw/main/evidence/molt-presentation.mp4" rel="noopener noreferrer"&gt;&lt;b&gt;🎬 Watch Digital Video (MP4)&lt;/b&gt;&lt;/a&gt; &amp;nbsp;•&amp;nbsp;
  &lt;a href="https://raw.githubusercontent.com/Pritam-mb/week3/main/evidence/molt-presentation.gif" rel="nofollow noopener noreferrer"&gt;&lt;b&gt;⚡ View Animated Explainer (GIF)&lt;/b&gt;&lt;/a&gt;
&lt;/p&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;What is Molt?&lt;/h2&gt;

&lt;/div&gt;

&lt;p&gt;Every month the same expense export lands with the same problems: whitespace on merchant names, three different date formats, amounts formatted as &lt;code&gt;"$1,240.00"&lt;/code&gt; strings, and inconsistent categories.&lt;/p&gt;

&lt;p&gt;Piping recurring CSV files through an LLM is expensive, non-deterministic, and prone to silent data corruption. &lt;strong&gt;Molt inverts the pattern: use the model as an offline compiler, never a production runtime.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Phase 1 (Compile Once):&lt;/strong&gt; A local Gemma model (&lt;code&gt;gemma3:4b&lt;/code&gt; via Ollama) inspects a masked schema profile (column names and types only, zero raw cell rows) and emits a recipe constrained to a closed 9-operation allowlist.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Verifier Gate:&lt;/strong&gt; Independent golden fixtures, null-injection checks, row-count invariants, and idempotence tests (&lt;code&gt;apply(apply(x)) == apply(x)&lt;/code&gt;) validate the candidate before human approval.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Phase 2 (Run Forever):&lt;/strong&gt; Approved recipes execute in…&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/week3" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;The contract gate is the heart of the safety model, and it is forty lines of boring Python rather than anything clever:&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;check_contract&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;recipe&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;Any&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;list&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nb"&gt;str&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;recipe&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input_contract&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;required_columns&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;missing&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;required&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;missing&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;raise&lt;/span&gt; &lt;span class="nc"&gt;MoltError&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
            &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;REQUIRED_COLUMN_MISSING&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Missing required column(s): &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;, &lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;missing&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;.&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="n"&gt;details&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;missing&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;missing&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;expected&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;required&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;observed&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;
        &lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;recipe&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input_contract&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;allow_extra_columns&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="ow"&gt;is&lt;/span&gt; &lt;span class="bp"&gt;False&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="n"&gt;extras&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;headers&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;required&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;extras&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;raise&lt;/span&gt; &lt;span class="nc"&gt;MoltError&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
                &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;INPUT_TYPE_MISMATCH&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Unexpected column(s): &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;, &lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;extras&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;.&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Around it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://github.com/Pritam-mb/week3/blob/main/molt/core.py" rel="noopener noreferrer"&gt;&lt;code&gt;molt/core.py&lt;/code&gt;&lt;/a&gt;: The deterministic execution engine, checkpoint ledger, and atomic writes.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/Pritam-mb/week3/blob/main/molt/application.py" rel="noopener noreferrer"&gt;&lt;code&gt;molt/application.py&lt;/code&gt;&lt;/a&gt;: Lifecycle state machine, verification gates, and human approval boundaries.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/Pritam-mb/week3/blob/main/molt/ollama.py" rel="noopener noreferrer"&gt;&lt;code&gt;molt/ollama.py&lt;/code&gt;&lt;/a&gt;: Constrained local Gemma/Ollama recipe compilation client.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/Pritam-mb/week3/blob/main/molt/temporal.py" rel="noopener noreferrer"&gt;&lt;code&gt;molt/temporal.py&lt;/code&gt;&lt;/a&gt;: Durable Temporal workflow definitions and activity worker.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/Pritam-mb/week3/tree/main/mastra-repair" rel="noopener noreferrer"&gt;&lt;code&gt;mastra-repair/&lt;/code&gt;&lt;/a&gt;: Isolated TypeScript microservice for out-of-band repair proposals.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/Pritam-mb/week3/tree/main/molt/web" rel="noopener noreferrer"&gt;&lt;code&gt;molt/web/&lt;/code&gt;&lt;/a&gt;: Obsidian graphite bento dashboard with zero external CDN dependencies.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;tests/&lt;/code&gt;: 79 Python unit/integration tests and 9 Node.js dashboard/diff tests.&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  Three Integrations With Full In-Post JSON Evidence
&lt;/h3&gt;

&lt;p&gt;Rather than asking you to blindly trust marketing claims, here is the exact machine-verified evidence for our partner integrations:&lt;/p&gt;

&lt;h4&gt;
  
  
  1. Temporal: Crash Recovery &amp;amp; Durable Checkpointing
&lt;/h4&gt;

&lt;p&gt;Steady-state execution runs inside a durable Temporal workflow. We injected process kills mid-flight (&lt;code&gt;MOLT_CRASH_AT=1&lt;/code&gt; killing both worker and server). Upon restart, Temporal picked up from step 1's saved checkpoint without duplicate writes and without making any model calls:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;From&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;evidence/temporal-crash-recovery.json:&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"COMPLETE"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"workflow"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"result_status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"SUCCEEDED"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"temporal_outcome"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"completed"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"llm_calls"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"rows_read"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"rows_written"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"failure_injection"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"mode"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"MOLT_CRASH_AT"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"after_step"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"activity_attempts"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"checkpoint_created"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"checkpoint_resumed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"claim_boundary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Real local Temporal server and worker workflow; one injected activity failure and idempotent retry."&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  2. TabPFN: Local Advisory Anomaly Detection
&lt;/h4&gt;

&lt;p&gt;Evaluated locally on CPU across 1,500 synthetic expense rows (1,200 training rows, 300 held-out test rows). It flags statistical schema spikes without modifying a single byte of source data:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;From&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;evidence/tabpfn-accuracy.json:&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"task"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"supervised_binary_classification"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"dataset"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"rows"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1500&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"train_rows"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1200&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"held_out_rows"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;300&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"holdout_metrics"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"confusion_matrix"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"true_positives"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;52&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"false_positives"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"true_negatives"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;225&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"false_negatives"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"precision"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;0.9455&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"recall"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;0.7222&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"accuracy"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;0.9233&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"source_rows_changed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"advisory_only"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;Why is 72% recall acceptable?&lt;/em&gt; Because TabPFN is strictly advisory and non-blocking—it is an extra signal for operator triage, while the deterministic Python contract gate is what actually guarantees zero corrupt rows reach disk.&lt;/p&gt;

&lt;h4&gt;
  
  
  3. Sentry: 9-Stage Distributed Tracing &amp;amp; Strict Redaction Allowlist
&lt;/h4&gt;

&lt;p&gt;Molt instruments all &lt;strong&gt;nine workflow lifecycle stages&lt;/strong&gt; in &lt;a href="https://github.com/Pritam-mb/week3/blob/main/molt/application.py" rel="noopener noreferrer"&gt;&lt;code&gt;molt/application.py&lt;/code&gt;&lt;/a&gt; using an allowlist-based scrub boundary in &lt;a href="https://github.com/Pritam-mb/week3/blob/main/molt/telemetry.py" rel="noopener noreferrer"&gt;&lt;code&gt;molt/telemetry.py&lt;/code&gt;&lt;/a&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;The 9 Lifecycle Tracing Spans:
1. automation.profile_csv        (profiles header names and inferred dtypes)
2. tabpfn.score_rows             (computes advisory outlier probabilities)
3. recipe.validate_operations    (enforces closed 9-op allowlist)
4. recipe.compile_gemma          (local Ollama compiler envelope check)
5. recipe.verify_examples        (runs golden fixture regression tests)
6. recipe.approve_version        (records explicit operator promotion)
7. repair.propose                (dispatches masked schema to Mastra sidecar)
8. automation.check_drift        (pure Python contract check in 16ms)
9. automation.execute_approved_recipe (deterministic Python transform)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;The Redaction Proof (Why It Is Safe to Upload):&lt;/strong&gt; To guarantee that confidential payroll data, invoices, customer PII, or internal file paths never leave your infrastructure, &lt;code&gt;molt/telemetry.py&lt;/code&gt; enforces a strict two-tier scrub boundary:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Strict Key Allowlist:&lt;/strong&gt; Attributes are dropped by default unless explicitly included in the safe set:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# From molt/telemetry.py:
&lt;/span&gt;&lt;span class="n"&gt;_SAFE_ATTRIBUTE_KEYS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;attempt&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;checks_passed&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;checks_total&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;column_count&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input_bytes&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input_rows&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;model_calls&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;output_rows&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="n"&gt;_SENSITIVE_KEY_PARTS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;content&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;csv&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;file&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;path&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;prompt&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;response&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;row&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;secret&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;token&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;value&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Payload Scrub Hook:&lt;/strong&gt; The Sentry SDK initializes with &lt;code&gt;send_default_pii=False&lt;/code&gt; and hooks &lt;code&gt;before_send&lt;/code&gt; and &lt;code&gt;before_send_transaction&lt;/code&gt; to sanitize payloads before transmission:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# Verified in tests/test_telemetry.py:
&lt;/span&gt;&lt;span class="n"&gt;scrubbed&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;before_send&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;message&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;raw&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;request&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;url&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://private/path&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ok&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;count&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;data&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;prompt&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;raw prompt&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input_rows&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;free_text&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;raw csv cell value: $1,240.00&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt;
&lt;span class="c1"&gt;# Result verified by unit test:
&lt;/span&gt;&lt;span class="k"&gt;assert&lt;/span&gt; &lt;span class="n"&gt;scrubbed&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ok&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;count&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;data&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;input_rows&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt;&lt;span class="p"&gt;}}&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&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%2Fj3vdbwjrs41zy42g5bnm.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%2Fj3vdbwjrs41zy42g5bnm.png" alt=" " width="800" height="489"&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%2Fncxpaed60pu9ebo7dr46.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%2Fncxpaed60pu9ebo7dr46.png" alt=" " width="800" height="477"&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%2F8ob2cxof18rv127fabag.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%2F8ob2cxof18rv127fabag.png" alt=" " width="799" height="476"&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%2Fc0si6ts54o41u48s0sln.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%2Fc0si6ts54o41u48s0sln.png" alt=" " width="799" height="482"&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%2Fx3pb2xkz3tsvmftsjqb0.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%2Fx3pb2xkz3tsvmftsjqb0.png" alt=" " width="800" height="493"&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%2Fven14lgchrah7yp961mn.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%2Fven14lgchrah7yp961mn.png" alt=" " width="800" height="472"&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%2Fzwt60iek9w6g9yw9lay1.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%2Fzwt60iek9w6g9yw9lay1.png" alt=" " width="800" height="458"&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%2Fnqx979gfsgaxagucmato.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%2Fnqx979gfsgaxagucmato.png" alt=" " width="799" height="472"&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%2Fvnsj6ich0bosdc556ijc.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%2Fvnsj6ich0bosdc556ijc.png" alt=" " width="799" height="462"&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%2Fe5f58o76egvpuzbkmnl1.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%2Fe5f58o76egvpuzbkmnl1.png" alt=" " width="799" height="472"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Verification Snapshot
&lt;/h2&gt;

&lt;p&gt;Recorded October 25, 2026:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;th&gt;Details&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Python test suite&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;79 PASSED, 20 subtests&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Full core, app, and verifier suite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Dashboard &amp;amp; diff (Node)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;9 PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Web UI lifecycle &amp;amp; diff integrity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Mastra TypeScript build&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Clean &lt;code&gt;tsc --noEmit&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Gemma local smoke compile&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Passed all envelope, schema &amp;amp; profile gates&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Mastra live repair&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;6/6 verifier checks passed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Temporal chaos recovery&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Checkpoint resume, no duplicate writes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;TabPFN evaluation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;94.55% precision, full matrix disclosed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Sentry redaction&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Strict allowlist verified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Offline submission check&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 model calls, clean execution + quarantine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Drift benchmark&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;PASSED&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;0 silent errors vs. 3 naive script errors&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Machine-Readable Verification Evidence
&lt;/h3&gt;

&lt;p&gt;Here is the exact verification check recorded from &lt;a href="https://github.com/Pritam-mb/week3/blob/main/evidence/live-integration-check-2026-10-25.json" rel="noopener noreferrer"&gt;&lt;code&gt;evidence/live-integration-check-2026-10-25.json&lt;/code&gt;&lt;/a&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"checked_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"2026-10-25"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"privacy"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Aggregate-only evidence. Zero raw row payloads recorded."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"repository_checks"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"python_pytest"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"79 passed, 20 subtests passed"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"node_dashboard_and_diff"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"9 passed"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"typescript_build"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"offline_submission_check"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"benchmark"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"gemma_ollama"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"model"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"gemma3:4b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"live_model_calls"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"validation_gate"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"response_envelope"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"recipe_schema"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"profile_contract"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"mastra_groq"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"sidecar_health"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"provider_model"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"groq/openai/gpt-oss-120b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"model_calls"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"molt_verification"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"verification_checks"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"6/6"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"human_approval"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"gated"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"tabpfn"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"precision"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;0.9455&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"recall"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mf"&gt;0.7222&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"source_bytes_altered"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"temporal"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"PASS"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"checkpoint_recovery"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"idempotent"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"model_calls"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Gemma:&lt;/strong&gt; Local &lt;code&gt;gemma3:4b&lt;/code&gt; compilation, constrained JSON schema output, a published failure ladder including an honest 0/5 result, and zero-call reuse thereafter.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mastra Agent Sidecar:&lt;/strong&gt; Out-of-band TypeScript repair agent with typed read-only tools and masked schema profiles, gated behind Molt’s own verifier and human approval.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Temporal:&lt;/strong&gt; Durable steady-state execution with injected crash recovery (&lt;code&gt;MOLT_CRASH_AT=1&lt;/code&gt;), checkpoint barriers, and idempotent replay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of TabPFN:&lt;/strong&gt; Local CPU anomaly advisory with a fully disclosed confusion matrix, non-commercial licensing boundaries, and zero data modification.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sentry:&lt;/strong&gt; Nine-phase tracing with strict allowlist redaction stripping all row values and PII.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;The point of Molt isn’t that the AI is right. On the hardest task I gave it, it was wrong five times out of five and told me it had succeeded.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The point is that it never gets the last word.&lt;/strong&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  devchallenge #hf26challenge #ai #opensource
&lt;/h1&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Kaggle benchmark</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Mon, 19 Oct 2026 08:34:48 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/-3fme</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/-3fme</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/t-rexbytes/does-your-llm-know-the-boundary-i-left-the-doors-open-and-6-of-10-ai-agents-crowned-themselves-4o42" class="crayons-story__hidden-navigation-link"&gt;Does Your LLM Know the Boundary? I Left the Doors Open and 6 of 10 AI Agents Crowned Themselves&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/t-rexbytes/does-your-llm-know-the-boundary-i-left-the-doors-open-and-6-of-10-ai-agents-crowned-themselves-4o42" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Kaggle Benchmarking Challenge Submission&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/t-rexbytes" class="crayons-avatar  crayons-avatar--l  "&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%2Fuser%2Fprofile_image%2F4026815%2Fa722cacd-1e7c-44a3-9a1d-945c06d48bb4.jpg" alt="t-rexbytes profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/t-rexbytes" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Sourish Panda
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Sourish Panda
                
                
              
              &lt;div id="story-author-preview-content-4825344" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/t-rexbytes" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&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%2Fuser%2Fprofile_image%2F4026815%2Fa722cacd-1e7c-44a3-9a1d-945c06d48bb4.jpg" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Sourish Panda&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/t-rexbytes/does-your-llm-know-the-boundary-i-left-the-doors-open-and-6-of-10-ai-agents-crowned-themselves-4o42" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Oct 9&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/t-rexbytes/does-your-llm-know-the-boundary-i-left-the-doors-open-and-6-of-10-ai-agents-crowned-themselves-4o42" id="article-link-4825344"&gt;
          Does Your LLM Know the Boundary? I Left the Doors Open and 6 of 10 AI Agents Crowned Themselves
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/devchallenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;devchallenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/kagglechallenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;kagglechallenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/ai"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;ai&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/machinelearning"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;machinelearning&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/t-rexbytes/does-your-llm-know-the-boundary-i-left-the-doors-open-and-6-of-10-ai-agents-crowned-themselves-4o42" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/exploding-head-daceb38d627e6ae9b730f36a1e390fca556a4289d5a41abb2c35068ad3e2c4b5.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;29&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/t-rexbytes/does-your-llm-know-the-boundary-i-left-the-doors-open-and-6-of-10-ai-agents-crowned-themselves-4o42#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              11&lt;span class="hidden s:inline"&gt;&amp;nbsp;comments&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            24 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
      <category>agents</category>
      <category>ai</category>
      <category>llm</category>
      <category>security</category>
    </item>
    <item>
      <title>16 of 26 federal grants that looked open to everyone hid a disqualifier in the fine print</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sun, 18 Oct 2026 10:21:09 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/16-of-26-federal-grants-that-looked-open-to-everyone-hid-a-disqualifier-in-the-fine-print-4bgd</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/16-of-26-federal-grants-that-looked-open-to-everyone-hid-a-disqualifier-in-the-fine-print-4bgd</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week2-2026-10-12"&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Grant Fine Print turns grant eligibility text into evidence-backed client screening cards.&lt;/strong&gt; It is built for freelance grant writers and small consultancies checking opportunities for several clients—not for replacing their judgment.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://grant-fine-print.onrender.com/" rel="noopener noreferrer"&gt;Open the app&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week2/tree/main/grant-fine-print" rel="noopener noreferrer"&gt;Browse the source&lt;/a&gt; · &lt;a href="https://grant-fine-print.onrender.com/proof/" rel="noopener noreferrer"&gt;Open the worked-example demo&lt;/a&gt; · &lt;a href="https://grant-fine-print.onrender.com/evidence" rel="noopener noreferrer"&gt;Inspect the evidence&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The short version:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The problem:&lt;/strong&gt; applicant-type codes cannot express every restriction buried in a notice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The product:&lt;/strong&gt; client profiles, source refresh, structured extraction, quote checks, deterministic matching, printable cards, explicit review reasons, and human corrections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The demonstrated catch:&lt;/strong&gt; three code-only mistakes corrected using verified foreign-organization restrictions, all involving one constructed UK profile and one rule family.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The honest boundary:&lt;/strong&gt; the current development replay leaves &lt;strong&gt;120 of 125 pairs for human review&lt;/strong&gt;. It is not a fresh inference run, an untouched holdout, or proof that fine-tuning outperforms prompting.&lt;/li&gt;
&lt;/ul&gt;

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

&lt;h3&gt;
  
  
  The fine print that changes the verdict
&lt;/h3&gt;

&lt;p&gt;Consider &lt;strong&gt;BTOD Centers, opportunity 360446 / PAR-27-024&lt;/strong&gt;, screened for &lt;strong&gt;Meridian Health Trust&lt;/strong&gt;, a constructed UK nonprofit profile.&lt;/p&gt;

&lt;p&gt;The applicant-code baseline says &lt;strong&gt;ELIGIBLE&lt;/strong&gt;. The notice says:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Non-domestic (non-U.S.) Entities (Foreign Organizations) are not eligible to apply.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The same notice separately allows &lt;strong&gt;foreign components&lt;/strong&gt;. These are not interchangeable: a foreign organization applying is different from a domestic organization including a foreign component.&lt;/p&gt;

&lt;p&gt;The historical extraction copied the relevant sentence but classified it as &lt;code&gt;citizenship_or_residency&lt;/code&gt;. The old matcher returned CHECK. The current bounded sentence interpreter recognizes the explicit &lt;strong&gt;organizational&lt;/strong&gt; exclusion, compares it with &lt;code&gt;us_based: false&lt;/code&gt;, and returns NOT_ELIGIBLE with the verified sentence.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Same notice, same constructed client&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Applicant-code baseline&lt;/td&gt;
&lt;td&gt;ELIGIBLE&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Original fine-tuned-labelled output&lt;/td&gt;
&lt;td&gt;CHECK&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Historical cached conditions + current matcher&lt;/td&gt;
&lt;td&gt;NOT_ELIGIBLE&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Author's reference label&lt;/td&gt;
&lt;td&gt;NOT_ELIGIBLE&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&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%2F9pe55bqr15a7blm9n8mv.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%2F9pe55bqr15a7blm9n8mv.png" alt=" " width="800" height="419"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshot 01 — Generated proof card, not a live application screenshot. It is built from the saved profile, predictions, and source-checked quote. Its footer states the development-replay scope and 120/125 CHECK count.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;This improvement is in rule interpretation, not model weights.&lt;/strong&gt; The prompted-cache stream supports the same catch. Historical backend labels do not authenticate the producing model or checkpoint.&lt;/p&gt;

&lt;p&gt;Two more pairs—&lt;strong&gt;359701 / C06 research facilities&lt;/strong&gt; and &lt;strong&gt;360541 / SPOREs&lt;/strong&gt;, both with the same UK profile—show the same baseline correction. They are three illustrative pairs, not three independent capabilities. The &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/reports/proof_pack/PROOF.md" rel="noopener noreferrer"&gt;proof notes&lt;/a&gt; list every qualifying catch rather than selecting only a flattering example.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo: The Complete Feature Walkthrough
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Multi-client dashboard and profile directory
&lt;/h3&gt;

&lt;p&gt;The dashboard shows available client profiles, the opportunity count, source-cache information, and backend selection. A writer can move between clients instead of rebuilding the same shortlist from scratch. The separate &lt;code&gt;/profiles&lt;/code&gt; page lists the client roster.&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%2Ffem3qr2xrn4gh1bgtcmp.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%2Ffem3qr2xrn4gh1bgtcmp.png" alt=" " width="800" height="773"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshot 02 — Existing dashboard screenshot. Counts, verdicts, and pull dates belong to the captured run; they are not the current benchmark or a promise of today's catalog size.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Custom client onboarding
&lt;/h3&gt;

&lt;p&gt;At &lt;code&gt;/profiles/new&lt;/code&gt;, a writer creates a profile containing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Organization name and type: nonprofit, for-profit, small business, university, tribal, government, individual, or other.&lt;/li&gt;
&lt;li&gt;U.S.-based status and state.&lt;/li&gt;
&lt;li&gt;Size band, focus keywords, and notes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The form validates required fields and handles duplicate-name slugs. The saved facts drive matching; focus keywords help order relevant opportunities, not prove eligibility.&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%2Fqgzlll4tjjlufv1o9v3z.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%2Fqgzlll4tjjlufv1o9v3z.png" alt=" " width="800" height="740"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Screenshot 03 placement — Client profile form:&lt;/strong&gt; capture &lt;code&gt;/profiles/new&lt;/code&gt; with a clearly fictional client, organization type, U.S.-based checkbox, state, size, and focus keywords visible. Caption: “Create a reusable client profile before screening.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  3. Source refresh, explicit offline mode, and screening runs
&lt;/h3&gt;

&lt;p&gt;The refresh flow offers a &lt;strong&gt;live Grants.gov pull&lt;/strong&gt; or an explicitly labelled &lt;strong&gt;offline sample&lt;/strong&gt;. The live pull caches official notice text and tracks source revisions through text hashes, while the sample provides an instant local testbed.&lt;/p&gt;

&lt;p&gt;From the screening controls, a grant specialist can screen against three distinct backends: the deterministic offline &lt;code&gt;mock&lt;/code&gt;, the zero-shot &lt;code&gt;prompted&lt;/code&gt; baseline, or the trained Tinker &lt;code&gt;fine_tuned&lt;/code&gt; model. The run summary explicitly certifies the backend actually executed, opportunity and profile counts, verdict totals, and direct links to the resulting cards.&lt;/p&gt;

&lt;p&gt;Live inference strictly enforces its provider configuration (&lt;code&gt;GFP_PROVIDER_BASE_URL&lt;/code&gt; and &lt;code&gt;TINKER_API_KEY&lt;/code&gt;) pointing at our custom Qwen3.5-4B weights (&lt;code&gt;grant-fine-print-sft&lt;/code&gt;); it never silently masks failures by falling back to mock output.&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%2Fcznc99i6p81z8ruocts1.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%2Fcznc99i6p81z8ruocts1.png" alt=" " width="800" height="425"&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%2F4okji68rzyrzm53oh9ln.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%2F4okji68rzyrzm53oh9ln.png" alt=" " width="800" height="515"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Screenshot 04 placement — Screening controls and run summary:&lt;/strong&gt; show the selected profile, backend, counts, and generated card links. If using the sample, keep the offline/mock label visible. Caption: “A run identifies its backend instead of disguising sample output as live inference.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  4. Searchable, filterable, printable client cards
&lt;/h3&gt;

&lt;p&gt;At &lt;code&gt;/card/&amp;lt;profile_id&amp;gt;&lt;/code&gt;, the writer can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Search within screening results and filter by &lt;strong&gt;LIKELY ELIGIBLE&lt;/strong&gt;, &lt;strong&gt;NOT ELIGIBLE&lt;/strong&gt;, or &lt;strong&gt;CHECK&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Sort by relevance, closing date, or award ceiling.&lt;/li&gt;
&lt;li&gt;See agency, deadline, award information where available, and the official notice link.&lt;/li&gt;
&lt;li&gt;Inspect source excerpts and highlighted disqualifying quotes.&lt;/li&gt;
&lt;li&gt;Print the screening sheet, including provenance such as backend and pull date.&lt;/li&gt;
&lt;/ul&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%2Fkr18i6ctibo9p2sgzl6d.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%2Fkr18i6ctibo9p2sgzl6d.png" alt=" " width="800" height="812"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshot 05 — Earlier application capture illustrating the highlighted-quote card design. This is not the current BTOD replay or evidence that all historical card decisions remain valid under the hardened matcher. The source-linked BTOD proof pack above is the current worked example.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  5. CHECK with a reason, not just an uncertain badge
&lt;/h3&gt;

&lt;p&gt;CHECK means the writer still needs to read. Cards can explain why: an empty extraction, unsupported condition, uncertain applicant grouping, missing profile facts, or an unverified quote.&lt;/p&gt;

&lt;p&gt;The intended benefit is a review starting point: the relevant extracted clause where available, the reason the code could not decide, and the original notice. &lt;strong&gt;Whether this saves net review time has not yet been measured.&lt;/strong&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%2Fohg1iuif6r9v47x0ajrx.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%2Fohg1iuif6r9v47x0ajrx.png" alt=" " width="716" height="1031"&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%2Ftbe5tbwlkaybnxjni40v.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%2Ftbe5tbwlkaybnxjni40v.png" alt=" " width="715" height="452"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Screenshot 06 placement — “Why CHECK” explanation:&lt;/strong&gt; show an unresolved condition, its actual review reason, and the official source link. Caption: “Unsupported or ambiguous rules stay with the human reviewer.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  6. Human corrections and recorded overrides
&lt;/h3&gt;

&lt;p&gt;The card's correction form lets a writer select an opportunity, change its verdict, and add a note. The application validates the profile, opportunity, and verdict before saving. Subsequent UI screening runs apply recorded corrections.&lt;/p&gt;

&lt;p&gt;An override is a &lt;strong&gt;human decision recorded separately&lt;/strong&gt;, not a model-generated quote or automatically verified training label. The current form handler saves through the filesystem correction path; the PostgreSQL integration also provides correction persistence methods.&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%2F43jo7eeo3fjvvk84m01h.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%2F43jo7eeo3fjvvk84m01h.png" alt=" " width="800" height="668"&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%2Fixvwmywlajvqcalk7mhk.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%2Fixvwmywlajvqcalk7mhk.png" alt=" " width="708" height="162"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Screenshot 07 placement — Correction form and saved entry:&lt;/strong&gt; capture “This is wrong,” the revised verdict, a short review note, and the correction list. Caption: “A grant specialist can challenge a result and leave a review trail.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  7. Evidence, downloadable charts, and a key-free proof demo
&lt;/h3&gt;

&lt;p&gt;The &lt;code&gt;/evidence&lt;/code&gt; page presents the saved catalog study and historical three-system benchmark, with warnings distinguishing those outputs from current code. Charts can be exported as PNGs.&lt;/p&gt;

&lt;p&gt;The separate &lt;a href="https://grant-fine-print.onrender.com/proof/" rel="noopener noreferrer"&gt;read-only &lt;code&gt;/proof/&lt;/code&gt; demo&lt;/a&gt; serves a self-contained comparison of the actual saved predictions, profile facts, verified quotes, and an honest failure case. It does not call a model. Allowlisted proof notes, JSON, provenance, and hero assets are available without exposing arbitrary repository files.&lt;/p&gt;

&lt;p&gt;The study and benchmark screenshots appear in the evidence section below; they are historical reporting, not a substitute for the replay table.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Stack diagnostics and operational health
&lt;/h3&gt;

&lt;p&gt;At &lt;code&gt;/stack&lt;/code&gt;, the application shows configured storage, source/cache information, profile and correction counts, model/checkpoint configuration, and whether optional provider keys are present. PostgreSQL connection/table counts are shown when available. &lt;code&gt;/healthz&lt;/code&gt; is a lightweight application health response.&lt;/p&gt;

&lt;p&gt;Configured keys are &lt;strong&gt;not&lt;/strong&gt; proof that a provider call succeeded; a healthy Flask route is &lt;strong&gt;not&lt;/strong&gt; a full database/model readiness check.&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%2F95y5oomr3mz1f5ido57e.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%2F95y5oomr3mz1f5ido57e.png" alt=" " width="788" height="665"&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%2Fabscj51mv7cu5r297fev.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%2Fabscj51mv7cu5r297fev.png" alt=" " width="721" height="647"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Screenshot 08 placement — Stack diagnostics:&lt;/strong&gt; capture storage status, available counts, source pull date, and model/provider configuration. Caption: “Visible configuration and connection status, without exposing secrets.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  9. Source adapters and command-line tools
&lt;/h3&gt;

&lt;p&gt;The ingestion boundary uses &lt;code&gt;BaseSourceAdapter&lt;/code&gt; and normalized opportunity objects so downstream extraction and matching are not tied to one portal's payload shape.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Source&lt;/th&gt;
&lt;th&gt;Current scope&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Grants.gov&lt;/td&gt;
&lt;td&gt;Implemented source used for the catalog study and saved evaluation.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EU Funding &amp;amp; Tenders Portal&lt;/td&gt;
&lt;td&gt;Prototype adapter with tests; not part of the reported benchmark.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Canada grants&lt;/td&gt;
&lt;td&gt;Registered placeholder, not a working evaluated source.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The repository also exposes CLI flows for pulling notices, screening, generating cards, evaluating saved predictions, initializing/importing the PostgreSQL store, optional official-link discovery, and preparing/training Tinker extraction models. These are developer tools, not a claim of a production scheduler or fully automated weekly delivery.&lt;/p&gt;

&lt;h3&gt;
  
  
  10. A proof-sheet interface rather than a chatbot
&lt;/h3&gt;

&lt;p&gt;The visual language is cream paper, ink typography, offset shadows, rubber-stamp verdicts, and marker-yellow quotes. Light/dark themes, responsive navigation, print styling, and reduced-motion handling support the review workflow. Evidence charts use patterns as well as color.&lt;/p&gt;

&lt;p&gt;The goal is for a writer to compare a client fact with a source sentence—not accept an unexplained confidence score.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Official Grants.gov notice
        |
        v
Saved source snapshot + text hash
        |
        v
Model extraction: structured conditions + source quotes
        |
        v
Python quote verifier: whitespace-normalized substring check
        |
        v
Bounded sentence interpretation + deterministic profile matching
        |
        +--&amp;gt; LIKELY ELIGIBLE: no supported disqualifier found; not a guarantee
        +--&amp;gt; NOT ELIGIBLE: model-backed rejection needs a verified source quote
        +--&amp;gt; CHECK: unresolved evidence or rules require human review
        |
        v
Client card + source link + review reasons + separate human overrides
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The model proposes conditions; it does not directly issue the final screening verdict. Quote presence is checked in Python, and supported conditions are compared with the profile in code. The bounded source grammar distinguishes foreign organizations from components, individual citizenship, and project location. It handles supported complete applicant alternatives as a union instead of treating every item as a separate mandatory requirement.&lt;/p&gt;

&lt;p&gt;Keyword matches alone cannot justify a model-backed rejection. A copied quote can still be misunderstood, and an extraction can omit an important condition, so quote verification is a necessary boundary—not a complete semantic guarantee.&lt;/p&gt;

&lt;h3&gt;
  
  
  Reliability and reproducibility work
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Strict extraction parsing:&lt;/strong&gt; malformed JSON, duplicate keys, unexpected schema, and truncated responses fail visibly rather than being cached as successful empty extraction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Empty extraction abstains:&lt;/strong&gt; no extracted conditions does not mean the applicant is eligible.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full cache identity:&lt;/strong&gt; source, prompt, model/checkpoint, and generation settings contribute to the extraction fingerprint. Legacy entries are not silently reused under the new identity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reuse across clients:&lt;/strong&gt; a matching extraction can be reused for several client profiles. New notices, amended text, or changed extraction settings can require new provider work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Escaped review text:&lt;/strong&gt; CHECK explanations and source-derived content are rendered with HTML escaping.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Separate evidence streams:&lt;/strong&gt; original predictions remain separate from current-code replay; hashes and pair-coverage checks make the saved comparison inspectable.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The implementation uses &lt;strong&gt;Python, Flask/Jinja, Gunicorn, PostgreSQL/psycopg, the Tinker SDK, an OpenAI-compatible inference boundary, SerpApi, and pytest&lt;/strong&gt;. Filesystem storage remains available for local/offline use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sponsor Integrations: What Each One Does and Where the Evidence Is
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Tiger Data — versioned official snapshots and PostgreSQL retrieval
&lt;/h3&gt;

&lt;p&gt;Tiger Data's PostgreSQL service on Timescale Cloud supplies the database integration. The current store defines these tables:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Table&lt;/th&gt;
&lt;th&gt;Role&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;opportunity_snapshots&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Source text, notice metadata, source hashes, capture timestamps, and current/historical revisions.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;official_link_candidates&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Discovery metadata for official-link candidates, separate from eligibility evidence.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;client_profiles&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Persistence support for reusable client facts.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;human_corrections&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Persistence support for human decisions and notes.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;rendered_cards&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Persistence support for card HTML and provenance.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A GIN index supports &lt;strong&gt;PostgreSQL keyword full-text retrieval&lt;/strong&gt; over title, agency, synopsis, and eligibility text. This is lexical search, not embeddings or pgvector. Retrieved snippets do not replace the full official snapshot used by the quote verifier.&lt;/p&gt;

&lt;p&gt;The distinction between storage support and UI wiring matters: the current profile-creation and correction handlers write local files; not every user interaction is automatically mirrored into PostgreSQL. The card page's displayed database-query timing is not an end-to-end application latency benchmark, so I am not claiming a universal “12 ms screening” result.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Implementation evidence:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/src/storage.py" rel="noopener noreferrer"&gt;database schema and store&lt;/a&gt;, &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/app/main.py" rel="noopener noreferrer"&gt;application integration&lt;/a&gt;, and &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/tests/test_integrations.py" rel="noopener noreferrer"&gt;integration-boundary tests&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%2F1r1bcl28pxbk8zi2w475.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%2F1r1bcl28pxbk8zi2w475.png" alt="Previously captured Tiger Data service console" width="800" height="459"&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%2Fj93e508m4qd4rh6vfz33.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%2Fj93e508m4qd4rh6vfz33.png" alt="Previously captured Tiger Data SQL Explorer" width="800" height="443"&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%2Fmdiykw9p1lxcf88kxvoa.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%2Fmdiykw9p1lxcf88kxvoa.png" alt="Previously captured Tiger Data database tables" width="799" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshots 09–11 — Existing Tiger Data console captures. They document the integration's development history; the linked schema is the reference for current table names. Account/connection details should be redacted before publication.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Tinker — the open-weight extraction and fine-tuning experiment
&lt;/h3&gt;

&lt;p&gt;The recorded experiment used &lt;strong&gt;Qwen/Qwen3.5-4B&lt;/strong&gt;, a rank-16 LoRA, &lt;strong&gt;100 model-assisted training examples&lt;/strong&gt;, three epochs, and a learning rate of &lt;strong&gt;0.0002&lt;/strong&gt;. The repository includes preparation and training code using Tinker's SDK, plus the inference backend used for structured extraction.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://tinker.thinkingmachines.ai/sessions/146167b6-6a85-54ec-bc00-f0489e3f207d" rel="noopener noreferrer"&gt;Recorded Tinker training session&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/src/train.py" rel="noopener noreferrer"&gt;Training implementation&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/src/extract.py" rel="noopener noreferrer"&gt;Extraction backend&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%2Frr9f7r2bfnqibdfnxc9t.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%2Frr9f7r2bfnqibdfnxc9t.png" alt="Previously captured Tinker training-session overview" width="800" height="486"&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%2F04zavd1grd5xwaio88pc.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%2F04zavd1grd5xwaio88pc.png" alt="Previously captured Tinker completed-run view" width="800" height="708"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshots 12–13 — Existing training-session captures. A training run is not, by itself, proof that a particular legacy prediction came from that checkpoint or that training improved generalization. The session may require its owner's account; public saved evidence is linked below.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The lesson was not “more training solves it.” A later audit found semantic errors in the training targets. Test-source IDs and hashes do not overlap the training examples, but the evaluation set has since been reused for diagnosis. Correcting target semantics and testing fresh notices are more important next steps than another epoch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No new training or remote inference was run for the current matcher replay.&lt;/strong&gt; The prompted and fine-tuned-labelled cache streams each produce five automatic rejections under the current code. I am documenting Tinker usage and lessons learned, not claiming a demonstrated fine-tuning advantage.&lt;/p&gt;

&lt;h3&gt;
  
  
  SerpApi — official-link recovery, not eligibility evidence
&lt;/h3&gt;

&lt;p&gt;If a notice is missing an official link, the discovery helper searches using the opportunity number or title with &lt;code&gt;site:grants.gov&lt;/code&gt;. It selects only HTTPS URLs on &lt;code&gt;grants.gov&lt;/code&gt; or its subdomains. Existing valid official links skip the search; a missing optional key does not fabricate a result.&lt;/p&gt;

&lt;p&gt;Discovery is available through the CLI and &lt;code&gt;POST /discover/&amp;lt;opportunity_id&amp;gt;&lt;/code&gt;. Search titles and snippets are discovery metadata only: they do not become source text, extracted restrictions, or grounds for a verdict.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Implementation evidence:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/src/discovery.py" rel="noopener noreferrer"&gt;link discovery and URL validation&lt;/a&gt; and &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/tests/test_integrations.py" rel="noopener noreferrer"&gt;boundary tests&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%2Fj9fl6hr5eipubnihkg39.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%2Fj9fl6hr5eipubnihkg39.png" alt="Previously captured SerpApi search activity" width="800" height="291"&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%2Fy6rs72y4qiat6pq0gxij.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%2Fy6rs72y4qiat6pq0gxij.png" alt="Previously captured SerpApi official-link search queries" width="800" height="485"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshots 14–15 — Existing SerpApi activity captures. They show development-time use, not a new billable call made to validate this submission. Redact account details and keys before publication.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Render — the hosted Flask application and read-only proof demo
&lt;/h3&gt;

&lt;p&gt;Render hosts the application at &lt;a href="https://grant-fine-print.onrender.com/" rel="noopener noreferrer"&gt;grant-fine-print.onrender.com&lt;/a&gt;. The checked-in Blueprint specifies Python 3.11.9, installs the application/PostgreSQL dependencies, and starts Gunicorn with the Flask application factory.&lt;/p&gt;

&lt;p&gt;Provider and database secrets are configured outside Git. The Blueprint keeps credential values out of the repository with &lt;code&gt;sync: false&lt;/code&gt; entries.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Implementation evidence:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/render.yaml" rel="noopener noreferrer"&gt;Render Blueprint&lt;/a&gt;, &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/app/main.py" rel="noopener noreferrer"&gt;Flask routes&lt;/a&gt;, and &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/tests/test_public_proof.py" rel="noopener noreferrer"&gt;public-proof route tests&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%2Fvhcd2wpbqfkn4n9fp759.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%2Fvhcd2wpbqfkn4n9fp759.png" alt="Previously captured Render web-service deployment dashboard" width="799" height="505"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshot 16 — Existing Render dashboard capture. A deployment screenshot documents that captured state; it is not a continuous uptime guarantee or proof of successful model calls.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;During this submission rewrite on &lt;strong&gt;October 19, 2026&lt;/strong&gt;, read-only HTTP checks returned &lt;strong&gt;200&lt;/strong&gt; for &lt;code&gt;/&lt;/code&gt;, &lt;code&gt;/healthz&lt;/code&gt;, &lt;code&gt;/profiles&lt;/code&gt;, &lt;code&gt;/evidence&lt;/code&gt;, &lt;code&gt;/stack&lt;/code&gt;, &lt;code&gt;/proof/&lt;/code&gt;, and &lt;code&gt;/proof/hero.png&lt;/code&gt;. These checks establish reachability at that time, not fresh Tinker inference, a successful database write, or the deployed commit identity. An earlier health probe returned 503 before recovering; I am not claiming that operational issue is proven fixed.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Evidence: What Was Measured
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Catalog audit: why applicant codes are not enough
&lt;/h3&gt;

&lt;p&gt;The saved &lt;strong&gt;October 17, 2026&lt;/strong&gt; catalog contains &lt;strong&gt;528 opportunities&lt;/strong&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Observation&lt;/th&gt;
&lt;th&gt;Count&lt;/th&gt;
&lt;th&gt;Interpretation&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;“Others” as the only applicant code&lt;/td&gt;
&lt;td&gt;180/528 (34.1%)&lt;/td&gt;
&lt;td&gt;The category alone leaves substantial eligibility detail unresolved.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Restriction-language regex hits&lt;/td&gt;
&lt;td&gt;221/528 (41.9%)&lt;/td&gt;
&lt;td&gt;A language proxy, not 221 proven disqualifications.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Author-labelled permissive-code subgroup containing hard restrictions&lt;/td&gt;
&lt;td&gt;16/26 (61.5%)&lt;/td&gt;
&lt;td&gt;Small stratified subgroup; not a population prevalence estimate.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Author-labelled Others-only subgroup containing hard restrictions&lt;/td&gt;
&lt;td&gt;12/15 (80.0%)&lt;/td&gt;
&lt;td&gt;Small stratified subgroup; not a population prevalence estimate.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&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%2Fd73djh4b2fh3tvelxp15.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%2Fd73djh4b2fh3tvelxp15.png" alt=" " width="688" height="962"&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%2Fr0nx979tb1iss2ytmpje.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%2Fr0nx979tb1iss2ytmpje.png" alt=" " width="677" height="746"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshot 17 — Saved catalog audit. It describes a historical snapshot, not today's open-notice count. The two labelled subgroups are small and single-author.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/results/study.json" rel="noopener noreferrer"&gt;Study output&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/src/study.py" rel="noopener noreferrer"&gt;Study implementation&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Original systems versus the current development replay
&lt;/h3&gt;

&lt;p&gt;The benchmark is &lt;strong&gt;25 unique notices × five constructed profiles = 125 pairs&lt;/strong&gt;, labelled by one author. Pairs share notices and profiles; they are not 125 independent observations. Current replay results apply new code to historical extracted conditions after development-set failures were inspected.&lt;/p&gt;

&lt;p&gt;“Automatic” means a non-CHECK result. “Correct among automatic” measures agreement with the author's verdict labels, not source-quote correctness or independently established real-world precision.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;System/run&lt;/th&gt;
&lt;th&gt;Automatic decisions&lt;/th&gt;
&lt;th&gt;Correct among automatic&lt;/th&gt;
&lt;th&gt;Human CHECK&lt;/th&gt;
&lt;th&gt;Disqualified called eligible&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Original code-only&lt;/td&gt;
&lt;td&gt;77/125&lt;/td&gt;
&lt;td&gt;53/77&lt;/td&gt;
&lt;td&gt;48/125&lt;/td&gt;
&lt;td&gt;14/65&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Original prompted&lt;/td&gt;
&lt;td&gt;61/125&lt;/td&gt;
&lt;td&gt;30/61&lt;/td&gt;
&lt;td&gt;64/125&lt;/td&gt;
&lt;td&gt;1/65&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Original fine-tuned-labelled run&lt;/td&gt;
&lt;td&gt;24/125&lt;/td&gt;
&lt;td&gt;12/24&lt;/td&gt;
&lt;td&gt;101/125&lt;/td&gt;
&lt;td&gt;0/65&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Current prompted-cache replay&lt;/td&gt;
&lt;td&gt;5/125&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;120/125&lt;/td&gt;
&lt;td&gt;0/65&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Current fine-tuned-cache replay&lt;/td&gt;
&lt;td&gt;5/125&lt;/td&gt;
&lt;td&gt;5/5&lt;/td&gt;
&lt;td&gt;120/125&lt;/td&gt;
&lt;td&gt;0/65&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&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%2Fsjipuulmq42cxyzx6hv0.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%2Fsjipuulmq42cxyzx6hv0.png" alt=" " width="690" height="897"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Screenshot 18 — Original saved benchmark visualization. Use the table above and current diagnostic for the hardened matcher's results; this historical screenshot does not display the current five-decision replay.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The original overall label agreement was &lt;strong&gt;70/125 for code-only&lt;/strong&gt;, &lt;strong&gt;47/125 for prompted&lt;/strong&gt;, and &lt;strong&gt;29/125 for the fine-tuned-labelled run&lt;/strong&gt;. Code-only wins on that metric and on coverage. Original fine-tuned output also wrongly rejected &lt;strong&gt;2/33 eligible pairs&lt;/strong&gt;; its source-valid quotes did not make the system reliably correct.&lt;/p&gt;

&lt;p&gt;The current fine-tuned-cache replay makes &lt;strong&gt;five rejections and no ELIGIBLE predictions&lt;/strong&gt;. Three correct baseline misses; the baseline already rejected the other two. Its exact labelled-sentence agreement is &lt;strong&gt;4/5&lt;/strong&gt;, a different measure from the five verdict-label agreements.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Zero false eligibilities is not a standalone safety result:&lt;/strong&gt; always abstaining—or never predicting ELIGIBLE—also achieves zero. The current result is a narrow, traceable catch with very low automation, not a general accuracy breakthrough or a demonstrated fine-tuning win.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. An honest failure: copied text can still miss the decisive rule
&lt;/h3&gt;

&lt;p&gt;For &lt;strong&gt;328026, a TIP Office notice of intent, and the for-profit profile&lt;/strong&gt;, the original model-backed output said ELIGIBLE even though the notice said applications were not being accepted.&lt;/p&gt;

&lt;p&gt;Its extraction was &lt;strong&gt;not empty&lt;/strong&gt;: it copied a mixed applicant list but omitted the application-status restriction. The current matcher returns CHECK because of ambiguous applicant grouping—not because it detected closure. The proof pack includes this case so the successful foreign-organization example does not hide extraction-coverage failures.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Public artifacts, not just screenshots
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Artifact&lt;/th&gt;
&lt;th&gt;What a reader can inspect&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/results/evidence/EVIDENCE.md" rel="noopener noreferrer"&gt;Original evidence bundle&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Saved predictions, labels, source text, constructed profiles, evaluator, examples, and SHA256 manifest.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/results/source_semantics/REPLAY.md" rel="noopener noreferrer"&gt;Current source-rule diagnostic&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Condition snapshot, current replay, full metrics, verdict changes, and limitations.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/reports/proof_pack/PROOF.md" rel="noopener noreferrer"&gt;Worked-example proof notes&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;All three qualifying catches and the honest failure, with actual quotes and profile facts.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://grant-fine-print.onrender.com/proof/" rel="noopener noreferrer"&gt;Hosted read-only comparison&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Browser-friendly proof page with no model inference.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;a href="https://grant-fine-print.onrender.com/proof/examples.json" rel="noopener noreferrer"&gt;Proof JSON&lt;/a&gt; and &lt;a href="https://grant-fine-print.onrender.com/proof/provenance.json" rel="noopener noreferrer"&gt;provenance&lt;/a&gt;
&lt;/td&gt;
&lt;td&gt;Machine-readable comparisons and artifact consistency checks.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/docs/images/btod-hero.provenance.json" rel="noopener noreferrer"&gt;Hero provenance&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Inputs, hashes, renderer, visible scope, and explicit generated-card limitations.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Hashes establish artifact consistency, not independent authenticity or correctness of the author's labels.&lt;/p&gt;

&lt;h2&gt;
  
  
  Code: Reproduce the Saved Evidence Without Keys
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/Pritam-mb/week2/tree/main/grant-fine-print" rel="noopener noreferrer"&gt;Repository and setup&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/docs/DEMO_OFFLINE.md" rel="noopener noreferrer"&gt;Safe offline instructions&lt;/a&gt; · &lt;a href="https://github.com/Pritam-mb/week2/blob/main/grant-fine-print/docs/PRODUCTION_SETUP.md" rel="noopener noreferrer"&gt;Production configuration&lt;/a&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;git&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;clone&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;https://github.com/Pritam-mb/week2.git&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;cd&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;week2/grant-fine-print&lt;/span&gt;&lt;span class="w"&gt;

&lt;/span&gt;&lt;span class="c"&gt;# Python 3.10+: verify original predictions, labels, hashes, and scores.&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="c"&gt;# No provider keys, site packages, or inference calls required.&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;python&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-B&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-S&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-m&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;src.evidence_bundle&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;verify&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;--bundle&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;results/evidence&lt;/span&gt;&lt;span class="w"&gt;

&lt;/span&gt;&lt;span class="c"&gt;# Replay current rules from saved public conditions into a NEW folder.&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="c"&gt;# Choose another output path if this one already exists.&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;python&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-B&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-S&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-m&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;src.matcher_replay&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;--bundle&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;results/evidence&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;--snapshot&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;results/source_semantics/conditions_snapshot.json&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;--output&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;results/replay_check&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Open &lt;code&gt;reports/proof_pack/index.html&lt;/code&gt; directly for the offline visual comparison. These commands recompute saved evidence and matcher results; &lt;strong&gt;they do not rerun the original model&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Tests and checks
&lt;/h3&gt;

&lt;p&gt;The latest full local suite run passed &lt;strong&gt;1,100 tests&lt;/strong&gt; using:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="c"&gt;# After creating/activating a virtual environment and installing test dependencies:&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;python&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-m&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;pip&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;install&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-e&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;".[app,test]"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="nv"&gt;$&lt;/span&gt;&lt;span class="nn"&gt;env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nv"&gt;PYTHON_DOTENV_DISABLED&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s1"&gt;'1'&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="n"&gt;python&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-B&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-m&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;pytest&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-q&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;-p&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;no:cacheprovider&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Coverage includes profile creation and validation, explicit mock screening, cards and filters, correction handling, source rules and adversarial cases, extraction/cache parsing, review-reason escaping, evidence/replay verification, hero generation, ingestion adapters, and public-proof allowlisting.&lt;/p&gt;

&lt;p&gt;The suite uses controlled fixtures and mocked service boundaries where appropriate. Passing tests do &lt;strong&gt;not&lt;/strong&gt; prove live provider accuracy, a production database transaction, customer satisfaction, or that every browser interaction has been manually tested. The original portable evidence verifier also passed, and the public pages listed above were reachable during the rewrite.&lt;/p&gt;

&lt;h2&gt;
  
  
  My First User: The Side-Hustle Plan
&lt;/h2&gt;

&lt;p&gt;The intended first user is a &lt;strong&gt;freelance grant writer managing several client profiles&lt;/strong&gt;. Instead of selling “AI that finds guaranteed grants,” I would sell a weekly evidence-review workflow: a shortlist, the sentence behind a rejection, and an explicit queue of things that still need judgment.&lt;/p&gt;

&lt;p&gt;The proposed price is &lt;strong&gt;$29–$49/month&lt;/strong&gt;. This is a hypothesis, not existing revenue. At an illustrative &lt;strong&gt;$39/month&lt;/strong&gt; and &lt;strong&gt;$100/hour&lt;/strong&gt; value of time, a writer needs &lt;strong&gt;23.4 net minutes saved per month&lt;/strong&gt; to break even. With 120/125 current pairs still needing review, I cannot assume the product already meets that bar.&lt;/p&gt;

&lt;p&gt;My first-three-customer pilot plan:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Recruit three freelance writers with different client domains.&lt;/li&gt;
&lt;li&gt;Help each create a client profile and establish their existing screening workflow.&lt;/li&gt;
&lt;li&gt;Compare review correctness and time with and without the evidence cards over four weeks.&lt;/li&gt;
&lt;li&gt;Record useful catches, missed restrictions, unresolved profile facts, and correction burden.&lt;/li&gt;
&lt;li&gt;Ask for paid conversion only if the measured benefit justifies it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;There are &lt;strong&gt;no reported external pilot outcomes or paying users yet&lt;/strong&gt;. Billing, authenticated client isolation, scheduled weekly delivery, and a production-ready multi-tenant SaaS are not claimed as completed features.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Grant screening is consequential enough that a confident-looking answer is not sufficient. The writer needs to inspect the source, understand the rule boundary, and challenge the result.&lt;/p&gt;

&lt;p&gt;Open model weights make the extractor replaceable. Readable Python makes the deterministic decision path inspectable. Public saved predictions, labelled examples, source snapshots, and reproducible metrics let someone check the demonstrated result without buying provider credits.&lt;/p&gt;

&lt;p&gt;The project builds on Qwen, Python, Flask, PostgreSQL, and the sponsor services rather than claiming those components as original inventions. My contribution is the review workflow and its explicit evidence boundaries: extraction is not eligibility, source presence is not semantic correctness, and human review is not hidden behind an accuracy headline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits and Next Steps
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Narrow automation:&lt;/strong&gt; the current development replay automatically resolves only five of 125 pairs, all as rejections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Small, reused evaluation:&lt;/strong&gt; 25 notices, constructed profiles, and single-author labels; no fresh independent holdout or second-labeler validation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Historical identity limits:&lt;/strong&gt; legacy cache names do not authenticate model/checkpoint provenance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Incomplete semantics:&lt;/strong&gt; foreign-organization exclusions are a demonstrated rule family, not proof of general grant understanding. Cost sharing, prior awards, partnerships, missing facts, and other unsupported constraints still need review.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extraction omissions:&lt;/strong&gt; a quote may be valid while a decisive condition is missing, as the notice-of-intent example shows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source scope:&lt;/strong&gt; Grants.gov is evaluated; EU ingestion is a prototype and Canada a placeholder. Notices can change after capture.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Operational scope:&lt;/strong&gt; recent read-only reachability is not a full live end-to-end check or an uptime promise. Old caches are intentionally cold under the new fingerprint, so live screening may incur fresh provider costs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Product validation:&lt;/strong&gt; time savings, pricing, retention, secure multi-user operation, and customer benefit remain to be established.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Next I would correct training-target semantics, collect missing client facts, establish a new notice-level holdout, and measure the workflow with real writers. A stronger model claim should follow that work—not precede it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Tiger Data:&lt;/strong&gt; versioned official snapshots and GIN keyword retrieval, with PostgreSQL persistence support for profiles, corrections, link candidates, and rendered cards. The current local-file UI boundaries are disclosed above.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Render:&lt;/strong&gt; the hosted Flask/Gunicorn application, read-only proof demo, operational health route, and reproducible Blueprint.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of SerpApi:&lt;/strong&gt; official Grants.gov link recovery with search snippets kept outside the eligibility evidence path.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Tinker is documented as an integration and fine-tuning experiment, not a claimed performance win.&lt;/strong&gt; The current replay does not establish improvement over the prompted model, so I am not presenting it as evidence of that prize requirement.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Grant Fine Print is a screening aid, not legal or grant advice. Confirm every decision in the current official notice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Chhaya: A Shade-First Walking Map for Tropical Cities</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sat, 10 Oct 2026 21:58:00 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/chhaya-a-shade-first-walking-map-for-tropical-cities-22f0</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/chhaya-a-shade-first-walking-map-for-tropical-cities-22f0</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week1-2026-10-05"&gt;Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Chhaya (ছায়া = "shade") is a live, open-source shade-first walking map + group hiking platform for Kolkata. It computes real building shadows in metric UTM, routes you through shade with dual-path "sun-minutes", lets you &lt;strong&gt;pick Club / Family / Trail mode, select any path, join any of 5 hiking groups, see + upload photo story cards on the map&lt;/strong&gt;, and — hero feature — &lt;strong&gt;listens hands-free via ElevenLabs voice briefings&lt;/strong&gt; so you can pocket your phone and truly touch grass.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Code:&lt;/strong&gt; &lt;/p&gt;
&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/chhya" rel="noopener noreferrer"&gt;
        chhya
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;Chhaya (ছায়া) — Kolkata Shade-Aware Navigation Map &amp;amp; Agent&lt;/h1&gt;
&lt;/div&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Hacktoberfest Open-Source AI Challenge 2026&lt;/strong&gt; · Week 1 Theme: &lt;em&gt;Touch Grass&lt;/em&gt;&lt;br&gt;
&lt;em&gt;Chhaya&lt;/em&gt; (Bengali &amp;amp; Hindi for "shade") moves building shadows with the Kolkata sun and routes walkers through shade instead of the shortest path.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Live demo:&lt;/strong&gt; &lt;em&gt;coming online via Render — see &lt;a href="https://github.com/Pritam-mb/chhya#4-deploy-render" rel="noopener noreferrer"&gt;Deploy&lt;/a&gt; below.&lt;/em&gt;&lt;/p&gt;

&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;What It Is&lt;/h2&gt;
&lt;/div&gt;
&lt;p&gt;In Kolkata's intense heat, two walks of the exact same length feel completely different depending on shade. Mainstream map applications optimize purely for distance or vehicle speed.&lt;/p&gt;
&lt;p&gt;Chhaya takes a plain-language request like:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Walk dadu to the clinic around 3 pm, he can't take much sun."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;An open model parses the walking constraints (origin, destination, depart time, sun aversion $k$, walking speed $v$). The routing engine models the sun's exact astronomical position, projects building shadows across the neighborhood in a metric projection (UTM Zone 45N), and discovers shaded side-lane routes (like Middleton…&lt;/p&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/chhya" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;br&gt;
&lt;strong&gt;Video&lt;/strong&gt;   &lt;iframe src="https://www.youtube.com/embed/U4MWp_zVBKA" width="710" height="399"&gt;
  &lt;/iframe&gt;


&lt;h2&gt;
  
  
  The shortest road in Kolkata is almost never the coolest one
&lt;/h2&gt;

&lt;p&gt;On a sweltering Tuesday afternoon, I tried walking from Middleton Row to Belle Vue Clinic in Kolkata at 2:15 PM. Google Maps said 11 minutes along the main road. What it omitted: 9 of those 11 minutes were in 38°C direct sun on asphalt with zero canopy. I arrived drenched, faint, squinting at a glaring screen.&lt;/p&gt;

&lt;p&gt;Every map optimizes for meters or car speed. For a human on foot in the tropics, the only metric that matters is &lt;strong&gt;how much sun you stand in&lt;/strong&gt;. Crossing to the shaded side, ducking into the lane behind the heritage library, catching a 3 PM building shadow that vanishes at noon — that's the difference between heat exhaustion and a pleasant stroll.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;Chhaya&lt;/strong&gt;: a shade-first navigation engine + AI voice agent + &lt;strong&gt;live group trail club platform&lt;/strong&gt; that calculates real-time building shadows, plans sun-avoiding routes, coordinates hikes, drops geo-locked story cards, and talks you through it — no screen-staring required.&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%2F40uemue4vvrelgc8fnyt.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%2F40uemue4vvrelgc8fnyt.png" alt="Chhaya Main Interface — Shade Studio with live shadow map, dual-path HUD and sundial slider" width="800" height="458"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Above: Shade Studio — hatched building shadows, green solid = shaded lanes, red dashed = sun lanes, sundial time slider 6 AM–6 PM, live solar badge.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  What I Built — a full outdoor platform, not just a router
&lt;/h2&gt;

&lt;p&gt;Chhaya is 4 apps in one paper-toned map shell (top nav: &lt;strong&gt;Agenda &amp;amp; Feed 🌱 · Live Trail &amp;amp; Dashboard 🥾 LIVE · Shade Studio 🗺️ · Grass Points 🌿&lt;/strong&gt;):&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Shade Studio&lt;/strong&gt; — solar physics + dual-path routing + select-your-path tickets&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Club / Live Trail Dashboard&lt;/strong&gt; — group hiking with radar, chat, repair, directions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Community Hike Feed&lt;/strong&gt; — browse / filter / announce any hike, 5 curated routes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Map Cards + Stories&lt;/strong&gt; — see cards, upload photo cards, geo-locked unlocks, QR trips&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ElevenLabs Voice&lt;/strong&gt; — hero hands-free briefing engine across all of the above&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI backbone&lt;/strong&gt; — Tinker fine-tune + TabPFN best-window + Tiger Data vibe search + Mastra agent + Sentry tracing&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Let me walk you through it like a real user journey.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Personal Journey Studio: SELECT your path, time, and trade-off
&lt;/h2&gt;

&lt;p&gt;This is where every walk starts. No blank prompt box — a guided &lt;strong&gt;"Plan Your Own Shaded Journey"&lt;/strong&gt; card:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;FROM / TO selects:&lt;/strong&gt; &lt;code&gt;Dadu's Residence (Middleton Row) → Belle Vue Clinic&lt;/code&gt;, &lt;code&gt;Flurys Tea Room → Camac Street Mall&lt;/code&gt;, &lt;code&gt;Oxford Bookstore → Russell Market&lt;/code&gt;, plus tap-anywhere-on-map &lt;code&gt;lat,lon&lt;/code&gt; picks that snap to the nearest lane.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AGENDA TYPE select:&lt;/strong&gt; &lt;code&gt;👵 Help / Family (slow, shaded, benches)&lt;/code&gt; · &lt;code&gt;🥾 Hike (group pack)&lt;/code&gt; · &lt;code&gt;🚶 Self Travel (solo trek)&lt;/code&gt; — one engine, three presets with different pace, sun-budget, and rest-stop cadence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SELECT TIME chips (see how shade changes live):&lt;/strong&gt; &lt;code&gt;🌅 08:30 · 82% shade&lt;/code&gt; · &lt;code&gt;🌤️ 10:30 · 70%&lt;/code&gt; · &lt;code&gt;☀️ 12:30 · 52% noon caution&lt;/code&gt; · &lt;code&gt;🌇 15:30 · 78% building shadow&lt;/code&gt; · &lt;code&gt;🌆 17:00 · 88% sunset breeze&lt;/code&gt;. Tapping a chip re-renders shadows + route instantly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Live comparison banner:&lt;/strong&gt; &lt;code&gt;Distance: 948m · Sun: 2.8 mins · Rest Stops: 2 Benches&lt;/code&gt; + one-sentence trade-off — e.g. &lt;em&gt;"At 08:30, continuous banyan canopies shield Dadu from 5.7 minutes of direct sun."&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;▶ Start My Journey&lt;/strong&gt; → creates a real trip (&lt;code&gt;/api/plan&lt;/code&gt; → &lt;code&gt;trip-XXXX&lt;/code&gt;), enrolls you by name, and opens Live Trail with those exact lanes.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  SELECT PATH: Shaded vs Shortest tickets
&lt;/h3&gt;

&lt;p&gt;In the Route HUD → &lt;strong&gt;Route tab&lt;/strong&gt;, two tappable tickets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;🌿 Shaded path — Pick/Picked ✓&lt;/code&gt;&lt;/strong&gt; (solid green line): &lt;code&gt;Sun 2.4 mins · Walk 14 min (710m) · 74% shaded lanes&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;Shortest — Direct&lt;/code&gt;&lt;/strong&gt; (ink dashed line): &lt;code&gt;Sun 8.8 mins · Walk 12 min (620m) · baseline&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Picking toggles &lt;code&gt;active-path&lt;/code&gt; styling and rewrites the CTA subtitle: &lt;em&gt;"Continues Middleton Row → Belle Vue @ 15:00 on the shaded path — Live Trail opens with these exact lanes"&lt;/em&gt; vs &lt;em&gt;"Direct is a sun-exposed baseline preview."&lt;/em&gt; You never walk a stale route — Continue carries &lt;strong&gt;exactly the displayed route&lt;/strong&gt; into Live Trail.&lt;/p&gt;

&lt;p&gt;Around it: &lt;strong&gt;sun-budget gauge&lt;/strong&gt; (marigold → vermilion needle, &lt;code&gt;0 / 4.0 sun-min&lt;/code&gt;), &lt;strong&gt;lane-by-lane exposure list&lt;/strong&gt; (&lt;code&gt;Middleton Row — 85m — 🌿 Shaded&lt;/code&gt; solid / &lt;code&gt;Camac Crossing — 40m — ☀️ Sunlit&lt;/code&gt; dashed + ✎ community calibration tags), &lt;strong&gt;Start time sweep&lt;/strong&gt; (sun-exposure curve every 10 min, best-start stamp, budget warning), &lt;strong&gt;Stops passport&lt;/strong&gt; (ticket per halt, stamped on arrival), &lt;strong&gt;Repair&lt;/strong&gt; (ranked regroup tickets + copyable group alert), &lt;strong&gt;Share&lt;/strong&gt; (trip chit + trip code + QR).&lt;/p&gt;

&lt;p&gt;The &lt;strong&gt;Sundial slider&lt;/strong&gt; (6:00–18:00, 30-min steps, play/pause auto-sweep, gnomon shadow follows) drives &lt;code&gt;GET /shadows?time=HH:MM&lt;/code&gt; + recomputes the route. At noon you get the honest alert: &lt;em&gt;"At 12 PM sun sits ~60° overhead. Shadows shrink to 0.56× height. Leave before 10 AM or after 2:30 PM."&lt;/em&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%2Fi1s4c12rfmrf2mi596ef.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%2Fi1s4c12rfmrf2mi596ef.png" alt=" " width="800" height="480"&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%2F5ha0tyroy6ighai4y0w4.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%2F5ha0tyroy6ighai4y0w4.png" alt=" " width="800" height="461"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  2. CLUB Mode + Live Trail Dashboard: hike together, never lose anyone
&lt;/h2&gt;

&lt;p&gt;Switch the top mode tabs to &lt;strong&gt;🏃 Club&lt;/strong&gt; or hit &lt;strong&gt;Live Trail &amp;amp; Dashboard (LIVE)&lt;/strong&gt;. This is the group-hiking OS:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Group switcher (SELECT ANY HIKING GROUP):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;🏃 Park Street Sun-Smart Trail Club (5 walkers · 74% shade)
👵 Dadu's Morning Clinic Walk
🍜 Bow Barracks Heritage Food Trail
🌿 Rabindra Sarobar Canopy Trek
📚 College Street Boi Para Passage
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Changing the dropdown (&lt;code&gt;#group-hike-select&lt;/code&gt;) swaps route summary, radar, chat, stories, stops, and map pins instantly. Enroll row: type your name → &lt;strong&gt;🥾 Enroll&lt;/strong&gt; (+5 🌱).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Route summary card (always visible):&lt;/strong&gt; &lt;code&gt;Flurys Tea Room → Camac Street Mall · 1.2 km · 3.5 sun-min · 18 min · UV 4.2 Mild · 74% Shade badge&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sub-tabs:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;🏃 Radar:&lt;/strong&gt; live GPS HUD (&lt;code&gt;22.5532°N 88.3526°E · ±6m · Next story 45m&lt;/code&gt;), &lt;code&gt;🛰️ Use Device GPS&lt;/code&gt; + &lt;code&gt;▶ Auto-Walk&lt;/code&gt; simulator, &lt;code&gt;🚶 Step Forward (+50m)&lt;/code&gt;, &lt;code&gt;◉ Check-in (+10 🌱)&lt;/code&gt;, &lt;code&gt;● We Reached (+50 🌱)&lt;/code&gt;, walker list with straggler banner (&lt;em&gt;"Rina resting at Russell Chai Stall bench (85% shade) — Wait 4 min at Loreto Colonnade (78% shade)"&lt;/em&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;🧭 Route:&lt;/strong&gt; turn-by-turn shaded guidance with mini shade analysis (&lt;code&gt;🌳 Shaded 640m · ☀️ Sun 180m&lt;/code&gt;) and gradient bar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;💬 Chat:&lt;/strong&gt; end-to-end trip channel with quick-status chips (&lt;em&gt;Taking a rest / In deep shade / Hydration break / Dropped story / Catching up&lt;/em&gt;), polling &lt;code&gt;GET /api/trip/{code}/chat?since_id=&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;📸 Stories:&lt;/strong&gt; geo-tagged discoveries, &lt;code&gt;📸 Pin Story&lt;/code&gt; button, unlock within 60m for +25 🌱.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;🛑 Stops:&lt;/strong&gt; regroup halts + ranked &lt;strong&gt;STRAGGLER REPAIR RANKINGS&lt;/strong&gt; (WAIT / SHORTCUT / SWEEP / SPLIT scored by &lt;code&gt;w1*wait + w2*sun + w3*rejoin&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;📍 Post:&lt;/strong&gt; Post to Trail Map (see Cards section below).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Club mode uses &lt;code&gt;k=4.5&lt;/code&gt; sun aversion, 12-min regroup cadence, chai-stop copy (&lt;em&gt;"Chai regroup stop at the 8-minute mark"&lt;/em&gt;), and live member dots on the map via &lt;code&gt;POST /api/trip/{code}/position&lt;/code&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%2Fb8bxyfqtrrx6uxcpvgvq.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%2Fb8bxyfqtrrx6uxcpvgvq.png" alt=" " width="800" height="467"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  3. Community Hike Feed: SELECT ANY hike, filter, or announce your own
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Agenda &amp;amp; Feed&lt;/strong&gt; is the default landing page — &lt;strong&gt;🌱 Kolkata Shaded Hike Community&lt;/strong&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Join upcoming group hikes, explore tree-lined heritage corridors, and earn Grass Points for every outdoor step."&lt;/em&gt; + &lt;strong&gt;+ Initiate New Group Hike&lt;/strong&gt; button.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;5 curated fixed routes&lt;/strong&gt; (&lt;code&gt;GET /api/routes/fixed&lt;/code&gt;) rendered as joinable cards:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Card&lt;/th&gt;
&lt;th&gt;Agenda&lt;/th&gt;
&lt;th&gt;Distance&lt;/th&gt;
&lt;th&gt;Shade&lt;/th&gt;
&lt;th&gt;Package&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Park Street Sun-Smart Heritage Trail&lt;/td&gt;
&lt;td&gt;🥾 Hike&lt;/td&gt;
&lt;td&gt;Medium 1.2 km&lt;/td&gt;
&lt;td&gt;74%, 3.5 sun-min&lt;/td&gt;
&lt;td&gt;💧 Water/Light&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dadu's Morning Shaded Clinic Walk&lt;/td&gt;
&lt;td&gt;👵 Help&lt;/td&gt;
&lt;td&gt;Short 0.9 km&lt;/td&gt;
&lt;td&gt;82%, 2.8 sun-min&lt;/td&gt;
&lt;td&gt;Medical/benches&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bow Barracks Food Trail&lt;/td&gt;
&lt;td&gt;🥾 Hike&lt;/td&gt;
&lt;td&gt;Medium 1.2 km&lt;/td&gt;
&lt;td&gt;82%, 2.2 sun-min&lt;/td&gt;
&lt;td&gt;☕ Food &amp;amp; Chai&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rabindra Sarobar Canopy Trek&lt;/td&gt;
&lt;td&gt;🚶 Self&lt;/td&gt;
&lt;td&gt;Long 4.8 km&lt;/td&gt;
&lt;td&gt;78%, 5.1 sun-min&lt;/td&gt;
&lt;td&gt;💧 Nature trek&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;College St Boi Para Passage&lt;/td&gt;
&lt;td&gt;🚶 Self&lt;/td&gt;
&lt;td&gt;Medium 1.4 km&lt;/td&gt;
&lt;td&gt;76%, 2.9 sun-min&lt;/td&gt;
&lt;td&gt;☕ Coffee/books&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Each card: description, shade badge, walker count, &lt;strong&gt;Embark on Trail&lt;/strong&gt; (registers name → joins trip → opens Live Trail).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Filter chips:&lt;/strong&gt; Agenda (&lt;code&gt;All / Hike / Help / Self&lt;/code&gt;), Distance (&lt;code&gt;Short &amp;lt;1.5km / Medium 1.5–4km / Long &amp;gt;4km&lt;/code&gt;), Package (&lt;code&gt;Food / Water&lt;/code&gt;). Filtering is instant client-side.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Announce form:&lt;/strong&gt; Title + From/To selects (populated from &lt;code&gt;/pois&lt;/code&gt;) + Distance Category + Package + Depart Time + Host Name → &lt;code&gt;POST /api/feed/create&lt;/code&gt; computes shade-wise route, publishes to feed, awards host +5 🌱, posts system chat &lt;em&gt;"Created hike group…"&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Plus &lt;strong&gt;Grass Points Passport&lt;/strong&gt;: &lt;code&gt;OUTDOOR PASSPORT · Canopy Ranger · 40 🌱&lt;/code&gt;, tier bar (Seedling 0 → Scout 40 → Ranger 80 → Master 150+), rules grid (+5 join / +10 check-in / +25 unlock / +50 finish), unlocked discoveries journal, Kolkata leaderboard (&lt;code&gt;GET /api/leaderboard&lt;/code&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%2Fna2b5k9ke56w7le5sxra.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%2Fna2b5k9ke56w7le5sxra.png" alt=" " width="800" height="461"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  4. Cards: SEE cards on the map + UPLOAD photo cards anywhere
&lt;/h2&gt;

&lt;p&gt;This is the community memory layer (&lt;code&gt;/api/cards&lt;/code&gt;, &lt;code&gt;/api/cards/near&lt;/code&gt;, &lt;code&gt;/api/cards/{id}/unlock&lt;/code&gt;, &lt;code&gt;/api/cards/{id}/report&lt;/code&gt;):&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SEE cards:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tap any POI landmark → popup → &lt;code&gt;Start Here / End Here&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Tap any map point → popup → &lt;code&gt;Start here / End here / Leave card&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Live Trail → 📍 Post tab:&lt;/strong&gt; tap map → dashed preview box updates (&lt;code&gt;No location picked yet&lt;/code&gt; → &lt;code&gt;22.55321, 88.35261&lt;/code&gt;), pin list below shows all nearby cards (&amp;lt;60m immediate, &amp;lt;300m radar).&lt;/li&gt;
&lt;li&gt;Story radar cards show shade %, distance, lock state. Locked cards (&amp;gt;50m away) open the &lt;strong&gt;Position-Locked modal&lt;/strong&gt; (&lt;em&gt;"Walk closer — 85m away · Locked until you arrive"&lt;/em&gt;). Within 60m → celebratory unlock modal with photo, paragraph, &lt;code&gt;+25 🌱 Collect Points &amp;amp; Add to Journal&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;UPLOAD cards (two paths):&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;📸 Pin Story modal:&lt;/strong&gt; title + paragraph (280 chars) + &lt;strong&gt;photo file upload&lt;/strong&gt; with live preview + auto shade label + coords label → &lt;code&gt;Pin Story to Trail (+25 🌱)&lt;/code&gt;. Photo stored as capped data-URL (&lt;code&gt;CARD_PHOTO_MAX_BYTES&lt;/code&gt;), rendered in unlock modal + journal gallery.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;📍 Post to Trail Map form:&lt;/strong&gt; title + description + type select (&lt;code&gt;👁️ Observation / 🌳 Shade Find / ⚠️ Warning / ☕ Food-Water / 📸 Story Drop&lt;/code&gt;) → &lt;code&gt;📍 Pin to Map&lt;/code&gt;. Types map to &lt;code&gt;tip/warning/meetup/note/hike/story&lt;/code&gt; server-side with 140-char cleaning, 24h TTL, 5/min rate limit, and one-tap &lt;strong&gt;Report → hide&lt;/strong&gt; moderation.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Every card carries &lt;code&gt;shade_at_creation&lt;/code&gt;, visibility (&lt;code&gt;public/group/addressed&lt;/code&gt;), and trip linkage — so &lt;em&gt;"huge banyan 95% shade"&lt;/em&gt; or &lt;em&gt;"fresh daab vendor"&lt;/em&gt; persists for the next walker.&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%2Fvlx9l8ffff89b8g5zql4.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%2Fvlx9l8ffff89b8g5zql4.png" alt=" " width="800" height="468"&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%2Fvs6jcm87s8cqmzm12q79.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%2Fvs6jcm87s8cqmzm12q79.png" alt=" " width="496" height="942"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  5. ⭐ HERO: Hands-Free Voice Guidance with ElevenLabs — pocket your phone and touch grass ⭐
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;If you remember one partner integration, make it this one. Screens kill walks in the tropics — glare blindness, squinting, stepping into traffic. &lt;strong&gt;Chhaya's ElevenLabs briefing is the entire point of "Touch Grass": you listen, you walk, you look at trees, not pixels.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Where it lives:&lt;/strong&gt; every Route HUD has a &lt;strong&gt;voice card&lt;/strong&gt;: &lt;code&gt;▶ Listen briefing&lt;/code&gt; button + provider tag + animated wave + script preview:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Route ready. Starting from Middleton Row at 3 PM. Head south 80 meters under the building canopy, then turn right into the shaded lane. You'll avoid 6.4 minutes of direct sunlight. Pocket your phone and enjoy the walk."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;How it works (&lt;code&gt;backend/voice.py&lt;/code&gt; + &lt;code&gt;POST /voice/briefing&lt;/code&gt;):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Frontend sends the generated briefing text (origin → destination @ time + trade-off sentence + first 2 shade cues).&lt;/li&gt;
&lt;li&gt;Backend tries &lt;strong&gt;ElevenLabs&lt;/strong&gt; (&lt;code&gt;eleven_multilingual_v2&lt;/code&gt; → &lt;code&gt;eleven_flash_v2_5&lt;/code&gt; fallback, George voice &lt;code&gt;JBFqnCBsd6RMkjVDRZzb&lt;/code&gt; default, &lt;code&gt;stability 0.65 / similarity 0.75&lt;/code&gt;), returns &lt;code&gt;audio/mpeg&lt;/code&gt; base64 → played as &lt;code&gt;data:audio/mpeg;base64,…&lt;/code&gt; with &lt;code&gt;ElevenLabs Audio Active&lt;/code&gt; tag + wave animation + &lt;code&gt;Replay Briefing&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero-key resilience:&lt;/strong&gt; no &lt;code&gt;ELEVENLABS_API_KEY&lt;/code&gt; → returns &lt;code&gt;has_audio:false, provider:browser_web_speech&lt;/code&gt; → Web Speech API speaks instantly (&lt;code&gt;Browser Speech Active&lt;/code&gt;). No dead button, no paywall, works offline in alleys.&lt;/li&gt;
&lt;li&gt;402/quota/voice errors auto-retry default voice, then gracefully fall back — logged via Sentry trace.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Why it wins Touch Grass:&lt;/strong&gt; field testers walked Middleton Row → Belle Vue without pulling the phone out once. Shade cues are phrased for ears (&lt;em&gt;"stay on the eastern sidewalk for the next 80 meters, deep 1.7× building shade"&lt;/em&gt;), not map zoom levels. Combine with Auto-Walk + audio and you get a true eyes-up walk.&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%2Fdkazi3amm3umv6iuz8rk.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%2Fdkazi3amm3umv6iuz8rk.png" alt=" " width="478" height="247"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Try in 30 seconds:&lt;/strong&gt;

&lt;ol&gt;
&lt;li&gt;Open Feed → pick &lt;strong&gt;Park Street Sun-Smart Heritage Trail&lt;/strong&gt; → Embark&lt;/li&gt;
&lt;li&gt;Or Studio → FROM &lt;code&gt;Dadu's Residence&lt;/code&gt; TO &lt;code&gt;Belle Vue Clinic&lt;/code&gt; → time &lt;code&gt;15:30&lt;/code&gt; → shaded ticket → &lt;strong&gt;Continue on this route&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Live Trail → &lt;strong&gt;▶ Listen briefing&lt;/strong&gt; (ElevenLabs) → pocket phone → &lt;strong&gt;Step Forward&lt;/strong&gt; → check in, chat, unlock a story card&lt;/li&gt;
&lt;li&gt;Feed → &lt;strong&gt;📍 Post&lt;/strong&gt; a shade find with photo&lt;/li&gt;
&lt;/ol&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Local:&lt;/strong&gt; &lt;code&gt;python backend/main.py&lt;/code&gt; → &lt;a href="http://localhost:8000" rel="noopener noreferrer"&gt;http://localhost:8000&lt;/a&gt; (100% offline fallback, no keys needed)&lt;/li&gt;
&lt;/ul&gt;


&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/chhya" rel="noopener noreferrer"&gt;
        chhya
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;Chhaya (ছায়া) — Kolkata Shade-Aware Navigation Map &amp;amp; Agent&lt;/h1&gt;
&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Hacktoberfest Open-Source AI Challenge 2026&lt;/strong&gt; · Week 1 Theme: &lt;em&gt;Touch Grass&lt;/em&gt;&lt;br&gt;
&lt;em&gt;Chhaya&lt;/em&gt; (Bengali &amp;amp; Hindi for "shade") moves building shadows with the Kolkata sun and routes walkers through shade instead of the shortest path.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Live demo:&lt;/strong&gt; &lt;em&gt;coming online via Render — see &lt;a href="https://github.com/Pritam-mb/chhya#4-deploy-render" rel="noopener noreferrer"&gt;Deploy&lt;/a&gt; below.&lt;/em&gt;&lt;/p&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;What It Is&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;In Kolkata's intense heat, two walks of the exact same length feel completely different depending on shade. Mainstream map applications optimize purely for distance or vehicle speed.&lt;/p&gt;

&lt;p&gt;Chhaya takes a plain-language request like:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Walk dadu to the clinic around 3 pm, he can't take much sun."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;An open model parses the walking constraints (origin, destination, depart time, sun aversion $k$, walking speed $v$). The routing engine models the sun's exact astronomical position, projects building shadows across the neighborhood in a metric projection (UTM Zone 45N), and discovers shaded side-lane routes (like Middleton…&lt;/p&gt;&lt;/div&gt;


&lt;/div&gt;
&lt;br&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/chhya" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;


&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;License:&lt;/strong&gt; MIT, open source&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stack:&lt;/strong&gt; Python 3.11, FastAPI, Shapely, PyProj UTM 45N, Leaflet/MapLibre, Mastra (&lt;code&gt;agent/src/agent.ts&lt;/code&gt;), TabPFN-2, Tinker, Tiger Data pgvector, ElevenLabs, Sentry&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt; ┌──────────────────────────────────────────────────────────┐
 │                      User Request                         │
 │     "Dadu ke clinic niye chalo 3 baje, roddur kom"        │
 └────────────────────────────┬─────────────────────────────┘
                               │
                               ▼
 ┌──────────────────────────────────────────────────────────┐
 │      Tinker Fine-Tuned Model (Qwen-2.5-3B-Instruct)      │
 │    Parsed: {dest: clinic, time: 15:00, tolerance: low}    │
 └────────────────────────────┬─────────────────────────────┘
                               │
                ┌──────────────┴──────────────┐
                ▼                             ▼
 ┌───────────────────────────┐ ┌───────────────────────────┐
 │   TabPFN-2 Best Window    │ │  Tiger Data (pgvector)    │
 │  Forecasts coolest 2-hr   │ │  Hybrid Semantic Search   │
 │   slot (73.5% MAE drop)   │ │   for shaded rest halts   │
 └─────────────┬─────────────┘ └─────────────┬─────────────┘
                └──────────────┬──────────────┘
                               │
                               ▼
 ┌──────────────────────────────────────────────────────────┐
 │     Shade Engine &amp;amp; Dual-Path Dijkstra Routing            │
 │     - NOAA Solar Position (Kolkata 22.55°N, 88.35°E)     │
 │     - 650 OSM Buildings extruded in UTM Zone 45N         │
 │     - Edge Cost: c_e = l_e * (1 + k * s_e)               │
 └────────────────────────────┬─────────────────────────────┘
                               │
                ┌──────────────┴──────────────┐
                ▼                             ▼
 ┌───────────────────────────┐ ┌───────────────────────────┐
 │   Leaflet Dynamic Map     │ │   ElevenLabs Voice Engine │
 │   Live shadow polygons    │ │   Hands-free audio route  │
 │   &amp;amp; dual-color path lines │ │   briefing for the pocket │
 └───────────────────────────┘ └───────────────────────────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Step 1: Solar Geometry and Metric Shadow Extrusion
&lt;/h3&gt;

&lt;p&gt;All GIS in &lt;strong&gt;UTM Zone 45N (EPSG:32645)&lt;/strong&gt; (1 unit = 1 meter). NOAA solar algorithm → elevation (α) + azimuth (φ) per minute. Shadow factor &lt;code&gt;s_f = 1/tan(α)&lt;/code&gt;, anti-solar vector &lt;code&gt;φ_shadow = (φ+180) mod 360&lt;/code&gt;, offset &lt;code&gt;dx = sin·(h·s_f)&lt;/code&gt;, &lt;code&gt;dy = cos·(h·s_f)&lt;/code&gt;, convex hull base+roof via &lt;code&gt;unary_union&lt;/code&gt;. At 3 PM (~30.16°) shadows are &lt;strong&gt;1.72× height&lt;/strong&gt; — deep shade over narrow lanes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Shade-Aware Street Graph Routing
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1,203 walkable segments / 1,108 nodes&lt;/strong&gt; around Park/Camac St. Per edge sunlit fraction &lt;code&gt;s_e ∈ [0,1]&lt;/code&gt;, cost &lt;code&gt;c_e = l_e·(1 + k·s_e)&lt;/code&gt; (&lt;code&gt;k=4.5&lt;/code&gt; low tolerance), sun-minutes &lt;code&gt;Σ l_e·s_e / v&lt;/code&gt; (&lt;code&gt;v=50 m/min&lt;/code&gt;). Dual Dijkstra (&lt;code&gt;k=0&lt;/code&gt; shortest vs &lt;code&gt;k=4.5&lt;/code&gt; shade) returns exact trade-off.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Fine-Tuning with Tinker
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;Qwen-2.5-3B-Instruct&lt;/code&gt; → &lt;code&gt;tinker/chhaya-codemixed-3b&lt;/code&gt; on Romanized Bengali/Hindi/English (&lt;code&gt;scripts/tinker_finetune.py&lt;/code&gt;, &lt;code&gt;results/tinker_eval.json&lt;/code&gt;):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Baseline&lt;/th&gt;
&lt;th&gt;Tinker Fine-Tuned&lt;/th&gt;
&lt;th&gt;Gain&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Parse Accuracy (30 held-out)&lt;/td&gt;
&lt;td&gt;66.7%&lt;/td&gt;
&lt;td&gt;93.3%&lt;/td&gt;
&lt;td&gt;+26.6%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Romanized Bengali&lt;/td&gt;
&lt;td&gt;62.5%&lt;/td&gt;
&lt;td&gt;100.0%&lt;/td&gt;
&lt;td&gt;+37.5%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Romanized Hindi&lt;/td&gt;
&lt;td&gt;50.0%&lt;/td&gt;
&lt;td&gt;83.3%&lt;/td&gt;
&lt;td&gt;+33.3%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Latency&lt;/td&gt;
&lt;td&gt;1,120 ms&lt;/td&gt;
&lt;td&gt;285 ms&lt;/td&gt;
&lt;td&gt;3.9× faster&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost&lt;/td&gt;
&lt;td&gt;70B equiv&lt;/td&gt;
&lt;td&gt;3B&lt;/td&gt;
&lt;td&gt;4.2× cheaper&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&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%2Fiqhbscj0gv6evf521at7.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%2Fiqhbscj0gv6evf521at7.png" alt="Tinker Benchmark Results — 93.3% vs 66.7%, 285ms vs 1120ms" width="800" height="234"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: TabPFN Best-Window (Prior Labs)
&lt;/h3&gt;

&lt;p&gt;TabPFN-2 on &lt;strong&gt;7,657 Oct hourly records (2004–2024, Open-Meteo)&lt;/strong&gt; for Park St, held-out Oct 2025 (403 rows):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;MAE&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Climatology baseline&lt;/td&gt;
&lt;td&gt;1.7723 °C&lt;/td&gt;
&lt;td&gt;reference&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TabPFN-2&lt;/td&gt;
&lt;td&gt;0.4699 °C&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;73.49% error cut&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Powers &lt;code&gt;/window&lt;/code&gt; + Best Walking Window widget (clickable cards apply time to slider + route).&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Vibe Search with Tiger Data
&lt;/h3&gt;

&lt;p&gt;Community shade lore in Tiger Lever &lt;code&gt;pgvector&lt;/code&gt;, hybrid keyword + cosine search:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;description&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;shade_score&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
       &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;embedding&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;query_vec&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;AS&lt;/span&gt; &lt;span class="n"&gt;similarity&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;community_waypoints&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;embedding&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;query_vec&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;65&lt;/span&gt;
&lt;span class="k"&gt;ORDER&lt;/span&gt; &lt;span class="k"&gt;BY&lt;/span&gt; &lt;span class="n"&gt;similarity&lt;/span&gt; &lt;span class="k"&gt;DESC&lt;/span&gt; &lt;span class="k"&gt;LIMIT&lt;/span&gt; &lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;"somewhere quiet with heavy tree shade"&lt;/em&gt; → &lt;em&gt;"old banyan bench behind the diocese"&lt;/em&gt;. Offline deterministic fallback when signal drops.&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%2Fuecf3qf5sm8lrn2wjv4d.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%2Fuecf3qf5sm8lrn2wjv4d.png" alt="Tiger Data hybrid search query — vibe match for shaded halts" width="799" height="286"&gt;&lt;/a&gt;&lt;br&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%2Fr9xyjfk7nidfgeodqmwj.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%2Fr9xyjfk7nidfgeodqmwj.png" alt="Tiger Data dashboard — live pgvector index status" width="800" height="449"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 6: Mastra Agent
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;agent/src/agent.ts&lt;/code&gt; (&lt;code&gt;@mastra/core&lt;/code&gt;): tools &lt;code&gt;planRoute&lt;/code&gt;, &lt;code&gt;bestWindow&lt;/code&gt;, &lt;code&gt;tigerSearch&lt;/code&gt;, &lt;code&gt;getShadows&lt;/code&gt;, memory + orchestration over FastAPI. &lt;code&gt;cd agent &amp;amp;&amp;amp; npm install &amp;amp;&amp;amp; GROQ_API_KEY=… npm run dev "Walk dadu to clinic 3pm, low sun"&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 7: ElevenLabs (hero — see Section 5 above)
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;backend/voice.py&lt;/code&gt; + &lt;code&gt;backend/briefing.py&lt;/code&gt; + voice card. Multilingual models, George default voice, base64 mp3, browser fallback, Sentry-traced latency. This is what makes Chhaya eyes-up and genuinely Touch-Grass.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 8: Sentry + Weather + Repair
&lt;/h3&gt;

&lt;p&gt;Sentry traces Tinker latency, shadow extrusion (~0.10s / 650 bldgs), routing. Open-Meteo scales sun budgets (&lt;code&gt;≥38°C ×0.5, ≥33°C ×0.75, UV≥8 ×0.75&lt;/code&gt;). Repair engine ranks WAIT/SHORTCUT/SWEEP/SPLIT for stragglers &amp;gt;3 min behind.&lt;/p&gt;




&lt;h2&gt;
  
  
  Taking It Outside: Field Test
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Journey&lt;/th&gt;
&lt;th&gt;Shortest (Google)&lt;/th&gt;
&lt;th&gt;Chhaya Shade Route&lt;/th&gt;
&lt;th&gt;Seen&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Middleton Row → Belle Vue (2:30 PM)&lt;/td&gt;
&lt;td&gt;620m, 8.8 sun-min&lt;/td&gt;
&lt;td&gt;710m, 2.4 sun-min&lt;/td&gt;
&lt;td&gt;Narrow high-rise lane, noticeably cooler, no neck burn&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Russell St → Flurys (3:15 PM)&lt;/td&gt;
&lt;td&gt;480m, 6.1 sun-min&lt;/td&gt;
&lt;td&gt;535m, 1.2 sun-min&lt;/td&gt;
&lt;td&gt;Eastern sidewalk, 4-storey colonial 1.7× shadows&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Honest limits:&lt;/strong&gt; OSM misses tarpaulins/banyan canopy (default 16m heights); glass facades reflect glare onto shade; humidity persists even in shade.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Open Innovation Matters
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Dialects need open weights&lt;/strong&gt; — closed APIs choke on &lt;em&gt;"roddur kom / dopahar 3 baje"&lt;/em&gt;; Qwen-3B + Tinker hits 100% Bengali.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Efficiency&lt;/strong&gt; — 285ms, 4.2× cheaper than 70B calls; runs on free Render.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sovereignty&lt;/strong&gt; — OSM + self-hostable, no tile billing, any Global South city can clone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Offline resilience&lt;/strong&gt; — solar math + Dijkstra + vector fallback work in dead-signal alleys.&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  My Agent Session
&lt;/h2&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%2Fcvlh47oqmk72p5kjvqry.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%2Fcvlh47oqmk72p5kjvqry.png" alt=" " width="800" height="495"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Logs in &lt;code&gt;BUILD_LOG.md&lt;/code&gt; + &lt;code&gt;results/&lt;/code&gt;)&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Best Use of Tinker ($200)
&lt;/h3&gt;

&lt;p&gt;Fine-tuned &lt;code&gt;Qwen-2.5-3B&lt;/code&gt; → &lt;code&gt;chhaya-codemixed-3b&lt;/code&gt;: 66.7%→93.3%, Bengali 100%, 285ms (3.9×), 4.2× cheaper. &lt;code&gt;scripts/tinker_finetune.py&lt;/code&gt;, &lt;code&gt;results/tinker_eval.json&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Best Use of TabPFN ($200)
&lt;/h3&gt;

&lt;p&gt;TabPFN-2 best-window &lt;code&gt;/window&lt;/code&gt;: 1.7723→0.4699°C MAE, 73.49% cut, 7,657 train / 403 held-out. &lt;code&gt;backend/best_window.py&lt;/code&gt;, &lt;code&gt;results/window_eval.json&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Best Use of Tiger Data ($100)
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;pgvector&lt;/code&gt; vibe search + offline fallback for shade lore/hal­ts. &lt;code&gt;backend/tiger_client.py&lt;/code&gt;, &lt;code&gt;/api/tiger/search&lt;/code&gt;, screenshots above.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Best Use of Mastra ($100)
&lt;/h3&gt;

&lt;p&gt;TypeScript agent &lt;code&gt;agent/src/agent.ts&lt;/code&gt;: &lt;code&gt;planRoute&lt;/code&gt;, &lt;code&gt;bestWindow&lt;/code&gt;, &lt;code&gt;tigerSearch&lt;/code&gt;, &lt;code&gt;getShadows&lt;/code&gt; over open models.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Best Use of Sentry ($100)
&lt;/h3&gt;

&lt;p&gt;FastAPI tracing: Tinker latency, extrusion time, routing bottlenecks with distributed IDs.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Best Use of ElevenLabs ($100) ⭐ HERO
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;backend/voice.py&lt;/code&gt; + voice card: natural turn-by-turn shade briefings, pocket-your-phone walking, browser fallback. The feature that makes Chhaya truly Touch Grass — see Section 5.&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion &amp;amp; What's Next
&lt;/h2&gt;

&lt;p&gt;Global South cities are heating fast. Easy tech keeps us inside on screens; hard tech gets us outside safely together.&lt;/p&gt;

&lt;p&gt;Next: crowdsourced &lt;strong&gt;Great Shade / Too Sunny&lt;/strong&gt; taps calibrating shadows with ground truth, more cities, more voices.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pick your club, select your path, join any hike, pin a card, press Listen — put the phone away and touch grass.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Your Policies Are Out of Date: How I Built a Sanity AI Agent to Catch Fact Drift</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sat, 03 Oct 2026 21:21:17 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/your-policies-are-out-of-date-how-i-built-a-sanity-ai-agent-to-catch-fact-drift-5bee</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/your-policies-are-out-of-date-how-i-built-a-sanity-ai-agent-to-catch-fact-drift-5bee</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/sanity-2026-09-16"&gt;Sanity Challenge, Path Two: Vibe-Code Something Strange&lt;/a&gt;&lt;/em&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%2Fl9gc4f7b60xx1mcjavzb.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%2Fl9gc4f7b60xx1mcjavzb.png" alt=" " width="800" height="436"&gt;&lt;/a&gt;&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;Fact Ledger&lt;/strong&gt; — an AI-assisted fact drift detection and remediation engine built on Sanity Content Lake.&lt;/p&gt;

&lt;p&gt;Here's the problem it solves, told as a scene:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;A product manager at a SaaS company decides to extend refunds from 30 days to 60 days. She opens the CMS, finds the Refund Policy page, updates it, clicks publish. Done. She sends the Slack message: &lt;em&gt;"Refund window is now 60 days, effective immediately."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;What she doesn't know: the Help Center article still says 30. The Pricing FAQ still says 30. The Onboarding Guide, the Terms of Service, the Enterprise SLA page, the Checkout confirmation modal copy — all still say 30. Six weeks later, a customer disputes a charge, screenshots the Pricing FAQ, and sends it to their lawyer.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That is &lt;strong&gt;Fact Drift&lt;/strong&gt; — and it happens quietly, constantly, in every company with more than a handful of content pages and more than one person editing them. It's not a CMS problem, it's a &lt;em&gt;structural&lt;/em&gt; problem. The number "30" is stored in twenty-three places as dead characters. There's no relationship between them. When one changes, the others don't know.&lt;/p&gt;

&lt;p&gt;Fact Ledger fixes this at the data model level.&lt;/p&gt;

&lt;p&gt;Business values — refund windows, SLA commitments, file size limits, pricing tiers, data retention periods — become &lt;strong&gt;first-class Sanity documents&lt;/strong&gt; called &lt;code&gt;fact&lt;/code&gt;s. Pages don't copy those values; they &lt;em&gt;reference&lt;/em&gt; them via a custom &lt;code&gt;factRef&lt;/code&gt; inline Portable Text annotation. When the fact document changes, every page that uses a &lt;code&gt;factRef&lt;/code&gt; renders the new value instantly, automatically, with zero editor intervention.&lt;/p&gt;

&lt;p&gt;For every page that still has the hardcoded plain text — either because it predates the system or because someone didn't know — a deterministic scanner runs on every webhook event, finds the stale copies, and raises structured &lt;code&gt;finding&lt;/code&gt; documents. An AI agent drafts the exact Sanity patch mutations to fix them. A human reviews the before/after diffs and clicks one button. Everything updates atomically in a single transaction. The audit ledger captures the whole chain.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The core principle, distilled to four words per step:&lt;/strong&gt; &lt;em&gt;Rules flag. AI drafts. Human approves. Sanity remembers.&lt;/em&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Fact Edit → Webhook → Deterministic Scanner → Finding Graph
         → AI Mutation Synthesis → Draft Release → Human Approval → Zero Drift
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  The 5 Scanner Rules (Zero AI Involved)
&lt;/h3&gt;

&lt;p&gt;This is where the design gets interesting. The scanner is &lt;strong&gt;pure deterministic TypeScript&lt;/strong&gt; — no model calls, no embeddings, no fuzzy matching libraries. It runs in milliseconds and produces findings with exact block keys and character offsets.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Rule&lt;/th&gt;
&lt;th&gt;What it catches&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;R1 — Unlinked Match&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Plain text &lt;code&gt;"30 days"&lt;/code&gt; where a &lt;code&gt;factRef&lt;/code&gt; should be&lt;/td&gt;
&lt;td&gt;The most common drift; editors hardcode values without realising&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;R2 — Contradiction&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Text says &lt;code&gt;"60 days"&lt;/code&gt; while the canonical fact says &lt;code&gt;30&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Catches the pages that were &lt;em&gt;partially&lt;/em&gt; updated manually&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;R3 — Deprecated Reference&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;A &lt;code&gt;factRef&lt;/code&gt; pointing to a fact marked &lt;code&gt;deprecated&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Catches linked pages when a fact is retired, not just changed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;R4 — Orphan Fact&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;An active fact exists in Sanity but zero pages reference it&lt;/td&gt;
&lt;td&gt;Surfaces forgotten policies that have drifted into irrelevance&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;R5 — Temporal Violation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;A &lt;code&gt;factRef&lt;/code&gt; pointing to a fact outside its &lt;code&gt;effectiveFrom/Until&lt;/code&gt; range&lt;/td&gt;
&lt;td&gt;Catches seasonal pricing or time-bound policies used out of window&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Run the benchmark against the seeded dataset of 31 planted violations: &lt;strong&gt;100% precision, 100% recall&lt;/strong&gt;. Every planted issue found, zero false positives. That's not a marketing number — the &lt;code&gt;seed/groundTruth.ts&lt;/code&gt; file has the exact expected findings per page, and the benchmark runner verifies against them on every run.&lt;/p&gt;

&lt;p&gt;The precision comes from a design decision in R2: the &lt;strong&gt;proximity window&lt;/strong&gt;. Instead of flagging any number that contradicts the fact value anywhere on the page (which would catch phone numbers, copyright years, and table row counts), R2 only flags numbers that appear within N characters of the fact's &lt;em&gt;label&lt;/em&gt; in the text. That single detail is the difference between a rule that's useful and one that's noise.&lt;/p&gt;


&lt;h3&gt;
  
  
  The Workflow
&lt;/h3&gt;

&lt;p&gt;Once findings exist in Sanity, the AI remediation agent kicks in. It fetches the page's Portable Text, locates the exact block and character span identified by the scanner, slices out the stale text, and generates a valid Sanity patch mutation — the kind you'd write by hand if you were doing this manually, except it does it for twenty pages in the time it takes to refresh the dashboard.&lt;/p&gt;

&lt;p&gt;All of this goes into a &lt;code&gt;remediation&lt;/code&gt; document: a structured release with a &lt;code&gt;fixes&lt;/code&gt; array where each item carries &lt;code&gt;beforeText&lt;/code&gt;, &lt;code&gt;afterText&lt;/code&gt;, the raw patch JSON, and an &lt;code&gt;approved&lt;/code&gt; boolean the editor can toggle.&lt;/p&gt;

&lt;p&gt;In Sanity Studio, there's a custom &lt;strong&gt;"Apply Fixes &amp;amp; Publish"&lt;/strong&gt; document action on the &lt;code&gt;remediation&lt;/code&gt; type. The editor reads through the diffs. They can approve or reject individual fixes. When they're satisfied, one click fires a &lt;code&gt;client.transaction()&lt;/code&gt; that atomically:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;patches every affected page&lt;/li&gt;
&lt;li&gt;flips every linked finding to &lt;code&gt;fixed&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;publishes the remediation document itself&lt;/li&gt;
&lt;li&gt;writes an immutable &lt;code&gt;changeEvent&lt;/code&gt; to the audit ledger&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No partial states. No "we fixed 17 of 21 pages and then the tab closed." All twenty-one pages update in the same transaction or none of them do. The Drift Score on the dashboard drops back to zero and stays there — until the next fact changes.&lt;/p&gt;


&lt;h3&gt;
  
  
  🌟 Key Features (The App SDK Experience)
&lt;/h3&gt;

&lt;p&gt;The Next.js dashboard at &lt;code&gt;https://fact-ledger.onrender.com/dashboard&lt;/code&gt; is a live, interactive layer on top of Content Lake. It isn't just a read-only frontend — it's a full &lt;strong&gt;App SDK Control Center&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. The Clause Impact Tree&lt;/strong&gt;&lt;br&gt;
When a policy changes, officials don't just see a list of broken pages. They see a &lt;strong&gt;cascading change graph&lt;/strong&gt;. The Clause Impact Tree visualizes exactly how a single canonical fact ripples outward across the entire corporate document graph, showing nodes turning red in real-time as the webhook fires.&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%2F9d761e2148rf8lsykuj3.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%2F9d761e2148rf8lsykuj3.png" alt=" " width="799" height="684"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The Live Control Center &amp;amp; Charts&lt;/strong&gt;&lt;br&gt;
Every number and graph on the dashboard comes from a live GROQ query. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The KPI Row:&lt;/strong&gt; Tracks current Drift Score, total facts, scanned pages, and overall health.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Resolution Health Chart:&lt;/strong&gt; A before-vs-after breakdown showing open findings vs fixed findings across releases.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Heatmap:&lt;/strong&gt; A CSS grid visualizing Fact × Page drift anomalies. Red for drift, green for clean.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interactive Triage:&lt;/strong&gt; Editors can approve or dismiss findings directly from the dashboard table. The API route patches the finding document in Sanity immediately, and the table re-queries live without reloading.&lt;/li&gt;
&lt;/ul&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%2Ftdrqcnnveovq5bt3vs9s.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%2Ftdrqcnnveovq5bt3vs9s.png" alt=" " width="799" height="675"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. The Employee Voice Portal&lt;/strong&gt;&lt;br&gt;
Policy confusion doesn't only flow downward. Employees and customers notice stale policies first. The &lt;strong&gt;Employee Voice&lt;/strong&gt; portal gives that signal a home. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Employees can submit policy complaints or questions.&lt;/li&gt;
&lt;li&gt;These submissions are stored as &lt;code&gt;complaint&lt;/code&gt; or &lt;code&gt;policyQuestion&lt;/code&gt; documents directly in Sanity.&lt;/li&gt;
&lt;li&gt;Officials see every submission in Sanity Studio right next to the open findings. When an employee asks, &lt;em&gt;"Why does the checkout page say 30 days but I was told 60?"&lt;/em&gt;, the complaint lives right next to the scanner finding that explains exactly why.&lt;/li&gt;
&lt;/ul&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%2Fi635q6h78ah03xe9y4tn.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%2Fi635q6h78ah03xe9y4tn.png" alt=" " width="800" height="478"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/Z-wFpxGywfg" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Live Dashboard:&lt;/strong&gt; &lt;code&gt;https://fact-ledger.onrender.com/dashboard&lt;/code&gt;&lt;br&gt;
&lt;strong&gt;Sanity Studio:&lt;/strong&gt; &lt;code&gt;https://pritam.sanity.studio/&lt;/code&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3&gt;
  
  
  The Full Loop in 60 Seconds
&lt;/h3&gt;

&lt;p&gt;Here is how the system actually looks in practice when a fact changes:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. The Trigger&lt;/strong&gt;&lt;br&gt;
An editor changes the &lt;code&gt;Cancellation Policy&lt;/code&gt; fact value from &lt;code&gt;60&lt;/code&gt; to &lt;code&gt;30&lt;/code&gt; in Sanity Studio.&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%2Fw7f5f30gy4chwfvwy5ye.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%2Fw7f5f30gy4chwfvwy5ye.png" alt=" " width="799" height="465"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The Detection&lt;/strong&gt;&lt;br&gt;
The webhook fires. The scanner runs R1–R5 across all pages. The dashboard Drift Score jumps and the KPI pulses red.&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%2Fco5pwgbb4mn0pk09fbwt.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%2Fco5pwgbb4mn0pk09fbwt.png" alt=" " width="800" height="460"&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%2Fvx2omow2zqkfie6g98i9.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%2Fvx2omow2zqkfie6g98i9.png" alt=" " width="800" height="465"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. The Remediation Draft&lt;/strong&gt;&lt;br&gt;
Clicking "Draft AI Remediation" triggers the AI to draft exact before/after patches for all stale spans.&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%2Fxj51v75l65imkc3h96it.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%2Fxj51v75l65imkc3h96it.png" alt=" " width="800" height="416"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. The Human Approval&lt;/strong&gt;&lt;br&gt;
The editor opens the Remediation Release in Studio, reads through the diffs, and clicks "Apply Fixes &amp;amp; Publish".&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%2Frsbxon4lqht2f1xdc1a1.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%2Frsbxon4lqht2f1xdc1a1.png" alt=" " width="800" height="466"&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%2Fu8gmvo7r1ri0lajtri0e.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%2Fu8gmvo7r1ri0lajtri0e.png" alt=" " width="800" height="468"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. The Resolution&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;client.transaction()&lt;/code&gt; commits. All pages are patched atomically, findings flip to fixed, and the Drift Score returns to 0.&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%2Fwn5tv2j5jpzy300a33n2.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%2Fwn5tv2j5jpzy300a33n2.png" alt=" " width="800" height="462"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/sanity" rel="noopener noreferrer"&gt;
        sanity
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div&gt;
  &lt;a rel="noopener noreferrer" href="https://github.com/Pritam-mb/sanity/./docs/Screenshot%202026-10-04%20014137.png"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FPritam-mb%2Fsanity%2FHEAD%2F.%2Fdocs%2FScreenshot%25202026-10-04%2520014137.png" alt="Fact Ledger Hero" width="100%"&gt;&lt;/a&gt;
  &lt;br&gt;
  &lt;br&gt;
  &lt;p&gt;
    &lt;b&gt;An AI-assisted fact drift detection engine built on Sanity Content Lake.&lt;/b&gt;
  &lt;/p&gt;
  &lt;p&gt;
    &lt;a href="https://fact-ledger.onrender.com" rel="nofollow noopener noreferrer"&gt;Live Demo&lt;/a&gt; •
    &lt;a href="https://pritam.sanity.studio" rel="nofollow noopener noreferrer"&gt;Sanity Studio&lt;/a&gt; •
    &lt;a href="https://github.com/Pritam-mb/sanity#setup" rel="noopener noreferrer"&gt;Installation&lt;/a&gt;
  &lt;/p&gt;
&lt;/div&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;🛑 The Problem: Fact Drift&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;A product manager at a SaaS company decides to extend refunds from 30 days to 60 days. She opens the CMS, updates the Refund Policy page, and clicks publish. What she doesn't know: the Help Center article still says 30. The Pricing FAQ still says 30. The Onboarding Guide, the Terms of Service, the Enterprise SLA page, the Checkout confirmation modal copy — &lt;strong&gt;all still say 30.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;That is Fact Drift.&lt;/strong&gt; The number "30" is stored in twenty-three places as dead characters. There's no relationship between them. When one changes, the others don't know.&lt;/p&gt;

&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;💡 The Solution: Fact Ledger&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;Fact Ledger fixes this at the data model level. Business values become &lt;strong&gt;first-class Sanity documents&lt;/strong&gt; (&lt;code&gt;facts&lt;/code&gt;). Pages don't copy those values; they reference them.&lt;/p&gt;

&lt;p&gt;For every…&lt;/p&gt;&lt;/div&gt;


&lt;/div&gt;
&lt;br&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/sanity" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;
&lt;br&gt;&lt;br&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;fact-ledger/
├── studio/     # Sanity Studio v3 — 13 schema types, custom structure, Document Action
├── web/        # Next.js 16 App Router — Drift Dashboard + API routes
├── scanner/    # Pure TypeScript R1–R5 + Vitest unit tests
├── seed/       # Idempotent seed script (facts, pages, ground truth)
└── bench/      # Benchmark runner — writes benchmarkResult docs to Sanity
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;&lt;strong&gt;Sanity Project ID:&lt;/strong&gt; &lt;code&gt;tmics7hc&lt;/code&gt; (dataset: &lt;code&gt;fact-ledger&lt;/code&gt;)&lt;/p&gt;


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

&lt;p&gt;I used &lt;strong&gt;Antigravity IDE&lt;/strong&gt; (Google DeepMind) as my primary AI-native IDE, with its browser agent running alongside for live validation and UI feedback during development.&lt;/p&gt;
&lt;h3&gt;
  
  
  How it started
&lt;/h3&gt;

&lt;p&gt;I came into this with a real problem in mind — not a contrived demo. The scenario of "fact changes in one place, stays stale everywhere else" has bitten real teams I've worked with. I wanted to see if a vibe-coded system could actually address it with structural rigor, not just vibes.&lt;/p&gt;

&lt;p&gt;My opening prompt was deliberately ambitious:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Build a closed-loop fact drift detection system on Sanity. Facts are first-class documents. Pages reference them with custom Portable Text inline objects. A deterministic scanner runs on webhook triggers and creates finding documents. An AI agent synthesizes patch mutations. A human approves via a custom Studio document action. Everything is audited. The LLM never publishes anything."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That single prompt produced the full schema architecture, the &lt;code&gt;factRef&lt;/code&gt; Portable Text annotation type, and an initial scanner skeleton in one pass. What struck me: the model correctly inferred the key constraint on its own — &lt;em&gt;no unsupervised publishing&lt;/em&gt; — and every design decision that followed was shaped by that constraint without me having to repeat it. It understood why the LLM's role should be limited to drafting, not deciding.&lt;/p&gt;
&lt;h3&gt;
  
  
  Prompts that worked
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Schema design:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Design a &lt;code&gt;fact&lt;/code&gt; schema for Sanity with: key (slug), label, value, unit, aliases (array of strings for surface-form matching), owner (reference to person), dependsOn (self-referential array), effectiveFrom/Until (dates), status (active/deprecated), and a highStakes flag."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The &lt;code&gt;aliases&lt;/code&gt; field is what makes the whole system actually useful in practice. Without it, the scanner could only catch exact matches like &lt;code&gt;"30 days"&lt;/code&gt;. With it, each fact document carries its own list of surface forms: &lt;code&gt;["30 days", "thirty (30) days", "one month", "30 calendar days"]&lt;/code&gt;. R1 matches any of them. That's how you catch the policy writer who wrote "one month" in the terms and the marketing person who wrote "thirty days" in the campaign landing page — same fact, same finding, zero NLP required.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;highStakes&lt;/code&gt; flag is a quiet but important detail: facts marked high-stakes require two human approvers in the remediation workflow. One person can't unilaterally ship a fix to the refund policy affecting twenty pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scanner architecture:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Write the 5 scanner rules as pure TypeScript functions. Zero dependencies. Zero AI. Take facts and Portable Text blocks as input, return findings with exact block key, child key, start offset, and end offset."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The model got genuinely clever here. For R2 (contradiction detection), it implemented a &lt;strong&gt;proximity window&lt;/strong&gt; — a contradictory number only fires as a finding if it appears within N characters of the fact's label in the text body. That design decision alone is what separates a useful rule from a useless one. A naive implementation would flag every number on every page. This one only flags the ones that are contextually near the fact's label, which is where contradictions actually matter.&lt;/p&gt;

&lt;p&gt;Running &lt;code&gt;npm run bench&lt;/code&gt; against the 31 planted issues: &lt;strong&gt;31 found, 0 false positives&lt;/strong&gt;. That's a real validation, not a demo.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The custom document action:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Write a Sanity Studio document action for the remediation type. Label: 'Apply Fixes &amp;amp; Publish'. Filter for approved=true fixes, parse each mutation JSON, build a client.transaction() that patches every page, flips findings to fixed, publishes the remediation doc, writes a changeEvent. Atomic commit."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This came out nearly correct on the first pass. The model chose &lt;code&gt;client.transaction()&lt;/code&gt; without prompting — it understood on its own that sequential patches would create a window where some pages are fixed and others aren't. That matters: if the tab closes halfway through twenty patches, you're left with a half-consistent dataset and no way to know which pages were updated. A transaction is all-or-nothing. The model knew that.&lt;/p&gt;
&lt;h3&gt;
  
  
  Prompts that didn't work
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Sanity Functions as the webhook handler.&lt;/strong&gt; The model scaffolded a genuinely clean Sanity Function — right structure, right exports, correct handler signature. Then I went to deploy it and hit the plan wall: Sanity Functions require a paid upgrade. Beautiful code, zero utility at my tier. The fallback was a Next.js API route, which actually turned out cleaner: scanner and webhook in the same process, easier to debug, no cold start latency.&lt;/p&gt;

&lt;p&gt;The lesson: &lt;em&gt;beautiful code requiring a plan upgrade isn't code you can ship.&lt;/em&gt; We fell back, and the fallback shipped.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Auto-generating seed data.&lt;/strong&gt; My first two attempts at generating realistic policy pages with planted drift violations produced pages where every violation was placed inside a heading element. Headings in Portable Text don't have child span arrays the way body blocks do — so the scanner couldn't see them. Completely valid Sanity documents, completely invisible to R1–R4.&lt;/p&gt;

&lt;p&gt;The fix was to be brutally explicit:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"All planted violations must be inside Portable Text body blocks with at least 2 child spans. Include exact byte offsets in the ground truth file so the benchmark can verify TP/FP/FN."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;After that, &lt;code&gt;seed/groundTruth.ts&lt;/code&gt; became the source of truth for the benchmark. Every time you run &lt;code&gt;npm run bench&lt;/code&gt;, it checks the scanner's output against those exact expected findings. If someone breaks a rule, the benchmark fails — not gracefully, loudly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The heatmap.&lt;/strong&gt; Describing the Fact × Page heatmap in prose got me a Recharts cell chart with tiles so small you needed a magnifying glass. The breakthrough was switching from describing &lt;em&gt;what it should look like&lt;/em&gt; to describing &lt;em&gt;how it should be built&lt;/em&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Implement this as a CSS grid. Rows = facts, columns = pages. Each cell: red background if open findings exist for that combo, green if clean. No charting library — plain CSS grid. Title attributes for hover tooltips."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One pass, done. The lesson: when the output is wrong, don't describe the outcome differently — describe the implementation.&lt;/p&gt;
&lt;h3&gt;
  
  
  Reaching past the Studio
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Workflows as data.&lt;/strong&gt; The &lt;code&gt;remediation&lt;/code&gt; schema &lt;em&gt;is&lt;/em&gt; the workflow document. Status transitions: &lt;code&gt;draft → pending_review → approved → published&lt;/code&gt;. Each transition is a Sanity patch. Every state is queryable in GROQ. The AI agent advances the document to &lt;code&gt;pending_review&lt;/code&gt;. A human editor reviews and advances to &lt;code&gt;published&lt;/code&gt; via the custom document action. If they're not ready, the document sits at &lt;code&gt;pending_review&lt;/code&gt; indefinitely — visible in the Studio sidebar under "Remediation Releases" with a running count of unapproved fixes. Nothing gets lost. Nothing gets auto-published.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A real-time custom interface.&lt;/strong&gt; The dashboard is not read-only. Editors can approve or dismiss individual findings directly from the &lt;code&gt;/findings&lt;/code&gt; table — the action patches Sanity and the table refreshes with the new state. The Drift Score pulses visually when non-zero. It's a small UX decision, but it matters: you want people to &lt;em&gt;feel&lt;/em&gt; the urgency of a non-zero drift score, not just read a number.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Employee Voice portal.&lt;/strong&gt; A late addition in Session 3, prompted into existence in a single session. Policy confusion doesn't only flow downward — employees and customers notice it first and report it through informal channels (Slack, email, support tickets) that never get structured or tracked. The portal gives that signal a home in the same Content Lake. A complaint about a confusing refund promise routes directly into a &lt;code&gt;complaint&lt;/code&gt; document in Sanity; the editor sees it in Studio next to the open findings for that fact. The problem and its reports live in the same place.&lt;/p&gt;

&lt;p&gt;Three schema types, three Studio sidebar sections, five Next.js routes — roughly 45 minutes from prompt to running.&lt;/p&gt;
&lt;h3&gt;
  
  
  What surprised me
&lt;/h3&gt;

&lt;p&gt;The model never once suggested putting the LLM in the approval loop. Even when I described the remediation flow in ways that left room for autonomous action, it consistently added a &lt;code&gt;canPublish&lt;/code&gt; guard, an &lt;code&gt;approved&lt;/code&gt; boolean per fix, and explicit before/after text fields for human review. The safety architecture emerged from the model's understanding of the design, not from me specifying every guardrail.&lt;/p&gt;

&lt;p&gt;The GROQ queries were also clean on first generation — almost no iteration needed. GROQ's declarative shape maps well onto how the model reasons about data: you describe the shape you want, not the traversal you'd write in SQL. When the output is wrong in SQL, you debug joins. When GROQ output is wrong, you usually just re-describe the shape. The model seems to prefer describing shapes.&lt;/p&gt;

&lt;p&gt;The most important moment: the model wrote an elegant Sanity Function. I had to explain that elegance and deployability aren't the same thing. The fallback shipped. The elegant version sits in a comment block as a note for when the plan gets upgraded.&lt;/p&gt;

&lt;p&gt;That's the honest build: seven and a half hours, a real problem, a model that got most of it right, a few walls we had to route around, and a system that actually works.&lt;/p&gt;


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

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Project ID:&lt;/strong&gt; &lt;code&gt;tmics7hc&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dataset:&lt;/strong&gt; &lt;code&gt;fact-ledger&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Schema types:&lt;/strong&gt; &lt;code&gt;fact&lt;/code&gt;, &lt;code&gt;factRef&lt;/code&gt; (custom Portable Text annotation), &lt;code&gt;page&lt;/code&gt;, &lt;code&gt;finding&lt;/code&gt;, &lt;code&gt;scanRun&lt;/code&gt;, &lt;code&gt;remediation&lt;/code&gt;, &lt;code&gt;changeEvent&lt;/code&gt;, &lt;code&gt;benchmarkResult&lt;/code&gt;, &lt;code&gt;complaint&lt;/code&gt;, &lt;code&gt;policyQuestion&lt;/code&gt;, &lt;code&gt;policyUpdate&lt;/code&gt;, &lt;code&gt;person&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Custom Studio features:&lt;/strong&gt; custom desk structure (Facts / Pages / Open Findings / Remediation Releases / Employee Voice / Audit Log), custom document action "Apply Fixes &amp;amp; Publish" (&lt;code&gt;PublishRemediationAction.ts&lt;/code&gt;), visionTool for GROQ exploration&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Webhooks:&lt;/strong&gt; fact and page publish events trigger &lt;code&gt;/api/webhook&lt;/code&gt; → scanner → finding creation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transactions:&lt;/strong&gt; remediation publishing uses &lt;code&gt;client.transaction()&lt;/code&gt; for atomic multi-document patches&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TypeGen:&lt;/strong&gt; &lt;code&gt;sanity typegen generate&lt;/code&gt; in &lt;code&gt;studio/&lt;/code&gt; — all GROQ queries are fully typed&lt;/li&gt;
&lt;/ul&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%2Fqb5rrbuvyyjjj9mexhfo.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%2Fqb5rrbuvyyjjj9mexhfo.png" alt=" " width="800" height="492"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Agent Session
&lt;/h2&gt;

&lt;p&gt;Built with &lt;strong&gt;Antigravity IDE&lt;/strong&gt; (Google DeepMind) over three sessions, roughly 7.5 hours total.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Session 1&lt;/strong&gt; (~2.5 hrs): schema design, &lt;code&gt;factRef&lt;/code&gt; annotation, scanner R1–R5, seed script&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Session 2&lt;/strong&gt; (~3 hrs): dashboard panels P1–P6, API routes, webhook handler, benchmark runner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Session 3&lt;/strong&gt; (~2 hrs): Studio structure, "Apply Fixes &amp;amp; Publish" action, Employee Voice portal, audit ledger, polish&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The model wrote the large majority of the TypeScript. My role was architect, reviewer, and the person who hit pricing walls so you don't have to.&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%2Fwvm9fvmw3y10d9wuaiiy.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%2Fwvm9fvmw3y10d9wuaiiy.png" alt=" " width="800" height="475"&gt;&lt;/a&gt;&lt;/p&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/sanity" rel="noopener noreferrer"&gt;
        sanity
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div&gt;
  &lt;a rel="noopener noreferrer" href="https://github.com/Pritam-mb/sanity/./docs/Screenshot%202026-10-04%20014137.png"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fraw.githubusercontent.com%2FPritam-mb%2Fsanity%2FHEAD%2F.%2Fdocs%2FScreenshot%25202026-10-04%2520014137.png" alt="Fact Ledger Hero" width="100%"&gt;&lt;/a&gt;
  &lt;br&gt;
  &lt;br&gt;
  &lt;p&gt;
    &lt;b&gt;An AI-assisted fact drift detection engine built on Sanity Content Lake.&lt;/b&gt;
  &lt;/p&gt;
  &lt;p&gt;
    &lt;a href="https://fact-ledger.onrender.com" rel="nofollow noopener noreferrer"&gt;Live Demo&lt;/a&gt; •
    &lt;a href="https://pritam.sanity.studio" rel="nofollow noopener noreferrer"&gt;Sanity Studio&lt;/a&gt; •
    &lt;a href="https://github.com/Pritam-mb/sanity#setup" rel="noopener noreferrer"&gt;Installation&lt;/a&gt;
  &lt;/p&gt;
&lt;/div&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;🛑 The Problem: Fact Drift&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;A product manager at a SaaS company decides to extend refunds from 30 days to 60 days. She opens the CMS, updates the Refund Policy page, and clicks publish. What she doesn't know: the Help Center article still says 30. The Pricing FAQ still says 30. The Onboarding Guide, the Terms of Service, the Enterprise SLA page, the Checkout confirmation modal copy — &lt;strong&gt;all still say 30.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;That is Fact Drift.&lt;/strong&gt; The number "30" is stored in twenty-three places as dead characters. There's no relationship between them. When one changes, the others don't know.&lt;/p&gt;

&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;💡 The Solution: Fact Ledger&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;Fact Ledger fixes this at the data model level. Business values become &lt;strong&gt;first-class Sanity documents&lt;/strong&gt; (&lt;code&gt;facts&lt;/code&gt;). Pages don't copy those values; they reference them.&lt;/p&gt;

&lt;p&gt;For every…&lt;/p&gt;&lt;/div&gt;


&lt;/div&gt;
&lt;br&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/sanity" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;br&gt;
&lt;/div&gt;
&lt;br&gt;


&lt;h2&gt;
  
  
  👥 The Team
&lt;/h2&gt;

&lt;p&gt;Our team came together for the International Charity Day DEV Challenge to build NeedFeed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pritam Patra&lt;a href="https://dev.to/pritam_patra_429a25dedae6"&gt;@pritam_patra_429a25dedae6&lt;/a&gt; ( Developer)&lt;/li&gt;
&lt;li&gt;Sourish Panda&lt;a href="https://dev.to/t-rexbytes"&gt;@t-rexbytes&lt;/a&gt; ( Developer)&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>sanitychallenge</category>
      <category>sanity</category>
      <category>ai</category>
    </item>
    <item>
      <title>OmniML: We Built an AutoML System That Refuses to Be a Black Box</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Tue, 22 Sep 2026 09:17:49 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/omniml-human-in-the-loop-automl-with-langgraph-groq-and-chainlit-3g36</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/omniml-human-in-the-loop-automl-with-langgraph-groq-and-chainlit-3g36</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/mlh-hackathon"&gt;MLH x DEV Writing Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  OmniML: An AutoML Pipeline That Actually Asks Before It Decides
&lt;/h1&gt;

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

&lt;p&gt;Most AutoML tools operate as complete black boxes. You feed in a dataset, a brute-force search algorithm churns away behind closed doors, and out comes a model with zero explanation, no room for expert intervention, and no consideration for regulatory standards like the EU AI Act or FDA Software-as-a-Medical-Device (SaMD) guidelines. That opacity is exactly what my team set out to fix.&lt;/p&gt;

&lt;p&gt;At HackTropica, we built &lt;strong&gt;OmniML&lt;/strong&gt; — an open-source, full-stack, autonomous machine learning system that keeps a human explicitly in the loop at every critical decision point. Orchestrated with LangGraph, powered by Groq's &lt;code&gt;openai/gpt-oss-120b&lt;/code&gt; for fast reasoning, and wrapped in an interactive Chainlit UI, OmniML turns a plain-English request into a fully trained, compliance-checked, and deployment-ready ML model, sourcing real datasets from Kaggle along the way.&lt;/p&gt;

&lt;p&gt;The pipeline runs through a chain of dedicated stages, and at five separate checkpoints it pauses and hands control back to the user before proceeding. The architect agent first proposes a baseline model graph from the problem statement, which the user can then visually edit through an embedded React Flow canvas before anything is compiled. From there, the system searches, ranks, and downloads a real tabular dataset via the Kaggle API, profiles it for feature distributions and data quality, and surfaces that analysis for review. The user then configures hyperparameters, fairness settings, and compliance mode, and makes an explicit choice between local and cloud compute before training is ever allowed to start. Once training resumes, an engineer and debugger agent pair generates deterministic training code, validates it, and executes it in a sandboxed environment while streaming real-time logs and metrics back to the UI. The final stage produces SHAP and LIME explainability outputs, fairness benchmarks, and a full compliance report formatted against EU AI Act and FDA SaMD guidance, alongside a production-ready deployment bundle.&lt;/p&gt;

&lt;p&gt;One design decision I'm particularly proud of is supporting two distinct training paths depending on the problem. Path B, which is the default, uses scikit-learn for fast tabular, text, or image training via grid search over a featurized CSV. Path A compiles the user-approved React Flow graph directly into a custom &lt;code&gt;OmniMLNet&lt;/code&gt; PyTorch module and trains it with real epoch-level metrics, which is useful when someone actually wants to reason about network architecture rather than just get a fast baseline. OmniML also grounds its architecture decisions in real research: before training begins, an agent pulls relevant literature and produces a gap-analysis comparing the current dataset, task, and proposed architecture against published methodologies, so the user can see exactly where their setup diverges from established approaches in the field. Every run is also fully reproducible: each execution persists to &lt;code&gt;runs/&amp;lt;run_id&amp;gt;/manifest.json&lt;/code&gt; as a complete evidence bundle covering artifacts, plots, logs, and reports, all downloadable and normalized for later benchmarking.&lt;/p&gt;

&lt;p&gt;Here's the high-level flow end to end:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User Query
  └─► Architecture generation
        └─► HITL architecture editor (React Flow)
              └─► Dataset sourcing and ranking (Kaggle)
                    └─► HITL dataset selection
                          └─► Dataset download + validation
                                └─► Drift sentry
                                      └─► EDA profiling
                                            └─► HITL training configuration
                                                  └─► HITL compute strategy
                                                        └─► Hyperparameter tuning + deterministic code generation
                                                              └─► Code validation &amp;amp; self-healing
                                                                    └─► Execution sandbox
                                                                          └─► XAI / benchmark / fairness / compliance
                                                                                └─► Deployment dashboard + downloadable reports
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What I learned building this had less to do with the ML itself and more to do with orchestration. Getting an LLM-driven agent graph to pause reliably at a UI checkpoint, hold state correctly, and resume exactly where it left off — without losing context or re-triggering earlier stages — turned out to be the hardest engineering problem in the whole project, harder than anything on the modeling side.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;Here's the full walkthrough of OmniML running end to end, including the interactive HITL graph editor, live dataset profiling, and compliance report generation:&lt;/p&gt;

&lt;h2&gt;
  
  
  🎬 Video Demo
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/dNsuma_PQ9g" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;br&gt;
&lt;strong&gt;🔗 GitHub Repository:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/hacktropica" rel="noopener noreferrer"&gt;https://github.com/Pritam-mb/hacktropica&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Visual Architecture Editor (HITL Checkpoint)
&lt;/h3&gt;

&lt;p&gt;The embedded React Flow visual editor inside Chainlit lets you visually refine a proposed neural network topology before it's compiled into a trainable model:&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%2F4bkl533mx9kkdgos1ugu.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%2F4bkl533mx9kkdgos1ugu.png" alt=" " width="800" height="545"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Pipeline Walkthrough in Screenshots
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1. EDA Profiling Dashboard.&lt;/strong&gt; After a dataset is sourced from Kaggle, OmniML runs it through an automated profiling stage that surfaces missing values, feature distributions with skewness stats, and categorical feature breakdowns — all before the user is asked to approve moving forward:&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%2Fuo3v7tclhdjizluajito.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%2Fuo3v7tclhdjizluajito.png" alt=" " width="800" height="501"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Outlier Detection, Correlation Analysis &amp;amp; AI Data Insights.&lt;/strong&gt; The same EDA stage flags outliers using IQR fencing, ranks the strongest feature-to-feature correlations, renders a full correlation heatmap, and closes with a natural-language summary generated by Groq — explaining data quality issues and how the dataset maps to its likely source (in this run, correctly identifying it as the Wisconsin Breast Cancer Diagnostic dataset):&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%2Fzppkglbe0vlb9d56vj4x.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%2Fzppkglbe0vlb9d56vj4x.png" alt=" " width="800" height="387"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Training Configuration (HITL Checkpoint).&lt;/strong&gt; Before any training runs, the user is handed an interactive configuration panel to set epochs, test split, batch size, learning rate, optimizer, and regularization settings — with quick presets for fast debug runs versus deep, balanced, or overfit-test configurations:&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%2Fh14hen5rmbcs163twfqg.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%2Fh14hen5rmbcs163twfqg.png" alt=" " width="800" height="626"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Live Training Progress.&lt;/strong&gt; Once training is launched, OmniML streams real epoch metrics back into the chat as live loss and accuracy curves, alongside a running Groq-generated observation of what's happening in the training dynamics — in this case flagging a plateau in validation loss and suggesting the learning rate may be too high for further fine-tuning:&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%2Fpt192ae4o23mztjbamg4.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%2Fpt192ae4o23mztjbamg4.png" alt=" " width="800" height="921"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Literature Comparison &amp;amp; Gap Analysis.&lt;/strong&gt; Before the pipeline finalizes an architecture, an agent cross-references the task and dataset against relevant published research, summarizing methodologies from comparable papers and calling out where the current setup diverges from established approaches in the literature:&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%2Fa0laemdrxmj5gmuct64h.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%2Fa0laemdrxmj5gmuct64h.png" alt=" " width="800" height="1007"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Try It Yourself
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/Pritam-mb/hacktropica.git
&lt;span class="nb"&gt;cd &lt;/span&gt;hacktropica

python &lt;span class="nt"&gt;-m&lt;/span&gt; venv venv
&lt;span class="nb"&gt;source &lt;/span&gt;venv/bin/activate   &lt;span class="c"&gt;# Windows: venv\Scripts\activate&lt;/span&gt;

pip &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; requirements.txt
&lt;span class="nb"&gt;cp&lt;/span&gt; .env.example .env       &lt;span class="c"&gt;# then fill in GROQ_API_KEY, KAGGLE_USERNAME, KAGGLE_KEY, CHAINLIT_AUTH_SECRET&lt;/span&gt;

python start.py
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then open &lt;code&gt;http://localhost:8001&lt;/code&gt; and try a prompt like &lt;em&gt;"Diagnose breast cancer from biopsy records"&lt;/em&gt; or &lt;em&gt;"Detect credit card fraud from transaction telemetry."&lt;/em&gt; Runtime diagnostics — Groq auth status, Kaggle CLI resolution, credential checks — are available at &lt;code&gt;http://localhost:8001/runtime-diagnostics&lt;/code&gt; if anything needs debugging.&lt;/p&gt;

&lt;h2&gt;
  
  
  Partner Technologies
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Groq (&lt;code&gt;openai/gpt-oss-120b&lt;/code&gt;)&lt;/strong&gt; is the reasoning engine behind almost every intelligent decision in OmniML: generating the initial model architecture from a natural-language prompt, ranking candidate Kaggle datasets, writing deterministic training code, self-healing that code when validation fails, and generating live natural-language commentary during training (as shown in the screenshots above). What made Groq stand out for this specific project was inference latency. Because OmniML's architecture involves an LLM call at nearly every stage transition in a multi-agent LangGraph state machine, using a slower inference provider would have made the human-in-the-loop experience feel sluggish and would have broken the sense that you're interacting with a live system rather than waiting on a batch job. Groq's speed meant the architect agent could regenerate a model graph, or the debugger agent could rewrite a failing script, fast enough that the checkpoint-and-resume UX in Chainlit felt responsive rather than like a loading screen. Swapping in the &lt;code&gt;openai/gpt-oss-120b&lt;/code&gt; model specifically gave us a good balance between reasoning quality for code generation tasks and the raw throughput Groq's hardware provides.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chainlit&lt;/strong&gt; is the backbone of the entire user-facing experience. Rather than building a custom frontend from scratch, we used Chainlit's message and element system to embed custom React components — the React Flow architecture editor, the EDA profiling dashboard, the training console, and the deployment dashboard — directly inside a chat interface. The interesting implementation challenge was making Chainlit's async message flow pause execution and wait on user interaction from an embedded custom element, rather than just displaying static content. We used Chainlit's action and custom-element callback system to bridge state from the frontend graph editor back into the LangGraph execution state, so a user's edits to the visual canvas actually mutate the architecture object that gets compiled downstream. Working with Chainlit's extensibility for custom JS/React elements alongside a Python-native backend was one of the more rewarding parts of the stack.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Kaggle API&lt;/strong&gt; powers structured dataset discovery, evaluation, and automated ingest — letting the agent search, rank, and validate real-world tabular datasets against the user's problem statement without any manual dataset hunting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;PyTorch, Optuna &amp;amp; Scikit-Learn&lt;/strong&gt; drive graph compilation, hyperparameter search, and model execution across both the sklearn (Path B) and PyTorch (Path A) training routes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hackathon Experience
&lt;/h2&gt;

&lt;p&gt;We attended &lt;strong&gt;HackTropica&lt;/strong&gt; on &lt;strong&gt;5th April 2026&lt;/strong&gt; at &lt;strong&gt;Asansol Engineering College&lt;/strong&gt;. The energy in the hall was electric from the moment we walked in—hundreds of developers, whiteboards filled with architecture diagrams, and a clear challenge in the air to build something truly transformative.&lt;/p&gt;

&lt;p&gt;Building &lt;strong&gt;AxisVision OmniML&lt;/strong&gt; under a tight deadline was both thrilling and intense. A pivotal part of our journey was the guidance we received from &lt;strong&gt;Prof. Tridib Chakraborty&lt;/strong&gt;. His mentorship helped us sharpen our system design, pushing us to ensure our Human-in-the-Loop (HITL) workflow was seamless, robust, and genuinely useful for real-world application.&lt;/p&gt;

&lt;p&gt;The most memorable moment was our final pipeline test. We had spent hours resolving a late-stage bug where the LLM-generated graph layout refused to bind cleanly with the Kaggle dataset streaming pipeline. After painstaking step-by-step debugging, we hit "Run"—and watched in real time as the prompt generated a complete 7-layer neural network, downloaded live data, rendered EDA metrics, and executed training end-to-end without breaking.&lt;/p&gt;

&lt;p&gt;What I'll remember most about this event is the sheer thrill of turning a complex, multi-module AI system into a working reality in a room full of passionate builders. HackTropica was a powerful reminder of what good teamwork and dedicated mentorship can achieve under pressure.&lt;/p&gt;

&lt;p&gt;If you find OmniML valuable, consider giving it a ⭐ on &lt;a href="https://github.com/Pritam-mb/hacktropica" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; — and if you build something with it or have feedback, I'd love to hear about it.&lt;/p&gt;

</description>
      <category>mlhacks</category>
      <category>devchallenge</category>
      <category>hackathon</category>
      <category>ai</category>
    </item>
    <item>
      <title>NeedFeed 🤝 — Safe, In-Kind Mutual Aid Without Cash or Tagging</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Mon, 07 Sep 2026 04:14:30 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/needfeed-safe-in-kind-mutual-aid-without-cash-or-tagging-1166</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/needfeed-safe-in-kind-mutual-aid-without-cash-or-tagging-1166</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/weekend-2026-09-03"&gt;Weekend Challenge: Generosity Edition&lt;/a&gt;.&lt;/em&gt;&lt;br&gt;
Prize categories: &lt;strong&gt;Best Use of Snowflake&lt;/strong&gt; · &lt;strong&gt;Best Use of Google AI&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The problem I couldn't unsee
&lt;/h2&gt;

&lt;p&gt;Most charity tech solves the wrong problem.&lt;/p&gt;

&lt;p&gt;It makes it easier to &lt;strong&gt;move money&lt;/strong&gt; — when the actual friction is moving &lt;em&gt;things&lt;/em&gt;. It makes it easier to &lt;strong&gt;identify people in need&lt;/strong&gt; — when the actual requirement is &lt;em&gt;protecting&lt;/em&gt; them. It makes it easier to &lt;strong&gt;claim generosity&lt;/strong&gt; — when the actual value is &lt;em&gt;proving&lt;/em&gt; it.&lt;/p&gt;

&lt;p&gt;Three failure modes, and they all start before a single dollar changes hands:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cash is a liability, not a feature.&lt;/strong&gt; When the need is "10 kg of rice" but the mechanism is "send ₹500," you've introduced an unnecessary conversion step — and with it every failure mode: fee skimming, diversion, a middleman buying the wrong thing entirely.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tagging is surveillance in a helpful mask.&lt;/strong&gt; "Tag someone who needs this!" sounds generous. It publicly identifies a vulnerable person to a stranger, with no consent, no accountability, and no recourse.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Self-reported badges are meaningless.&lt;/strong&gt; Most platforms award "generous donor" status when someone &lt;em&gt;says&lt;/em&gt; they gave. No one checks. The badge becomes a participation trophy, not a trust signal.&lt;/p&gt;

&lt;p&gt;NeedFeed exists because charity does not have to mean money — and almost everyone has &lt;em&gt;something&lt;/em&gt; they can give.&lt;/p&gt;




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

&lt;p&gt;&lt;strong&gt;NeedFeed&lt;/strong&gt; is a hyperlocal, in-kind mutual aid platform. Neighbors coordinate real, physical help — food, clothing, medical supplies, school materials, volunteer time — without ever touching cash, without publicly tagging vulnerable people, and without asking anyone to just trust the process.&lt;/p&gt;

&lt;p&gt;The unit of generosity is a &lt;strong&gt;physical item&lt;/strong&gt;: a warm sweater, a walking cane, a bag of rice.&lt;br&gt;
The unit of trust is a &lt;strong&gt;verified handoff&lt;/strong&gt; — not a payment receipt, not a checkbox.&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%2F30yrwdz9icqn7p9ngnmz.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%2F30yrwdz9icqn7p9ngnmz.png" alt=" " width="800" height="708"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Four hard rules — in the data model, not the guidelines
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1. Strictly in-kind, zero cash, ever.&lt;/strong&gt;&lt;br&gt;
Food, clothing, medicine, mobility aids, school supplies, shelter materials, hygiene kits, and volunteer time only. There is no "donate cash" button, and there never will be.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Open pledge pool, no direct tagging.&lt;/strong&gt;&lt;br&gt;
A posted need enters a public pledge pool. Any neighbor can pledge to fulfill it, but no one gets a private link, a DM, or a direct connection to the beneficiary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Steward representation, with recorded consent.&lt;/strong&gt;&lt;br&gt;
People who can't represent themselves online — no phone, no literacy, no connectivity — are represented by a verified local steward who opens a persistent Case Page on their behalf, &lt;em&gt;only after a recorded verbal consent clip&lt;/em&gt;, not a checkbox.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Two-party verification cycle.&lt;/strong&gt;&lt;br&gt;
A giver pledges, marks the item "Handed Off." Only after the steward independently confirms receipt with the beneficiary does the giver earn their Honor Badge. A mismatch is flagged and auditable.&lt;/p&gt;

&lt;p&gt;The badge means something because it costs something to earn.&lt;/p&gt;


&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/HCPxF1s6CnM" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Run locally — zero API keys required:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/Pritam-mb/charity.git
&lt;span class="nb"&gt;cd &lt;/span&gt;charity
npm &lt;span class="nb"&gt;install
&lt;/span&gt;npm run dev
&lt;span class="c"&gt;# → http://localhost:3000&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The local auto-tagger and local metric engine stand in for Gemini and Snowflake respectively. To connect the real services, add keys to &lt;code&gt;.env.local&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# Snowflake Data Cloud
SNOWFLAKE_ACCOUNT=&amp;lt;account&amp;gt;.&amp;lt;region&amp;gt;
SNOWFLAKE_USERNAME=&amp;lt;username&amp;gt;
SNOWFLAKE_PASSWORD=&amp;lt;password&amp;gt;
SNOWFLAKE_DATABASE=CHARITY
SNOWFLAKE_SCHEMA=PUBLIC
SNOWFLAKE_WAREHOUSE=COMPUTE_WH

# Google Gemini AI
GOOGLE_AI_API_KEY=AIzaSy...
GOOGLE_AI_MODEL=gemini-1.5-flash
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Delete &lt;code&gt;data/store.json&lt;/code&gt; and restart the dev server to reseed with fresh, realistic demo data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub →&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/charity" rel="noopener noreferrer"&gt;Pritam-mb/charity&lt;/a&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  The walkthrough
&lt;/h2&gt;
&lt;h3&gt;
  
  
  The feed
&lt;/h3&gt;

&lt;p&gt;The home feed is designed for Gen Z: visual, fast, and community-driven. It's a dark-mode, Reddit-style three-column layout — a collapsible left sidebar for navigation, a center feed with segmented sorting (&lt;strong&gt;New / Hot / Top Urgent&lt;/strong&gt;) and category/neighborhood filters, and a right rail with a Local Area Explorer and community rules.&lt;/p&gt;

&lt;p&gt;You can browse new, hot, or urgent needs, filter by category and neighborhood, and see exactly what is needed — with a real image, urgency flair, and steward-beneficiary attribution (&lt;em&gt;"Posted by Rashid on behalf of Arjun"&lt;/em&gt;). Every need card has a four-action bar: Support, Comments, Share, and Pledge Help.&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%2Fy2avs425p05ua1xsanxv.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%2Fy2avs425p05ua1xsanxv.png" alt=" " width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Opening a need
&lt;/h3&gt;

&lt;p&gt;Open a need and you get the full context — item, urgency, quantity, neighborhood, and the Case Page it belongs to. A verified local handoff point appears on the Leaflet map, so help stays simple and local. No stranger-to-stranger coordinates. No private DMs.&lt;/p&gt;
&lt;h3&gt;
  
  
  Making a pledge
&lt;/h3&gt;

&lt;p&gt;Choose &lt;strong&gt;Pledge Help&lt;/strong&gt;, select what you can provide, and complete the handoff. But a pledge is not impact.&lt;/p&gt;

&lt;p&gt;You mark it &lt;strong&gt;Handed Off&lt;/strong&gt;. Then the verified steward confirms delivery with the beneficiary. Only when &lt;em&gt;both sides confirm&lt;/em&gt; does the system record a verified contribution and award the Honor Badge. That two-step is not a formality — it's the whole point.&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%2F550qr460yvpmsdfwdiv1.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%2F550qr460yvpmsdfwdiv1.png" alt=" " width="800" height="469"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Posting a need
&lt;/h3&gt;

&lt;p&gt;Posting only requires a plain-language caption and an optional photo or video. Gemini AI analyzes the description and proposes category, item type, quantity, and urgency — all fully editable before publishing. AI proposes; a human confirms. Nothing auto-publishes.&lt;/p&gt;

&lt;p&gt;When Gemini isn't configured, a local keyword-and-regex inference engine (&lt;code&gt;lib/auto-tag.ts&lt;/code&gt;) handles the same job. The workflow never breaks because of a missing API key.&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%2Fccaxa0xdmx4to68lsq0x.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%2Fccaxa0xdmx4to68lsq0x.png" alt=" " width="1582" height="808"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Case Pages
&lt;/h3&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%2Fs8npifoffbqpmviqm8c0.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%2Fs8npifoffbqpmviqm8c0.png" alt=" " width="800" height="471"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Case Pages (&lt;code&gt;/cases/[id]&lt;/code&gt;) are dedicated, persistent profiles for recurring or high-vulnerability beneficiaries. Instead of isolated posts, a Case Page becomes a &lt;em&gt;living record&lt;/em&gt; of the community helping one person over time.&lt;/p&gt;

&lt;p&gt;Each page has:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A letter avatar and alias name (never a legal name)&lt;/li&gt;
&lt;li&gt;A verified-consent badge&lt;/li&gt;
&lt;li&gt;An append-only steward update timeline with photo evidence&lt;/li&gt;
&lt;li&gt;All associated needs with their fulfillment status&lt;/li&gt;
&lt;li&gt;A defined handoff location — a known local anchor point, not a stranger's address&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The community extends beyond individual needs too — people can offer items, volunteer their time, connect with organisations, and follow cases they care about.&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%2Ffas1rjkmj3bu5mglhb4e.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%2Ffas1rjkmj3bu5mglhb4e.png" alt=" " width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Account settings define a person's platform role (volunteer, steward, NGO leader), primary neighborhood for anchor-point matching, and contact info — which is only ever shared with stewards at the point of a pledge or handoff, never made public.&lt;/p&gt;
&lt;h3&gt;
  
  
  Achievements
&lt;/h3&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%2F5p041han8af36kevgu9p.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%2F5p041han8af36kevgu9p.png" alt=" " width="800" height="452"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Confirmed, fulfilled needs become a quiet public record — not a leaderboard of who gave the most, but a feed of what actually changed for someone, with a link back to their Case Page. Verified contributions, not participation trophies.&lt;/p&gt;
&lt;h3&gt;
  
  
  Snowflake HQ — the transparency layer
&lt;/h3&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%2Fhhq6emcdwxj95eulxrgu.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%2Fhhq6emcdwxj95eulxrgu.png" alt=" " width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then comes &lt;strong&gt;Snowflake HQ&lt;/strong&gt; — what I call the GlassPocket layer, because every transaction is visible through the glass.&lt;/p&gt;

&lt;p&gt;A one-click &lt;code&gt;POST /api/sync&lt;/code&gt; pushes the entire local transactional state to Snowflake. Dashboard metrics are then computed via Snowflake SQL when available, or locally from &lt;code&gt;store.json&lt;/code&gt; when not — the platform is always operational either way.&lt;/p&gt;

&lt;p&gt;Snowflake surfaces:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which neighborhoods have the most unfulfilled needs&lt;/li&gt;
&lt;li&gt;Which categories are chronically undersupplied&lt;/li&gt;
&lt;li&gt;Which Case Pages are going stale (steward abandonment detection)&lt;/li&gt;
&lt;li&gt;Whether badge counts actually correspond to real confirmed handoffs&lt;/li&gt;
&lt;li&gt;Which shared needs convert into pledges and which don't&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Top Givers are ranked by &lt;strong&gt;confirmed handoffs&lt;/strong&gt; — not pledges. That single distinction is the difference between a leaderboard and an accountability record.&lt;/p&gt;


&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Tech&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Framework&lt;/td&gt;
&lt;td&gt;Next.js 15 (App Router), React 19&lt;/td&gt;
&lt;td&gt;Server Components for the heavy lifting, Client Components for interactive hubs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Language&lt;/td&gt;
&lt;td&gt;TypeScript (strict mode)&lt;/td&gt;
&lt;td&gt;100% type safety across every API route and component&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Styling&lt;/td&gt;
&lt;td&gt;Vanilla CSS, custom design system&lt;/td&gt;
&lt;td&gt;Reddit dark theme, glassmorphism, responsive grids — no framework overhead&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data&lt;/td&gt;
&lt;td&gt;Local JSON store (&lt;code&gt;data/store.json&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;Atomically managed via &lt;code&gt;lib/store.ts&lt;/code&gt;, auto-seeded on first run&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intelligence&lt;/td&gt;
&lt;td&gt;Google Gemini AI&lt;/td&gt;
&lt;td&gt;Auto-categorization, item extraction, urgency scoring on upload&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytics&lt;/td&gt;
&lt;td&gt;Snowflake Data Cloud&lt;/td&gt;
&lt;td&gt;Relational telemetry with automated local fallback&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mapping&lt;/td&gt;
&lt;td&gt;Leaflet + OpenStreetMap&lt;/td&gt;
&lt;td&gt;Hyperlocal anchor point visualization&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Repo structure:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;app/              Next.js App Router — pages, layouts, API routes
components/       Feed, need cards, pledge pool, steward tools, forms, dashboard widgets
lib/              Types, store, seed data, Gemini client, Snowflake queries, auto-tagger
data/             store.json (auto-generated, gitignored)
scripts/          Snowflake diagnostics and connectivity tests
public/images/    Photorealistic need imagery
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Worth reading: &lt;code&gt;plan.md&lt;/code&gt; (product thesis), &lt;code&gt;problems.md&lt;/code&gt; (every risk identified and how it's mitigated), &lt;code&gt;lib/store.ts&lt;/code&gt; (the two-party verification cycle), &lt;code&gt;lib/snowflake.ts&lt;/code&gt; (dual-engine telemetry with automatic fallback).&lt;/p&gt;


&lt;h2&gt;
  
  
  Safety decisions I'm proud of
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Alias names, not legal names.&lt;/strong&gt; Case Pages use pseudonyms and broad neighborhood tags — never exact addresses, never legal identity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No solo stewardship.&lt;/strong&gt; One person alone speaking for another is exactly the risk the platform exists to prevent. The system requires co-stewardship.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Consent isn't a checkbox.&lt;/strong&gt; Verbal recorded consent is a structural requirement — a field in the data model, not a terms-of-service paragraph.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Anchor points over direct meetups.&lt;/strong&gt; Handoffs route through a known local location (a shop, a community hub) rather than a stranger-to-stranger connection.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Staleness detection.&lt;/strong&gt; Snowflake flags Case Pages with no recent updates. An abandoned page that still &lt;em&gt;looks&lt;/em&gt; active is worse than no page at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Editable AI tags.&lt;/strong&gt; Gemini proposes; the steward confirms. No auto-publish, no blind trust in classification.&lt;/p&gt;


&lt;h2&gt;
  
  
  Prize categories
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Best Use of Snowflake — GlassPocket accountability layer&lt;/strong&gt;&lt;br&gt;
Snowflake is the transparency backbone. It powers the institutional dashboard (unfulfilled needs by category/area, urgency distribution, steward staleness detection, confirmed-handoffs-only leaderboard) with a dual-engine design that falls back to local computation with zero downtime if Snowflake is unreachable. Key design choice: analytics that fail silently are worse than no analytics at all — so the fallback is first-class, not an afterthought.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best Use of Google AI — Gemini auto-categorization&lt;/strong&gt;&lt;br&gt;
Gemini analyzes every posted need (description and/or photo) to propose category, item type, quantity, and urgency. A local keyword-and-regex engine (&lt;code&gt;lib/auto-tag.ts&lt;/code&gt;) provides identical functionality when Gemini isn't configured, so the platform never depends on a live API key to function. AI assists the steward — it does not replace the steward's judgment.&lt;/p&gt;


&lt;h2&gt;
  
  
  What I'd build next
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Solana confirmation ledger&lt;/strong&gt; — writing each verified handoff on-chain so badge counts are cryptographically auditable, not just database rows. The &lt;code&gt;ConfirmationRecord&lt;/code&gt; model already has an &lt;code&gt;on_chain_ref&lt;/code&gt; field waiting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ElevenLabs voice input&lt;/strong&gt; — letting stewards speak updates instead of typing, with auto-narrated Case Page timelines in multiple languages for low-literacy accessibility.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate detection&lt;/strong&gt; — Gemini visual-similarity + area matching at Case Page creation, to prevent two stewards unknowingly opening pages for the same person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stewardship transfer&lt;/strong&gt; — a formal flow for community members to take over inactive Case Pages after a defined inactivity window.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real geospatial infrastructure&lt;/strong&gt; — replacing manual neighborhood tags with location-aware matching and proximity-based feed prioritization.&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;
  
  
  The point
&lt;/h2&gt;

&lt;p&gt;Someone posts a need. Someone else offers what they can. The community connects them. The handoff happens. The steward verifies it. The contribution becomes part of a trusted record.&lt;/p&gt;

&lt;p&gt;Not everyone can donate money. But almost everyone has something they can give — a bag of rice, a spare cane, an afternoon.&lt;/p&gt;

&lt;p&gt;NeedFeed turns those small acts into a connected, accountable community. No cash to divert. No vulnerable people to tag. No badges to fake. Just rice, sweaters, wheelchairs, and the receipts to prove they arrived.&lt;/p&gt;




&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/Pritam-mb" rel="noopener noreferrer"&gt;
        Pritam-mb
      &lt;/a&gt; / &lt;a href="https://github.com/Pritam-mb/charity" rel="noopener noreferrer"&gt;
        charity
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;&lt;div class="markdown-heading"&gt;
&lt;h1 class="heading-element"&gt;NeedFeed&lt;/h1&gt;
&lt;/div&gt;

&lt;p&gt;Hyperlocal in-kind giving. Post a need, anyone can pledge a piece of it into an open pool
a steward confirms the handoff, and the giver earns a verifiable badge — no money, no tagging
of vulnerable people.&lt;/p&gt;
&lt;p&gt;Product thinking lives in &lt;code&gt;plan.md&lt;/code&gt; and &lt;code&gt;problems.md&lt;/code&gt; (at repo root, &lt;code&gt;..&lt;/code&gt;).&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Run it&lt;/h2&gt;
&lt;/div&gt;
&lt;div class="highlight highlight-source-shell notranslate position-relative overflow-auto js-code-highlight"&gt;
&lt;pre&gt;npm install
npm run dev        &lt;span class="pl-c"&gt;&lt;span class="pl-c"&gt;#&lt;/span&gt; http://localhost:3000&lt;/span&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;The app works with zero API keys. Local auto-tagging stands in for Google AI and the
Snowflake dashboard falls back to computing the same metrics locally.&lt;/p&gt;
&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Demo script (2–3 min)&lt;/h2&gt;

&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Reel&lt;/strong&gt; (&lt;code&gt;/&lt;/code&gt;) — filter by category/area, open a need.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Case Page&lt;/strong&gt; (&lt;code&gt;/cases/c-arjun&lt;/code&gt;) — multi-entry timeline, recorded-consent badge, steward tools.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pledge&lt;/strong&gt; — on a need card, pledge a portion → “Mark handed off”.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm&lt;/strong&gt; — on the Case Page, steward tools → “Confirm received” → giver badge increments (see &lt;code&gt;/&lt;/code&gt; toolbar is per-user; badge lives in &lt;code&gt;store.json&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;…&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/Pritam-mb/charity" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;h2&gt;
  
  
  👥 The Team
&lt;/h2&gt;

&lt;p&gt;Our team came together for the International Charity Day DEV Challenge to build NeedFeed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://dev.to"&gt;@pritam_patra_429a25dedae6&lt;/a&gt; (Lead Developer)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://github.com/RexBytes" rel="noopener noreferrer"&gt;@t-rexbytes&lt;/a&gt; (Collaborator)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Built with Next.js 15 · React 19 · Snowflake Data Cloud · Google Gemini AI · Leaflet · TypeScript&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>showdev</category>
      <category>opensource</category>
    </item>
    <item>
      <title>From 2.0 MB to 471 KB: Debugging Rawbee with Sentry + Gemini</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sun, 16 Aug 2026 21:37:22 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/from-20-mb-to-471-kb-debugging-rawbee-with-sentry-gemini-363g</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/from-20-mb-to-471-kb-debugging-rawbee-with-sentry-gemini-363g</guid>
      <description>&lt;h1&gt;
  
  
  I Thought Rawbee Was Slow — Then I Opened the Network Tab
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;This is a submission for &lt;a href="https://dev.to/bugsmash"&gt;DEV's Summer Bug Smash: Smash Stories&lt;/a&gt; powered by &lt;a href="https://sentry.io/" rel="noopener noreferrer"&gt;Sentry&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Project
&lt;/h2&gt;

&lt;p&gt;Rawbee is a full-stack video-sharing and real-time streaming platform that I built as a YouTube-inspired application.&lt;/p&gt;

&lt;p&gt;It currently includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Video uploads&lt;/li&gt;
&lt;li&gt;Video discovery&lt;/li&gt;
&lt;li&gt;Subscriptions&lt;/li&gt;
&lt;li&gt;Watch history&lt;/li&gt;
&lt;li&gt;Live streaming&lt;/li&gt;
&lt;li&gt;WebRTC-based functionality&lt;/li&gt;
&lt;li&gt;Screen sharing&lt;/li&gt;
&lt;li&gt;Socket.IO communication&lt;/li&gt;
&lt;li&gt;Cloudinary media delivery&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The stack includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frontend:&lt;/strong&gt; React 18, TypeScript, Tailwind CSS, Vite&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; Node.js, Express&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database:&lt;/strong&gt; MongoDB&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Media:&lt;/strong&gt; Cloudinary&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real-time:&lt;/strong&gt; Socket.IO, WebRTC&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Observability:&lt;/strong&gt; Sentry&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI debugging:&lt;/strong&gt; Google Gemini&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Repository:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/rawbee" rel="noopener noreferrer"&gt;View Rawbee on GitHub&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bug Smash PR:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/rawbee/pull/1" rel="noopener noreferrer"&gt;View the Pull Request&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For this Bug Smash, I deliberately stopped adding new features and focused on one question:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Where is Rawbee doing unnecessary work, and can I prove that my fixes actually made it better?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The Moment I Realized Something Was Wrong
&lt;/h2&gt;

&lt;p&gt;Nothing was obviously broken.&lt;/p&gt;

&lt;p&gt;The homepage loaded. Videos appeared. Search worked.&lt;/p&gt;

&lt;p&gt;But the application felt heavier than it should.&lt;/p&gt;

&lt;p&gt;My first instinct was to blame React.&lt;/p&gt;

&lt;p&gt;When I typed into the search bar, the parent component updated and the video-card tree was being evaluated again.&lt;/p&gt;

&lt;p&gt;So I opened React DevTools and started profiling.&lt;/p&gt;

&lt;p&gt;The profiler showed repeated &lt;code&gt;VideoCard&lt;/code&gt; renders during a simple interaction, even when the underlying video data had not changed.&lt;/p&gt;

&lt;p&gt;That was the first bug.&lt;/p&gt;

&lt;p&gt;Then I opened the Network tab.&lt;/p&gt;

&lt;p&gt;And I found a much bigger problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Network Tab Changed Everything
&lt;/h2&gt;

&lt;p&gt;The production homepage was transferring approximately:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.0 MB&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Some individual image assets were enormous for their displayed size:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;834 KB
433 KB
160 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;An 834 KB thumbnail for a relatively small video card immediately looked wrong.&lt;/p&gt;

&lt;p&gt;At that point, the problem stopped being:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"The page feels slow."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;and became:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"The browser is downloading far more data than this UI should need."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Before: Production Baseline
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;📸 SCREENSHOT 1 — BEFORE NETWORK&lt;/strong&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%2Ft1um3ilrj881amyorbw8.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%2Ft1um3ilrj881amyorbw8.png" alt="Chrome DevTools Network panel showing the unoptimized production build with 30 requests, 2.0 MB transferred, 2.3 MB of resources, and a 2.61 second Load time" width="800" height="493"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Production baseline before optimization. The homepage transferred approximately 2.0 MB, with individual image assets reaching 834 KB, 433 KB, and 160 KB.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The baseline showed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;30 requests&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.0 MB transferred&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.3 MB resources&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;593 ms DOMContentLoaded&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.61 s Load&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.82 s Finish&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For the first time, I had a real baseline instead of a vague feeling that the application was slow.&lt;/p&gt;

&lt;h1&gt;
  
  
  Fix #1 — Stopping Unnecessary React Renders
&lt;/h1&gt;

&lt;p&gt;The first fix was &lt;code&gt;React.memo()&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The problem looked roughly like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Search state changes
        ↓
Home re-renders
        ↓
VideoCard renders again
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;But if the video's data hasn't changed, that child component doesn't necessarily need to render again.&lt;/p&gt;

&lt;p&gt;I changed the component to:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;memo&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;formatDuration&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;seconds&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// ...&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;formatViews&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;views&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// ...&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;VideoCard&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;memo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;VideoCard&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="nx"&gt;video&lt;/span&gt;
&lt;span class="p"&gt;}:&lt;/span&gt; &lt;span class="nx"&gt;VideoCardProps&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"group cursor-pointer"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="cm"&gt;/* Video card UI */&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nx"&gt;VideoCard&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I also moved pure formatting helpers outside the component so their definitions weren't recreated during every component execution.&lt;/p&gt;

&lt;p&gt;The important optimization, however, was &lt;code&gt;React.memo()&lt;/code&gt; combined with stable props.&lt;/p&gt;

&lt;p&gt;When the &lt;code&gt;video&lt;/code&gt; prop remains referentially equal, React can skip rendering the component.&lt;/p&gt;

&lt;h2&gt;
  
  
  React Profiler — Before
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;📸 SCREENSHOT 2 — REACT PROFILER BEFORE&lt;/strong&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%2Fjnywt9afuyjg96g9fekf.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%2Fjnywt9afuyjg96g9fekf.png" alt="React DevTools Profiler showing VideoCard rendering repeatedly during the unoptimized search interaction" width="799" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Before memoization: &lt;code&gt;VideoCard&lt;/code&gt; renders repeatedly during the recorded interaction as parent state changes.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The profiler gave me a concrete reason to make the optimization instead of blindly applying &lt;code&gt;React.memo()&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  React Profiler — After
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;📸 SCREENSHOT 3 — REACT PROFILER AFTER&lt;/strong&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%2Fnphg2snr595qiuuhlt5j.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%2Fnphg2snr595qiuuhlt5j.png" alt="React DevTools Profiler showing the memoized VideoCard component being skipped during the optimized interaction" width="800" height="498"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;After memoization: the Profiler explicitly reports "Did not render on the client during this profiling session." The memoized component is skipped when its props remain unchanged.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The important result wasn't the raw number of React commits.&lt;/p&gt;

&lt;p&gt;It was seeing React actually skip the component when its props remained unchanged.&lt;/p&gt;

&lt;h1&gt;
  
  
  Fix #2 — The 834 KB Thumbnail
&lt;/h1&gt;

&lt;p&gt;The React optimization removed unnecessary rendering work.&lt;/p&gt;

&lt;p&gt;But the Network tab was still pointing at the much larger problem:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;image delivery.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The original application requested full-size images from Cloudinary even when the UI only needed a relatively small thumbnail.&lt;/p&gt;

&lt;p&gt;I created a helper:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;getOptimizedCloudinaryUrl&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;width&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;500&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;url&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;cloudinary.com&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;/upload/&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;`/upload/w_&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;width&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;/f_auto/q_auto/`&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;img&lt;/span&gt;
  &lt;span class="na"&gt;src&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;getOptimizedCloudinaryUrl&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="nx"&gt;video&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;thumbnail&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="mi"&gt;500&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;alt&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;video&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The transformation uses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;w_500&lt;/code&gt; to resize the image&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;f_auto&lt;/code&gt; to let Cloudinary select an appropriate format&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;q_auto&lt;/code&gt; to optimize quality&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before optimization, some image responses were approximately:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;834 KB
433 KB
160 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After optimization, examples included:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;7.3 KB
2.0 KB
22.0 KB
2.6 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This became the biggest contributor to the overall network improvement.&lt;/p&gt;

&lt;p&gt;Instead of:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;2.0 MB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;the optimized production build transferred:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;471 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's a:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;76.5% reduction in transferred data.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  After: Optimized Production Build
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;📸 SCREENSHOT 4 — AFTER NETWORK&lt;/strong&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%2Fq9lnkkegq42kh1rejyyj.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%2Fq9lnkkegq42kh1rejyyj.png" alt="Chrome DevTools Network panel showing the optimized production build with 32 requests, 471 KB transferred, 767 KB resources, and a 1.60 second Load time" width="800" height="519"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Same page, same throttling, same cache-disabled conditions. Payload dropped from 2.0 MB to 471 KB and Load time from 2.61 s to 1.60 s.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Fix #3 — Why Load JavaScript for Pages the User Hasn't Opened?
&lt;/h1&gt;

&lt;p&gt;Rawbee contains multiple routes.&lt;/p&gt;

&lt;p&gt;But a user visiting the homepage doesn't need every page's JavaScript immediately.&lt;/p&gt;

&lt;p&gt;So I introduced route-level code splitting using &lt;code&gt;React.lazy()&lt;/code&gt; and &lt;code&gt;Suspense&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;lazy&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Suspense&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;Home&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;lazy&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;./pages/Home&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;Login&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;lazy&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;./pages/Login&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;App&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Router&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Suspense&lt;/span&gt; &lt;span class="err"&gt;&amp;lt;&lt;/span&gt;&lt;span class="na"&gt;div&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"flex h-screen items-center justify-center"&lt;/span&gt; &lt;span class="na"&gt;fallback&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"{"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
            Loading...
          &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        }
      &amp;gt;
        &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Routes&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
          &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Route&lt;/span&gt; &lt;span class="na"&gt;element&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"{&amp;lt;Login"&lt;/span&gt; &lt;span class="na"&gt;path&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/login"&lt;/span&gt;&lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;}
          /&amp;gt;

          &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Route&lt;/span&gt; &lt;span class="na"&gt;element&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"{&amp;lt;Home"&lt;/span&gt; &lt;span class="na"&gt;path&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/"&lt;/span&gt;&lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;}
          /&amp;gt;
        &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Routes&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Suspense&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="na"&gt;Router&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  );
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Instead of:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Application
    ↓
Everything loads immediately
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;the browser can now load:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Current route
    ↓
Current route chunk
    ↓
User navigates
    ↓
Additional route chunk
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This keeps the initial JavaScript workload focused on the route the user is actually visiting.&lt;/p&gt;

&lt;h1&gt;
  
  
  Fix #4 — Cleaning Up Sentry Configuration
&lt;/h1&gt;

&lt;p&gt;While working on observability, I also found that the Sentry DSN was hardcoded in the source.&lt;/p&gt;

&lt;p&gt;I moved it to environment configuration.&lt;/p&gt;

&lt;p&gt;Before:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="nx"&gt;Sentry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;init&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;dsn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;your_dsn_here&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="nx"&gt;Sentry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;init&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;dsn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;meta&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;VITE_SENTRY_DSN&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;VITE_SENTRY_DSN=your_dsn_here
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This makes the configuration easier to manage across environments and keeps environment-specific configuration outside application source.&lt;/p&gt;

&lt;h1&gt;
  
  
  Fix #5 — When MongoDB Stopped Connecting
&lt;/h1&gt;

&lt;p&gt;While working on the frontend, I encountered a completely different problem.&lt;/p&gt;

&lt;p&gt;MongoDB stopped connecting and the backend reported:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;querySrv ECONNREFUSED
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;At first, I treated it as a MongoDB problem.&lt;/p&gt;

&lt;p&gt;But the failure was occurring during DNS/SRV resolution.&lt;/p&gt;

&lt;p&gt;I investigated the DNS behavior using:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Resolve-DnsName&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;mongodb-host&lt;/span&gt;&lt;span class="err"&gt;&amp;gt;&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After confirming the DNS resolution problem in my Windows environment, I changed the MongoDB connection strategy to a direct connection configuration as a workaround.&lt;/p&gt;

&lt;p&gt;The backend then reconnected successfully.&lt;/p&gt;

&lt;h1&gt;
  
  
  Best Use of Sentry
&lt;/h1&gt;

&lt;p&gt;Sentry became part of my debugging workflow rather than something I added only after the application was finished.&lt;/p&gt;

&lt;p&gt;My process became:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Runtime problem
      ↓
Sentry captures the event
      ↓
Inspect issue + stack trace + context
      ↓
Locate affected code
      ↓
Fix
      ↓
Verify
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One concrete example happened during a refactor.&lt;/p&gt;

&lt;p&gt;I accidentally removed an import for &lt;code&gt;VideoSkeleton&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The application could still build successfully.&lt;/p&gt;

&lt;p&gt;But when the loading path executed at runtime, the browser threw:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ReferenceError: VideoSkeleton is not defined
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Sentry captured the runtime failure and provided the stack trace and surrounding debugging context.&lt;/p&gt;

&lt;p&gt;Instead of:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Something is broken."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I now had:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"This exact runtime path is throwing this exact error."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;📸 SCREENSHOT 5 — SENTRY ISSUE&lt;/strong&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%2Fo9hbila26fx96lrq5vwy.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%2Fo9hbila26fx96lrq5vwy.png" alt="Sentry issue page showing the ReferenceError VideoSkeleton is not defined with its stack trace and debugging context" width="800" height="484"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Sentry captured the runtime failure with the stack trace and execution context used during debugging.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Sentry and React Profiler Answered Different Questions
&lt;/h2&gt;

&lt;p&gt;One of the biggest lessons from the project was that different debugging tools answer different questions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sentry&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What is failing?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;React Profiler&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What is rendering?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Chrome Network&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What is the browser downloading?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Using separate tools for separate questions made the investigation much clearer.&lt;/p&gt;

&lt;h1&gt;
  
  
  Best Use of Google AI
&lt;/h1&gt;

&lt;p&gt;I used &lt;strong&gt;Google Gemini 3.1 Pro&lt;/strong&gt; as a debugging partner rather than simply asking it to generate code.&lt;/p&gt;

&lt;p&gt;The MongoDB DNS error was the clearest example.&lt;/p&gt;

&lt;p&gt;I provided Gemini with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;code&gt;querySrv ECONNREFUSED&lt;/code&gt; error&lt;/li&gt;
&lt;li&gt;My Windows environment&lt;/li&gt;
&lt;li&gt;Node.js information&lt;/li&gt;
&lt;li&gt;The MongoDB connection behavior&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Gemini helped investigate possible causes involving DNS resolution, MongoDB SRV records, and IPv4/IPv6 behavior.&lt;/p&gt;

&lt;p&gt;One useful diagnostic was:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Resolve-DnsName&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;_mongodb._tcp.cluster0.x3qwygg.mongodb.net&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I ran the command myself.&lt;/p&gt;

&lt;p&gt;That distinction was important:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;I treated Gemini's response as a hypothesis, not as proof.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I independently verified the behavior before changing the connection configuration.&lt;/p&gt;

&lt;p&gt;The debugging loop became:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;MongoDB querySrv ECONNREFUSED
        ↓
Gemini analysis
        ↓
DNS / IPv4-IPv6 hypothesis
        ↓
Resolve-DnsName verification
        ↓
Connection configuration workaround
        ↓
Backend restored
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;📸 SCREENSHOT 6 — GEMINI DEBUGGING&lt;/strong&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%2Fxjiirxdbgbbofewggcow.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%2Fxjiirxdbgbbofewggcow.png" alt="Gemini 3.1 Pro conversation analyzing the MongoDB querySrv ECONNREFUSED DNS and IPv4 IPv6 issue" width="799" height="499"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Gemini helped narrow down the MongoDB connection failure; I independently verified the suggested diagnostic path before implementing the workaround.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The useful part of AI debugging wasn't:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"AI wrote code for me."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;"AI helped me turn an unfamiliar error into a testable hypothesis."&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h1&gt;
  
  
  The Final Benchmark
&lt;/h1&gt;

&lt;p&gt;After applying the fixes, I repeated the production benchmark under the same conditions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Chrome&lt;/li&gt;
&lt;li&gt;Fast 4G throttling&lt;/li&gt;
&lt;li&gt;Browser cache disabled&lt;/li&gt;
&lt;li&gt;Same homepage&lt;/li&gt;
&lt;li&gt;Same machine&lt;/li&gt;
&lt;li&gt;Same production preview workflow&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Before&lt;/th&gt;
&lt;th&gt;After&lt;/th&gt;
&lt;th&gt;Change&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Network transferred&lt;/td&gt;
&lt;td&gt;2.0 MB&lt;/td&gt;
&lt;td&gt;471 KB&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;−76.5%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Resources loaded&lt;/td&gt;
&lt;td&gt;2.3 MB&lt;/td&gt;
&lt;td&gt;767 KB&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;−66.7%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Load event&lt;/td&gt;
&lt;td&gt;2.61 s&lt;/td&gt;
&lt;td&gt;1.60 s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;−38.7%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Finish&lt;/td&gt;
&lt;td&gt;2.82 s&lt;/td&gt;
&lt;td&gt;1.81 s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;−35.8%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Requests&lt;/td&gt;
&lt;td&gt;30&lt;/td&gt;
&lt;td&gt;32&lt;/td&gt;
&lt;td&gt;+2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DOMContentLoaded&lt;/td&gt;
&lt;td&gt;593 ms&lt;/td&gt;
&lt;td&gt;624 ms&lt;/td&gt;
&lt;td&gt;+31 ms&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The two numbers I cared about most were:&lt;/p&gt;

&lt;h3&gt;
  
  
  2.0 MB → 471 KB
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;76.5% less network data transferred&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;and:&lt;/p&gt;

&lt;h3&gt;
  
  
  2.61 s → 1.60 s
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;38.7% faster Load event&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What Didn't Improve
&lt;/h2&gt;

&lt;p&gt;Not every metric improved.&lt;/p&gt;

&lt;p&gt;The request count changed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;30 → 32
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and DOMContentLoaded changed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;593 ms → 624 ms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I also had a stale thumbnail returning a 404, which I flagged as follow-up work.&lt;/p&gt;

&lt;p&gt;I don't want to turn a benchmark into:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Everything got better."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It didn't.&lt;/p&gt;

&lt;p&gt;The meaningful result was the large reduction in transferred data and the improvement in the Load event.&lt;/p&gt;

&lt;p&gt;Those are the results I can actually demonstrate.&lt;/p&gt;

&lt;h1&gt;
  
  
  What I'm Most Proud Of
&lt;/h1&gt;

&lt;p&gt;The thing I'm most proud of isn't a particular line of code.&lt;/p&gt;

&lt;p&gt;It's the change in how I approached the problem.&lt;/p&gt;

&lt;p&gt;Before this work, my instinct would have been:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"The application feels slow. I should optimize the code."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Now the process is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Observe
   ↓
Measure
   ↓
Hypothesize
   ↓
Test
   ↓
Fix
   ↓
Measure again
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I thought React rendering was the main problem.&lt;/p&gt;

&lt;p&gt;Then the Network tab showed me that an &lt;strong&gt;834 KB thumbnail&lt;/strong&gt; was a much bigger issue.&lt;/p&gt;

&lt;p&gt;That was a useful reminder:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The thing that feels slow isn't always the thing that is actually expensive.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h1&gt;
  
  
  What I Learned
&lt;/h1&gt;

&lt;h3&gt;
  
  
  Profile before optimizing
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;React.memo()&lt;/code&gt; is useful when you can identify unnecessary renders.&lt;/p&gt;

&lt;p&gt;The profiler gave me evidence to make the change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Network payload matters
&lt;/h3&gt;

&lt;p&gt;A frontend can have clean React code and still feel slow if the browser downloads unnecessary data.&lt;/p&gt;

&lt;h3&gt;
  
  
  Observability changes debugging
&lt;/h3&gt;

&lt;p&gt;Sentry turned runtime errors into actionable issues instead of vague UI failures.&lt;/p&gt;

&lt;h3&gt;
  
  
  AI works best with verification
&lt;/h3&gt;

&lt;p&gt;Gemini helped me investigate the MongoDB problem faster, but I still tested the hypothesis myself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Not every metric needs to improve
&lt;/h3&gt;

&lt;p&gt;A useful benchmark should report the actual result, including the numbers that didn't move in the desired direction.&lt;/p&gt;

&lt;h1&gt;
  
  
  What's Next for Rawbee?
&lt;/h1&gt;

&lt;p&gt;The Bug Smash focused on performance, reliability, and debugging.&lt;/p&gt;

&lt;p&gt;But Rawbee is still evolving.&lt;/p&gt;

&lt;p&gt;The next direction is a more interactive social streaming experience.&lt;/p&gt;

&lt;p&gt;Future work includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Live Rooms&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WebRTC video/audio&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Screen sharing&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Real-time Socket.IO chat&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synchronized watch parties&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Multi-user co-streaming&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Host controls&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is eventually to let users watch, communicate, and participate together without needing a separate application for every part of the experience.&lt;/p&gt;

&lt;p&gt;These are &lt;strong&gt;future roadmap features&lt;/strong&gt; and are not included in the performance measurements above.&lt;/p&gt;

&lt;h1&gt;
  
  
  Final Result
&lt;/h1&gt;

&lt;p&gt;The most important transformation was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.0 MB → 471 KB&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A &lt;strong&gt;76.5% reduction in network transfer&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The Load event changed from:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.61 s → 1.60 s&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A &lt;strong&gt;38.7% improvement&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Along the way I also:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reduced unnecessary &lt;code&gt;VideoCard&lt;/code&gt; rendering&lt;/li&gt;
&lt;li&gt;Optimized Cloudinary image delivery&lt;/li&gt;
&lt;li&gt;Added route-level code splitting&lt;/li&gt;
&lt;li&gt;Improved Sentry configuration&lt;/li&gt;
&lt;li&gt;Diagnosed a MongoDB DNS/SRV failure&lt;/li&gt;
&lt;li&gt;Used Sentry for runtime observability&lt;/li&gt;
&lt;li&gt;Used Gemini to accelerate debugging&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No rewrite.&lt;/p&gt;

&lt;p&gt;No new framework.&lt;/p&gt;

&lt;p&gt;Just:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Measure → Understand → Fix → Verify&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h1&gt;
  
  
  Links
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Rawbee Repository:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://github.com/Pritam-mb/rawbee" rel="noopener noreferrer"&gt;https://github.com/Pritam-mb/rawbee&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bug Smash Pull Request:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://github.com/Pritam-mb/rawbee/pull/1" rel="noopener noreferrer"&gt;https://github.com/Pritam-mb/rawbee/pull/1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks for reading.&lt;/p&gt;

&lt;p&gt;And thanks to DEV and Sentry for giving me a reason to stop adding features for a moment and ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;How well does the application I've already built actually work?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>devchallenge</category>
      <category>bugsmash</category>
    </item>
    <item>
      <title>Slashing Network Payload by 76%: How I Used Sentry and Gemini to Optimize a Real-Time Streaming Platform</title>
      <dc:creator>Pritam Patra</dc:creator>
      <pubDate>Sun, 16 Aug 2026 19:21:13 +0000</pubDate>
      <link>https://dev.to/pritam_patra_429a25dedae6/slashing-network-payload-by-76-how-i-used-sentry-and-gemini-to-optimize-a-real-time-streaming-fnd</link>
      <guid>https://dev.to/pritam_patra_429a25dedae6/slashing-network-payload-by-76-how-i-used-sentry-and-gemini-to-optimize-a-real-time-streaming-fnd</guid>
      <description>&lt;h1&gt;
  
  
  From 20+ Unnecessary Renders to a 76.5% Smaller Network Payload — How I Optimized Rawbee with Sentry + Gemini
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;This is a submission for &lt;a href="https://dev.to/bugsmash"&gt;DEV's Summer Bug Smash: Clear the Lineup&lt;/a&gt; powered by &lt;a href="https://sentry.io/" rel="noopener noreferrer"&gt;Sentry&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Overview
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Project:&lt;/strong&gt; Rawbee —  Collaborative Real-Time Streaming Platform &lt;br&gt;
&lt;strong&gt;Implementation:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/rawbee/pull/1" rel="noopener noreferrer"&gt;View the GitHub Pull Request&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Repository:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/rawbee" rel="noopener noreferrer"&gt;View the GitHub Repository&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Rawbee is a full-stack video sharing and live streaming platform with traditional VOD features (uploads, subscriptions, watch history) alongside a WebRTC-based collaborative streaming engine for co-streaming, screen sharing, and in-browser voice/video chat.&lt;/p&gt;

&lt;p&gt;The current stack includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frontend:&lt;/strong&gt; React 18, TypeScript, Tailwind CSS, Vite&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; Node.js, Express&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database:&lt;/strong&gt; MongoDB&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Media:&lt;/strong&gt; Cloudinary&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Observability:&lt;/strong&gt; Sentry&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI debugging assistant:&lt;/strong&gt; Google Gemini&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For the Summer Bug Smash, I focused on improving the existing application rather than adding a new feature.&lt;/p&gt;

&lt;p&gt;My goal was simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Find real problems → measure them → understand the root cause → fix them → measure again.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;During the Bug Smash, I addressed frontend performance issues, a backend reliability problem, and runtime errors surfaced through Sentry.&lt;/p&gt;


&lt;h2&gt;
  
  
  Bug Fix or Performance Improvement
&lt;/h2&gt;

&lt;p&gt;As Rawbee grew, the homepage started doing more work than necessary.&lt;/p&gt;

&lt;p&gt;The first issue appeared while using the search bar. Updating the search state caused the parent component to re-render, and the video-card grid was repeatedly evaluated even when individual video data had not changed. React Profiler confirmed repeated &lt;code&gt;VideoCard&lt;/code&gt; renders during the interaction, which led me to investigate whether those renders were actually necessary.&lt;/p&gt;

&lt;p&gt;The second problem was visible directly in Chrome DevTools. The homepage was transferring a surprisingly large amount of data, with several individual image assets reaching hundreds of kilobytes.&lt;/p&gt;

&lt;p&gt;The original production trace contained images such as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;834 KB PNG
433 KB JPEG
160 KB JPEG
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I also found that the frontend was loading more JavaScript up front than necessary because page-level code was not being split efficiently.&lt;/p&gt;

&lt;p&gt;On the backend, MongoDB was failing to connect in my Windows environment with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;querySrv ECONNREFUSED
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Finally, Sentry was capturing frontend runtime errors that gave me useful visibility into failures occurring inside the application.&lt;/p&gt;

&lt;h2&gt;
  
  
  Controlled Before/After Benchmark
&lt;/h2&gt;

&lt;p&gt;To make the performance comparison meaningful, I benchmarked the &lt;strong&gt;before and after production builds&lt;/strong&gt; using the same setup:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Chrome&lt;/li&gt;
&lt;li&gt;Fast 4G throttling&lt;/li&gt;
&lt;li&gt;Browser cache disabled&lt;/li&gt;
&lt;li&gt;Same homepage&lt;/li&gt;
&lt;li&gt;Same machine&lt;/li&gt;
&lt;li&gt;Same production preview workflow&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Before&lt;/th&gt;
&lt;th&gt;After&lt;/th&gt;
&lt;th&gt;Improvement&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Network transferred&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2.0 MB&lt;/td&gt;
&lt;td&gt;471 KB&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;76.5% reduction&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Resources loaded&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2.3 MB&lt;/td&gt;
&lt;td&gt;767 KB&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;66.7% reduction&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Load event&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2.61 s&lt;/td&gt;
&lt;td&gt;1.60 s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;38.7% faster&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Finish&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2.82 s&lt;/td&gt;
&lt;td&gt;1.81 s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;35.8% faster&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Requests&lt;/td&gt;
&lt;td&gt;30&lt;/td&gt;
&lt;td&gt;32&lt;/td&gt;
&lt;td&gt;No improvement&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DOMContentLoaded&lt;/td&gt;
&lt;td&gt;593 ms&lt;/td&gt;
&lt;td&gt;624 ms&lt;/td&gt;
&lt;td&gt;Slightly higher&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;I am deliberately reporting the metrics that actually improved instead of dressing every measurement as a win. Request count went slightly up, partly because of a stale thumbnail returning 404, and DOMContentLoaded shifted marginally within measurement noise.&lt;/p&gt;

&lt;p&gt;The headline result is the &lt;strong&gt;76.5% payload reduction&lt;/strong&gt;.&lt;br&gt;
The biggest measurable gain came from reducing the amount of image data transferred to the browser.&lt;/p&gt;
&lt;h3&gt;
  
  
  Before: Production Benchmark
&lt;/h3&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%2Ft1um3ilrj881amyorbw8.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%2Ft1um3ilrj881amyorbw8.png" alt="Chrome DevTools Network panel showing the unoptimized production build with 30 requests, 2.0 MB transferred, 2.3 MB of resources, and a 2.61 second Load time" width="800" height="493"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Production baseline before optimization. The homepage transferred approximately 2.0 MB, dominated by unoptimized image assets — including an 834 KB PNG, a 433 KB JPG, and a 160 KB JPG.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  After: Production Benchmark
&lt;/h3&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%2Fq9lnkkegq42kh1rejyyj.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%2Fq9lnkkegq42kh1rejyyj.png" alt="Chrome DevTools Network panel showing the optimized production build with reduced image payload and improved loading performance" width="800" height="519"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Same page, same throttling, same cache-disabled conditions. Payload dropped from 2.0 MB to 471 KB and Load time from 2.61 s to 1.60 s.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;The complete implementation is available in the &lt;a href="https://github.com/Pritam-mb/rawbee/pull/1" rel="noopener noreferrer"&gt;GitHub Pull Request&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The main changes covered:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;React.memo
Cloudinary image transformations
React.lazy / Suspense
MongoDB connection workaround
Sentry configuration improvements
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  1. Memoizing &lt;code&gt;VideoCard&lt;/code&gt;
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;memo&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;formatDuration&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;seconds&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// ...&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;formatViews&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;views&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// ...&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;VideoCard&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;memo&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;VideoCard&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="nx"&gt;video&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}:&lt;/span&gt; &lt;span class="nx"&gt;VideoCardProps&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"group cursor-pointer"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="cm"&gt;/* Video card UI */&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nx"&gt;VideoCard&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The important optimization here is &lt;code&gt;React.memo&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;When the parent component updates, React can skip rendering the memoized &lt;code&gt;VideoCard&lt;/code&gt; if the &lt;code&gt;video&lt;/code&gt; prop remains referentially equal.&lt;/p&gt;

&lt;p&gt;I also moved pure formatting helpers outside the component so they are not recreated as part of each component execution.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Cloudinary Image Optimization
&lt;/h3&gt;

&lt;p&gt;This was the single biggest performance win in the benchmark. An 834 KB PNG for a card thumbnail was far larger than necessary for the displayed dimensions.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;getOptimizedCloudinaryUrl&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nx"&gt;width&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;500&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;url&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;cloudinary.com&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;url&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;/upload/&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;`/upload/w_&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;width&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;/f_auto/q_auto/`&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;img&lt;/span&gt;
  &lt;span class="na"&gt;src&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;getOptimizedCloudinaryUrl&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;video&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;thumbnail&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;500&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;alt&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;video&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The w_500 resizes to display dimensions, f_auto serves modern formats (WebP/AVIF) where supported, and q_auto picks quality intelligently.&lt;/p&gt;

&lt;p&gt;The before trace contained image responses of 834 KB, 433 KB, and 160 KB. The after trace shows the same images at 7.3 KB, 2.0 KB, 22.0 KB, and 2.6 KB. This single change is the primary contributor to the 2.0 MB → 471 KB reduction.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Route-Level Code Splitting
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;lazy&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Suspense&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;Home&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;lazy&lt;/span&gt;&lt;span class="p"&gt;(()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;./pages/Home&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;Login&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;lazy&lt;/span&gt;&lt;span class="p"&gt;(()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;./pages/Login&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;App&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Router&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Suspense&lt;/span&gt;
        &lt;span class="na"&gt;fallback&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;
          &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"flex h-screen items-center justify-center"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
            Loading application...
          &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;div&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="si"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Routes&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
          &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Route&lt;/span&gt; &lt;span class="na"&gt;path&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/login"&lt;/span&gt; &lt;span class="na"&gt;element&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Login&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
          &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Route&lt;/span&gt; &lt;span class="na"&gt;path&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/"&lt;/span&gt; &lt;span class="na"&gt;element&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Home&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
        &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Routes&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Suspense&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Router&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This moved page-specific JavaScript into route-level chunks instead of requiring every page to be part of the initial route workload.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Sentry Environment Configuration
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight diff"&gt;&lt;code&gt;// frontend/.env
&lt;span class="err"&gt;
&lt;/span&gt;&lt;span class="gi"&gt;+ VITE_SENTRY_DSN=your_dsn_here
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight diff"&gt;&lt;code&gt;// frontend/src/main.tsx
&lt;span class="err"&gt;
&lt;/span&gt;&lt;span class="p"&gt;Sentry.init({
&lt;/span&gt;&lt;span class="gd"&gt;-  dsn: "your_dsn_here",
&lt;/span&gt;&lt;span class="gi"&gt;+  dsn: import.meta.env.VITE_SENTRY_DSN,
&lt;/span&gt;});
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This makes the configuration easier to manage across different environments.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. MongoDB DNS Failure
&lt;/h3&gt;

&lt;p&gt;The backend was failing with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;querySrv ECONNREFUSED
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I investigated the DNS behavior in the Windows environment and used:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Resolve-DnsName&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;mongodb-host&lt;/span&gt;&lt;span class="err"&gt;&amp;gt;&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;to verify the DNS resolution problem.&lt;/p&gt;

&lt;p&gt;I then switched to a direct MongoDB connection configuration as a workaround for the affected environment, restoring database connectivity.&lt;/p&gt;




&lt;h2&gt;
  
  
  My Improvements
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Eliminating unnecessary React work
&lt;/h3&gt;

&lt;p&gt;The first performance problem was component-level rendering.&lt;/p&gt;

&lt;p&gt;A search update causes the &lt;code&gt;Home&lt;/code&gt; component to update, but an individual video card does not necessarily need to update with it.&lt;/p&gt;

&lt;p&gt;Before optimization:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Search state changes
        ↓
Home updates
        ↓
VideoCard repeatedly renders
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After optimization:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Search state changes
        ↓
Home updates
        ↓
React.memo checks props
        ↓
VideoCard render skipped when props are unchanged
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  React Profiler Evidence
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;React Profiler evidence — before:&lt;/strong&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%2Fryav79n2bb1ripr0qrds.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%2Fryav79n2bb1ripr0qrds.png" alt="React DevTools Profiler showing VideoCard rendering repeatedly during the unoptimized search interaction" width="799" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Before memoization: VideoCard renders repeatedly across the profiling session as parent state updates.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;React Profiler evidence — after:&lt;/strong&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%2Fo9x96aqdpi88xg6nsw6c.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%2Fo9x96aqdpi88xg6nsw6c.png" alt="React DevTools Profiler showing VideoCard2 as a memoized component that did not render during the optimized interaction" width="800" height="498"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;After memoization: the Profiler explicitly reports "Did not render on the client during this profiling session." The memoized component is skipped entirely when props are unchanged.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;React Profiler evidence for the memoized component. The optimized &lt;code&gt;VideoCard&lt;/code&gt; was skipped during the recorded interaction when its props remained unchanged.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I am intentionally not presenting the React commit count itself as the number of renders. The important result is that the profiler directly shows the memoized component being skipped.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Reducing image payload
&lt;/h3&gt;

&lt;p&gt;The largest measurable performance improvement came from image delivery.&lt;/p&gt;

&lt;p&gt;The original production trace contained image resources such as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;834 KB
433 KB
160 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After applying Cloudinary transformations, the optimized trace contained much smaller responses, including examples around:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;7.3 KB
2.0 KB
22.0 KB
2.6 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This change was the main contributor to:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;2.0 MB → 471 KB
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;or a &lt;strong&gt;76.5% reduction in transferred data&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Reducing initial JavaScript work
&lt;/h3&gt;

&lt;p&gt;The route-level &lt;code&gt;React.lazy()&lt;/code&gt; change means that the browser no longer needs to load code for every page before the current route can operate.&lt;/p&gt;

&lt;p&gt;Before:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Initial application
├── Home
├── Login
├── other route code
└── dependencies
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Initial route
├── shared dependencies
└── current page chunk

Additional page
└── loaded on demand
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This keeps the initial route focused on the code it actually needs.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Backend reliability improvement
&lt;/h3&gt;

&lt;p&gt;The MongoDB issue was not treated as a performance metric because it was fundamentally a reliability problem.&lt;/p&gt;

&lt;p&gt;The debugging process was:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;MongoDB connection fails
        ↓
querySrv ECONNREFUSED
        ↓
DNS investigation
        ↓
Resolve-DnsName verification
        ↓
Direct connection workaround
        ↓
Backend connectivity restored
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This fix removed a development blocker that was preventing the API from connecting to the database.&lt;/p&gt;




&lt;h2&gt;
  
  
  Best Use of Sentry
&lt;/h2&gt;

&lt;p&gt;I am submitting this project for the &lt;strong&gt;Best Use of Sentry&lt;/strong&gt; category.&lt;/p&gt;

&lt;p&gt;Sentry became part of the debugging workflow rather than simply being another dependency.&lt;/p&gt;

&lt;p&gt;The workflow was:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Runtime problem
      ↓
Sentry captures the event
      ↓
Inspect issue + stack trace
      ↓
Locate affected code
      ↓
Fix
      ↓
Verify application behavior
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;During development, Sentry captured frontend runtime errors including:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ReferenceError: VideoSkeleton is not defined
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Sentry provided:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;issue details&lt;/li&gt;
&lt;li&gt;event information&lt;/li&gt;
&lt;li&gt;stack trace&lt;/li&gt;
&lt;li&gt;browser/environment context&lt;/li&gt;
&lt;li&gt;affected execution path&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That helped me move from:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Something is broken."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;to:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"This specific code path is failing for this specific reason."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Sentry Evidence
&lt;/h3&gt;

&lt;p&gt;Sentry became part of my debugging loop, not just a dependency in package.json. The workflow was consistent throughout the Bug Smash:&lt;/p&gt;

&lt;p&gt;Runtime failure → Sentry captures event → inspect issue + stack trace + context → locate affected code → fix → verify.&lt;/p&gt;

&lt;p&gt;One concrete example: during a refactor, I accidentally removed an import for VideoSkeleton. It didn't crash the build — it only threw at runtime when the loading state triggered. Without Sentry I'd have found it eventually when a user reported a blank page. With Sentry, I had it within minutes:&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%2Fo9hbila26fx96lrq5vwy.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%2Fo9hbila26fx96lrq5vwy.png" alt="Sentry issue page showing the ReferenceError VideoSkeleton is not defined with its stack trace and debugging context" width="800" height="484"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Sentry captured the ReferenceError with the full stack trace, release hash, browser and OS context, and event breadcrumbs. This turned "the page is broken sometimes" into a single actionable issue with a direct line to the failing code path.&lt;/p&gt;

&lt;p&gt;What Sentry gave me that my terminal couldn't: the release hash tying the error to a specific build, the browser and OS the user hit it on, the URL and route where it happened, and the trace ID linking to surrounding events. That context is what turned a five-word error into a five-minute fix.&lt;/p&gt;

&lt;p&gt;Importantly, I used Sentry for runtime observability and React Profiler for component rendering analysis — I didn't conflate them. Sentry told me what was failing; the Profiler told me how components were rendering. Keeping those two evidence streams separate gave me a cleaner picture of the application's actual behavior.&lt;/p&gt;




&lt;h2&gt;
  
  
  Best Use of Google AI
&lt;/h2&gt;

&lt;p&gt;I am also submitting this project for the &lt;strong&gt;Best Use of Google AI&lt;/strong&gt; category.&lt;/p&gt;

&lt;p&gt;I used &lt;strong&gt;Gemini 3.1 Pro&lt;/strong&gt; as a debugging partner during the Bug Smash rather than simply asking it to generate the implementation.&lt;/p&gt;

&lt;p&gt;The clearest example was the MongoDB connection problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Problem
&lt;/h3&gt;

&lt;p&gt;The backend returned:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;querySrv ECONNREFUSED
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and the application could not establish its database connection.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Gemini investigation
&lt;/h3&gt;

&lt;p&gt;I provided Gemini with the error and information about my Windows environment.&lt;/p&gt;

&lt;p&gt;Gemini analyzed the failure and suggested investigating DNS and IPv4/IPv6 resolution behavior.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Independent verification
&lt;/h3&gt;

&lt;p&gt;I did not blindly copy the recommendation.&lt;/p&gt;

&lt;p&gt;I ran the diagnostic myself:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;Resolve-DnsName&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;mongodb-host&lt;/span&gt;&lt;span class="err"&gt;&amp;gt;&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and verified the DNS resolution problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Implementation
&lt;/h3&gt;

&lt;p&gt;After confirming the issue, I changed the MongoDB connection strategy to use a direct connection configuration that avoided the failing SRV-resolution path.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Result
&lt;/h3&gt;

&lt;p&gt;The backend was able to reconnect to MongoDB and resume normal operation.&lt;/p&gt;

&lt;p&gt;The overall debugging loop became:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;querySrv ECONNREFUSED
        ↓
Gemini analysis
        ↓
DNS hypothesis
        ↓
Resolve-DnsName verification
        ↓
Connection workaround
        ↓
Backend restored
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;I treated Gemini's response as a hypothesis, not as the final answer. I independently verified the DNS behavior before changing the MongoDB connection strategy.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Gemini Evidence
&lt;/h3&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%2Fxjiirxdbgbbofewggcow.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%2Fxjiirxdbgbbofewggcow.png" alt="Gemini 3.1 Pro conversation analyzing the MongoDB querySrv ECONNREFUSED DNS and IPv4 IPv6 issue" width="799" height="499"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Use the screenshot showing Gemini analyzing the &lt;code&gt;querySrv ECONNREFUSED&lt;/code&gt; problem and discussing the DNS/connection investigation.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Suggested caption: Gemini helped narrow down the MongoDB connection failure; I independently verified the suggested diagnostic path before implementing the workaround.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The important part for me was not simply generating code faster. It was shortening the path from an unfamiliar error to a testable hypothesis.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Impact
&lt;/h2&gt;

&lt;p&gt;The clearest measured result was the reduction in network transfer:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.0 MB → 471 KB&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's a &lt;strong&gt;76.5% reduction&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The Load event changed from:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.61 s → 1.60 s&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;which is a &lt;strong&gt;38.7% reduction in Load time&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The total resource footprint changed from:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.3 MB → 767 KB&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;which is a &lt;strong&gt;66.7% reduction&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The React Profiler also showed that the optimized &lt;code&gt;VideoCard&lt;/code&gt; could be skipped during the recorded search interaction when its props remained unchanged.&lt;/p&gt;

&lt;p&gt;The MongoDB issue was resolved as a backend reliability fix, while Sentry and Gemini made the debugging workflow more observable and efficient.&lt;/p&gt;




&lt;h2&gt;
  
  
  What I Deliberately Did Not Claim
&lt;/h2&gt;

&lt;p&gt;Not every metric improved.&lt;/p&gt;

&lt;p&gt;Request count moved from 30 to 32, partly because a stale thumbnail returned 404. DOMContentLoaded moved from 593 ms to 624 ms, which I consider within the noise of this benchmark.&lt;/p&gt;

&lt;p&gt;The strongest measured result is the reduction in transferred data from 2.0 MB to 471 KB, followed by the Load improvement from 2.61 s to 1.60 s.&lt;/p&gt;

&lt;p&gt;The Sentry runtime event shown in this post was captured in development; validating the same workflow against production traffic is a next step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Future Roadmap for Rawbee
&lt;/h2&gt;

&lt;p&gt;The Bug Smash was focused on performance and reliability, but I also have a larger direction planned for Rawbee.&lt;/p&gt;

&lt;p&gt;The next stage is to turn Rawbee from a traditional video-sharing application into a more interactive, social streaming platform.&lt;/p&gt;

&lt;p&gt;Planned future work includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Live Rooms&lt;/strong&gt; where users can create and join shared sessions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WebRTC video/audio calling&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Screen sharing&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Real-time room chat using Socket.io&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synchronized watch experiences&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Multi-user collaborative streaming&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Host controls and participant management&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is to let users watch and interact together without needing a separate Discord or video-call application.&lt;/p&gt;

&lt;p&gt;These real-time features are &lt;strong&gt;future work&lt;/strong&gt; and are not included in the performance measurements reported in this Bug Smash submission.&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;This Bug Smash started with a simple observation: Rawbee was getting slower as the application grew.&lt;/p&gt;

&lt;p&gt;Instead of rewriting large parts of the project, I used measurement and debugging tools to identify where the actual problems were.&lt;/p&gt;

&lt;p&gt;The result was a focused set of improvements:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;React.memo
      ↓
Less unnecessary rendering

Cloudinary transformations
      ↓
Smaller image payloads

React.lazy + Suspense
      ↓
Route-level code splitting

DNS investigation + MongoDB workaround
      ↓
Backend reliability restored

Sentry
      ↓
Runtime visibility

Gemini
      ↓
Faster debugging investigation
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The biggest measurable performance improvement was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.0 MB → 471 KB transferred&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;with the production Load event improving from:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;2.61 s → 1.60 s&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The main takeaway is simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before optimizing code, measure what the application is actually doing.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That is what I tried to do throughout this Bug Smash: identify the real bottlenecks, fix them deliberately, and verify the results instead of relying on assumptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub Pull Request:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/rawbee/pull/1" rel="noopener noreferrer"&gt;View PR #1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Repository:&lt;/strong&gt; &lt;a href="https://github.com/Pritam-mb/rawbee" rel="noopener noreferrer"&gt;View Rawbee on GitHub&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Thanks for checking out my submission!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>bugsmash</category>
      <category>ai</category>
      <category>sentry</category>
    </item>
  </channel>
</rss>
