<?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: mannubaveja007</title>
    <description>The latest articles on DEV Community by mannubaveja007 (@mannubaveja007).</description>
    <link>https://dev.to/mannubaveja007</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%2F2352433%2F3483911d-6943-448f-ba5d-00097b44af32.jpeg</url>
      <title>DEV Community: mannubaveja007</title>
      <link>https://dev.to/mannubaveja007</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mannubaveja007"/>
    <language>en</language>
    <item>
      <title>kabristan - Yes Ignore it! and You Will Suffer Later</title>
      <dc:creator>mannubaveja007</dc:creator>
      <pubDate>Sat, 31 Oct 2026 12:00:37 +0000</pubDate>
      <link>https://dev.to/mannubaveja007/necropolis-the-ghost-16cb</link>
      <guid>https://dev.to/mannubaveja007/necropolis-the-ghost-16cb</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;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;kabristan&lt;/strong&gt; turns a &lt;code&gt;package.json&lt;/code&gt; into a graveyard.&lt;/p&gt;

&lt;p&gt;Paste a manifest, press &lt;strong&gt;Raise the dead&lt;/strong&gt;, and every dependency rises as an SVG headstone. Each stone is carved with the package name, the version you asked for, the real latest publish date from the npm registry, and how many years it has been resting. The stones are coloured by fate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;alive&lt;/strong&gt;, published within the last year, moonlit green&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;restless&lt;/strong&gt;, one to two years, pale gold&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;haunted&lt;/strong&gt;, the registry returns a deprecation notice, violet with a slow ghost glow&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;dead&lt;/strong&gt;, more than two years since the last publish, ash grey with cracks and moss&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;unknown&lt;/strong&gt;, a 404 or an unreachable registry, cold slate with a dashed outline&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A summary band counts the five fates and computes a &lt;strong&gt;Haunting Score&lt;/strong&gt; from 0 to 100. Click any stone and a local Gemma model, served through Ollama, writes a two-sentence epitaph and a one-sentence maintenance warning from five registry facts. The whole yard exports as a Markdown report.&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%2F4bfsf14230dtwlepnokh.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%2F4bfsf14230dtwlepnokh.png" alt="kabristan graveyard: seven headstones in a dark violet fog, with version, last publish and years since publish carved into each stone" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My reading of &lt;strong&gt;Ghost in the Machine&lt;/strong&gt; is literal: the machine is the dependency tree, and the ghosts are the packages nobody maintains any more. A &lt;code&gt;package.json&lt;/code&gt; is a burial register we keep adding names to. kabristan just makes the register visible, and lets a local model speak for the dead.&lt;/p&gt;

&lt;p&gt;It felt right to ship it on Halloween, the night before Día de los Muertos.&lt;/p&gt;

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

&lt;p&gt;There is no hosted demo, and that is deliberate: the model runs on your machine, not mine.&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/mannubaveja007/kabristan.git
&lt;span class="nb"&gt;cd &lt;/span&gt;kabristan
npm &lt;span class="nb"&gt;install
&lt;/span&gt;ollama pull gemma3:4b
ollama serve
npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;Open &lt;code&gt;http://localhost:3000&lt;/code&gt;, press &lt;strong&gt;Load sample&lt;/strong&gt;, then &lt;strong&gt;Raise the dead&lt;/strong&gt;. The sample includes &lt;code&gt;request&lt;/code&gt;, &lt;code&gt;node-sass&lt;/code&gt;, &lt;code&gt;left-pad&lt;/code&gt;, &lt;code&gt;moment&lt;/code&gt;, &lt;code&gt;express&lt;/code&gt;, &lt;code&gt;react&lt;/code&gt; and &lt;code&gt;typescript&lt;/code&gt;, which is enough to fill the yard with three haunted stones and four living ones.&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%2Fcsw5gvk2eksbr5fvgimf.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%2Fcsw5gvk2eksbr5fvgimf.png" alt="The landing page: a package.json textarea, a Load sample button and a Raise the dead button" width="800" height="500"&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%2F4n0i3v0v9lc8c8muqsdb.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%2F4n0i3v0v9lc8c8muqsdb.png" alt="The epitaph panel: a Gemma-written epitaph for left-pad and a maintenance warning" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;The repository is public and self-contained:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/mannubaveja007/kabristan" rel="noopener noreferrer"&gt;https://github.com/mannubaveja007/kabristan&lt;/a&gt;&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/mannubaveja007" rel="noopener noreferrer"&gt;
        mannubaveja007
      &lt;/a&gt; / &lt;a href="https://github.com/mannubaveja007/kabristan" rel="noopener noreferrer"&gt;
        kabristan
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      Kabristan: a graveyard for your dependencies, read by a local Gemma model
    &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;Kabristan 🪦&lt;/h1&gt;
&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;A quiet kabristan for your dependencies. Paste a &lt;code&gt;package.json&lt;/code&gt;, and every package rises as a headstone with a registry-verified fate, a Haunting Score, and an epitaph written locally by Gemma through Ollama.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a rel="noopener noreferrer" href="https://github.com/mannubaveja007/kabristan/docs/screenshots/headstones.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%2Fmannubaveja007%2Fkabristan%2FHEAD%2Fdocs%2Fscreenshots%2Fheadstones.png" alt="The Kabristan: seven headstones under emerald mist, each carved with a package name, version, last publish date and years since publish" width="920"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Architecture Overview&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;┌──────────────────────────────────────────────────────────────────┐
│ Browser — Next.js 16 client                                      │
│ paste package.json → Raise the dead → Kabristan                  │
└──────────────────────────────┬───────────────────────────────────┘
                               │ POST /api/scan
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ Next.js route handlers (App Router, RSC)                         │
│ POST /api/scan · POST /api/epitaph · GET /api/health             │
└──────────────────────────────┬───────────────────────────────────┘
                               │ Promise.all
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ registry.npmjs.org — one GET per package                         │
│ 5s timeout · latest · time[latest] · deprecated                  │
└──────────────────────────────┬───────────────────────────────────┘
                               │ statuses → headstones → click a stone
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ Ollama — local Gemma, format:"json"                              │
│ validate → memory cache → template fallback                      │
└──────────────────────────────┬───────────────────────────────────┘
                               ▼
                               Epitaph panel · Markdown report
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Method&lt;/th&gt;
&lt;th&gt;Route&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;POST&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;/api/scan&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Body &lt;code&gt;{ packageJson }&lt;/code&gt;; returns &lt;code&gt;{ packages, summary&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/mannubaveja007/kabristan" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;



&lt;p&gt;The app is Next.js 16 on the App Router, with TypeScript, Tailwind CSS 4, and shadcn/ui primitives. The interesting parts are small and readable:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;src/lib/npm.ts&lt;/code&gt; parses the manifest, fetches each package in parallel with a 5-second timeout, and maps deprecation notices and publish age onto the five fates.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;src/lib/epitaph.ts&lt;/code&gt; builds the Ollama request, validates the JSON, caches answers per &lt;code&gt;name@version&lt;/code&gt;, and falls back to a deterministic template when the model is unavailable.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;src/components/tombstone.tsx&lt;/code&gt; draws the slab, cracks, moss and ghost glow as inline SVG.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Run the checks yourself:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;test&lt;/span&gt;          &lt;span class="c"&gt;# 52 tests&lt;/span&gt;
npm run typecheck
npm run build
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;

&lt;p&gt;kabristan is one Next.js app with three route handlers. The browser only renders; the registry and the model are both called server-side.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;┌──────────────────────────────────────────────────────────────────┐
│ Browser — Next.js 16 client                                      │
│ paste package.json → Raise the dead → graveyard                  │
└──────────────────────────────┬───────────────────────────────────┘
                               │ POST /api/scan
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ Next.js route handlers (App Router, RSC)                         │
│ POST /api/scan · POST /api/epitaph · GET /api/health             │
└──────────────────────────────┬───────────────────────────────────┘
                               │ Promise.all
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ registry.npmjs.org — one GET per package                         │
│ 5s timeout · latest · time[latest] · deprecated                  │
└──────────────────────────────┬───────────────────────────────────┘
                               │ statuses → headstones → click a stone
                               ▼
┌──────────────────────────────────────────────────────────────────┐
│ Ollama — local Gemma, format:"json"                              │
│ validate → memory cache → template fallback                      │
└──────────────────────────────┬───────────────────────────────────┘
                               ▼
                               Epitaph panel · Markdown report
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;The order of one scan:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;POST /api/scan&lt;/code&gt; parses &lt;code&gt;dependencies&lt;/code&gt; and &lt;code&gt;devDependencies&lt;/code&gt;, dedupes them, and stops at 40 packages.&lt;/li&gt;
&lt;li&gt;Every package is fetched from &lt;code&gt;registry.npmjs.org&lt;/code&gt; in parallel, with a 5-second timeout each.&lt;/li&gt;
&lt;li&gt;Each result becomes a fate: &lt;code&gt;alive&lt;/code&gt;, &lt;code&gt;restless&lt;/code&gt;, &lt;code&gt;haunted&lt;/code&gt;, &lt;code&gt;dead&lt;/code&gt; or &lt;code&gt;unknown&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The summary counts the fates and computes the Haunting Score.&lt;/li&gt;
&lt;li&gt;The browser paints the headstones; clicking one calls &lt;code&gt;POST /api/epitaph&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The epitaph is validated, cached, or replaced by the deterministic template.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Export graveyard report&lt;/strong&gt; builds the Markdown file in the browser.&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Method&lt;/th&gt;
&lt;th&gt;Route&lt;/th&gt;
&lt;th&gt;Responsibility&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;POST&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;/api/scan&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Validate the manifest, resolve every package, return &lt;code&gt;{ packages, summary }&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;POST&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;/api/epitaph&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Take five facts, call Ollama, validate JSON, cache, fall back&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;GET&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;/api/health&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Probe Ollama for the header dot&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The project is deliberately small and ordered by responsibility:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;kabristan/
├── src/
│   ├── app/
│   │   ├── api/                    # scan, epitaph, health
│   │   ├── globals.css             # tokens, fog, headstone styles
│   │   ├── layout.tsx              # fonts and shell
│   │   └── page.tsx                # landing and graveyard states
│   ├── components/
│   │   ├── tombstone.tsx           # SVG slab, cracks, moss, glow
│   │   ├── tombstone-grid.tsx      # responsive grid
│   │   ├── summary-bar.tsx         # counts and Haunting Score
│   │   ├── epitaph-panel.tsx       # sheet, request, cache, fallback
│   │   └── loading-graveyard.tsx   # skeletons
│   └── lib/
│       ├── npm.ts                  # parse, fetch, statuses, score
│       ├── epitaph.ts              # prompt, cache, template
│       ├── report.ts               # Markdown export
│       └── types.ts                # shared contracts
└── docs/screenshots/               # README and post images
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



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

&lt;h3&gt;
  
  
  The AI
&lt;/h3&gt;

&lt;p&gt;The only model in the loop is &lt;strong&gt;Gemma, running locally through Ollama&lt;/strong&gt;. There is no hosted LLM, no API key, and no account.&lt;/p&gt;

&lt;p&gt;When you click a stone, the browser posts exactly five facts to &lt;code&gt;/api/epitaph&lt;/code&gt;: name, version, last publish, years since publish, and the deprecation message. Nothing else. The route sends those facts to Ollama with &lt;code&gt;stream: false&lt;/code&gt; and &lt;code&gt;format: "json"&lt;/code&gt;, under this system prompt:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;You are a gravedigger poet. Using ONLY the facts given, write a 2-sentence epitaph and a 1-sentence maintenance warning. Never invent dates, versions, CVEs or package names. Name a replacement only if the deprecation message names one; otherwise write 'successor unknown'. Return JSON {epitaph, warning}.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The response is parsed as JSON and rejected unless both fields are non-empty strings. Successful answers are cached in memory. Anything else, a closed port, a timeout, a malformed answer, falls back to a template that repeats only the facts it was given. The panel says &lt;strong&gt;Ghost offline: template epitaph&lt;/strong&gt; when that happens, so the failure is visible instead of hidden.&lt;/p&gt;

&lt;p&gt;My first version used a 60-second timeout. The first local 12B generation ran past it, and the request came back at 62.8 seconds with the template. I measured it, raised the default to 180 seconds, and the next call returned a real epitaph in 88 seconds. The wait is shown as a skeleton, and the answer is cached afterwards.&lt;/p&gt;

&lt;h3&gt;
  
  
  The design
&lt;/h3&gt;

&lt;p&gt;The interface is built with the open-source &lt;strong&gt;Hallmark&lt;/strong&gt; design skill, vendored in the repository. It is a dark-gothic direction: near-black &lt;code&gt;#0b0a12&lt;/code&gt;, violet and moonlit-green accents, Cormorant Garamond for display, Geist for text, and JetBrains Mono for carved data such as versions and dates.&lt;/p&gt;

&lt;p&gt;The stones are inline SVG so they can decay with the data: cracks and moss appear only on dead packages, a slow ghost glow only on haunted ones, and hover raises a candlelight wash at the base of the stone. Everything collapses under &lt;code&gt;prefers-reduced-motion&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;I ran Hallmark's &lt;code&gt;sloplint&lt;/code&gt; render sweep from 320 to 1920 pixels. It reports &lt;strong&gt;0 FAIL, 0 WARN&lt;/strong&gt;, with two documented dismissals, the sheet scrim and the wrapping tombstone metadata.&lt;/p&gt;

&lt;h3&gt;
  
  
  The agents
&lt;/h3&gt;

&lt;p&gt;I built kabristan with three parallel subagents in the DeepSeek Harness, each in its own git worktree:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;one for the API routes and the registry logic&lt;/li&gt;
&lt;li&gt;one for the graveyard UI&lt;/li&gt;
&lt;li&gt;one for the Markdown report and documentation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The work landed on three branches (&lt;code&gt;feat/api-core&lt;/code&gt;, &lt;code&gt;feat/graveyard-ui&lt;/code&gt;, &lt;code&gt;feat/report-docs&lt;/code&gt;), each merged into &lt;code&gt;main&lt;/code&gt; with a &lt;code&gt;--no-ff&lt;/code&gt; merge commit. The history is conventional commits: &lt;code&gt;feat(scan)&lt;/code&gt;, &lt;code&gt;fix(ui)&lt;/code&gt;, &lt;code&gt;docs&lt;/code&gt;, one logical change per commit.&lt;/p&gt;

&lt;p&gt;That workflow paid for itself. When the machine got slow I could stop all three, see exactly what each had written, and resume them without losing work.&lt;/p&gt;

&lt;h3&gt;
  
  
  What broke
&lt;/h3&gt;

&lt;p&gt;Three things, all fixed and committed:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The 60-second model timeout above.&lt;/li&gt;
&lt;li&gt;Turbopack's CSS rule flattened CSS modules, so the headstone styles loaded as global CSS while the component's class names came back empty. The stones rendered as black shapes with raw text below them. I moved the styles into the global stylesheet with prefixed class names.&lt;/li&gt;
&lt;li&gt;A browser extension injected dozens of &lt;code&gt;data-*&lt;/code&gt; attributes onto &lt;code&gt;&amp;lt;html&amp;gt;&lt;/code&gt; before hydration, which made React report a mismatch. I reproduced it by injecting the same attributes at document start in headless Chrome, then fixed it with &lt;code&gt;suppressHydrationWarning&lt;/code&gt; on the document elements, which tolerates attribute differences without hiding real markup mismatches.&lt;/li&gt;
&lt;/ol&gt;

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

&lt;p&gt;kabristan is possible because the model is a file on my disk, not a service.&lt;/p&gt;

&lt;p&gt;That changes the privacy story completely. Dependency names are the most sensitive part of a private codebase: they reveal what you build, which vendors you depend on, and where you are behind. With a hosted model, every click on a stone would ship that list to someone else's server. With Ollama, the names go to the public npm registry, which already has them, and the five facts go to a model running on the same laptop. My footer says exactly that, and it is true.&lt;/p&gt;

&lt;p&gt;It also changes who can build this. There is no key to provision, no free-tier limit, no bill at the end of the month. A student on a five-year-old laptop can run a 3B model and get the whole experience. When the model is missing or too slow, the app still works, because the deterministic fallback does not depend on anyone's API being healthy.&lt;/p&gt;

&lt;p&gt;And it changes what the app can be. A closed API couples the product to one vendor's model, prompt format and failure modes. Here, &lt;code&gt;OLLAMA_MODEL&lt;/code&gt; is one environment variable. Swap in a smaller Gemma, a bigger one, or a different open-weight model, and the graveyard still works. The design skill, the harness, and the code are all in the repository, so the whole thing can be read, forked and argued with.&lt;/p&gt;

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

&lt;p&gt;The session lives in the git history rather than a recording. The three feature branches, their individual commits, and the merge commits that joined them to &lt;code&gt;main&lt;/code&gt; are public, and they show the actual sequence: scaffold, design system, API core, graveyard UI, report and docs, and the fixes that came after testing against a real registry and a real local model.&lt;/p&gt;

&lt;p&gt;The harness also kept the work honest. Every agent had to run &lt;code&gt;tsc&lt;/code&gt; and Vitest before committing, and the final integration had to survive a production build plus the Hallmark render sweep.&lt;/p&gt;

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

&lt;p&gt;The moment that landed for me was &lt;code&gt;left-pad&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;This is a package that was famously unpublished in 2016 and broke builds across the internet. A decade later it is deprecated, eight and a half years past its last release, and the model wrote this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;left-pad sleeps after 8.6 years. Its final publication was 2018-04-09T01:10:45.796Z.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And this warning:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Use String.prototype.padStart() as the successor.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It is not profound. It is just accurate, plain, and a little sad, which is exactly what a graveyard is for. A local model, given nothing but five facts, looked at a package that once took down half the JavaScript ecosystem and quietly noted that &lt;code&gt;padStart&lt;/code&gt; won.&lt;/p&gt;

&lt;p&gt;That is the ghost in the machine for me. Not a haunted chatbot, just the machine remembering what we buried, one dependency at a time.&lt;/p&gt;

&lt;p&gt;The graveyard is open. Bring your &lt;code&gt;package.json&lt;/code&gt;.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Syapa: The Sloth's Secret Weapon Against Freelance Scope Creep (Powered by Gemma &amp; Local AI)</title>
      <dc:creator>mannubaveja007</dc:creator>
      <pubDate>Sun, 25 Oct 2026 17:13:28 +0000</pubDate>
      <link>https://dev.to/mannubaveja007/syapa-the-sloths-secret-weapon-against-freelance-scope-creep-powered-by-gemma-local-ai-175o</link>
      <guid>https://dev.to/mannubaveja007/syapa-the-sloths-secret-weapon-against-freelance-scope-creep-powered-by-gemma-local-ai-175o</guid>
      <description>&lt;p&gt;&lt;em&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;/em&gt;&lt;/p&gt;




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

&lt;p&gt;Every freelancer knows the dread of post-meeting administrative chores. &lt;/p&gt;

&lt;p&gt;You finish an intense 60-minute call with a client. Instead of relaxing, you face an exhausting to-do list: re-listening to call recordings, combing through pages of notes, spotting where the client casually snuck in unbilled extra features (&lt;em&gt;"Can we also just add an SMS notification drip and student portal?"&lt;/em&gt;), catching moments where you accidentally gave away free work (&lt;em&gt;"Sure, I can look into that this weekend"&lt;/em&gt;), and drafting an uncomfortable pushback email.&lt;/p&gt;

&lt;p&gt;In honor of &lt;strong&gt;International Sloth Day&lt;/strong&gt;, I built &lt;strong&gt;Syapa&lt;/strong&gt; (meaning &lt;em&gt;“chaos”&lt;/em&gt; or &lt;em&gt;“headache”&lt;/em&gt; in Punjabi/Hindi)—a precision freelance intelligence platform designed to do all of that heavy lifting so you don't have to. &lt;/p&gt;

&lt;p&gt;Syapa lets freelancers channel their inner sloth:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;One-Click Audio Capture&lt;/strong&gt;: Click "Start Recording" inside a lightweight Chrome Manifest V3 side panel during any Google Meet, Zoom, or browser call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero Post-Meeting Effort&lt;/strong&gt;: Once the call ends, you literally walk away. Syapa’s asynchronous background pipeline automatically transcribes the conversation with speaker diarization ("You" vs. "Others"), chunks and embeds the dialogue locally, and runs &lt;strong&gt;Google Gemma&lt;/strong&gt; to extract an executive summary, action items, sneaky scope creep, and dangerous unbilled promises.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic Hallucination Filter&lt;/strong&gt;: All extracted quotes are verified verbatim against the raw transcript using deterministic string validation. No fabricated client statements or hallucinated promises.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automated Boundary Coaching&lt;/strong&gt;: Syapa generates copy-pasteable negotiation pushbacks and formal change orders ready to send to the client.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interactive Sparring Room&lt;/strong&gt;: Before having that difficult conversation, practice your pushback against realistic client personas (like &lt;em&gt;Mr. Sharma&lt;/em&gt;, the budget-pinching coaching center owner) using conversational AI.&lt;/li&gt;
&lt;/ol&gt;




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

&lt;p&gt;🎥 &lt;strong&gt;Video Walkthrough &amp;amp; Architecture Tour&lt;/strong&gt;:&lt;br&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%2Fmannu.codes%2F" 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%2Fmannu.codes%2F" alt="Watch Syapa in Action" width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Local-First Architecture: Because Syapa runs local edge inference via Ollama and a native Chrome Manifest V3 side panel for privacy reasons, the video walkthrough demonstrates the full end-to-end recording, pipeline processing, and interactive sparring session live).&lt;/em&gt;&lt;/p&gt;


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

&lt;p&gt;Syapa is completely open-source under the MIT License:&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/mannubaveja007" rel="noopener noreferrer"&gt;
        mannubaveja007
      &lt;/a&gt; / &lt;a href="https://github.com/mannubaveja007/Syapa" rel="noopener noreferrer"&gt;
        Syapa
      &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;Syapa 🛡️&lt;/h1&gt;
&lt;/div&gt;
&lt;blockquote&gt;
&lt;p&gt;A precision freelance intelligence platform combining a Chrome Manifest V3 meeting recorder with server-side speaker diarization, grounded negotiation coaching, and real-time Conversational AI client sparring.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Architecture Overview&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;                                      +---------------------------------------------+
                                      |            Browser (Chrome MV3)             |
                                      +---------------------------------------------+
                                      |                                             |
                                      |   [Active Tab Audio]   [Microphone Audio]   |
                                      |           |                    |            |
                                      |           +---------+----------+            |
                                      |                     |                       |
                                      |                     v                       |
                                      |       AudioContext Stream Mixer             |
                                      |       (Tab Audio routed to speakers)        |
                                      |                     |                       |
                                      |                     v                       |
                                      |     MediaRecorder (audio/webm;codecs=opus)  |
                                      |                     |                       |
                                      +---------------------|-----------------------+
                                                            |
                                                            | POST /api/meetings/transcribe
                                                            | (x-api-token: syp_...)
                                                            v
+-----------------------------------------------------------------------------------+
|                            Syapa Web App (Next.js 14)                             |
|                               http://localhost:3000                               |
+-----------------------------------------------------------------------------------+
|  POST /api/meetings/transcribe   --&amp;gt; Validates audio, calls ElevenLabs STT        |
|                                      Server-side only (diarize=true, scribe_v2)   |
|                                      Rejects empty/silent audio (HTTP 422)        |
|                                      Saves TranscriptSegments (You / Others)      |
|                                      Triggers asynchronous post-meeting pipeline  |
|  GET  /api/meetings/:id/analysis --&amp;gt; Polls status, executive summary &amp;amp; top&lt;/code&gt;&lt;/pre&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/mannubaveja007/Syapa" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;h3&gt;
  
  
  Architecture Overview
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;                                  +---------------------------------------------+
                                  |            Browser (Chrome MV3)             |
                                  +---------------------------------------------+
                                  |   [Active Tab Audio]   [Microphone Audio]   |
                                  |           \                    /            |
                                  |            AudioContext Stream Mixer        |
                                  |                       |                     |
                                  |                       v                     |
                                  |             MediaRecorder (Opus)            |
                                  +-----------------------|---------------------+
                                                          | POST /api/meetings/transcribe
                                                          v
+---------------------------------------------------------------------------------------+
|                              Syapa Web App (Next.js 14)                               |
+---------------------------------------------------------------------------------------+
| - Speaker Diarization: ElevenLabs Scribe v2 (Server-side key protection)              |
| - Embeddings Engine: nomic-embed-text (Fixed 1024-dim, single batched request)        |
| - Reasoning &amp;amp; Extraction: Gemma 4 / Gemma 2 via Ollama local inference                |
| - Hybrid RAG: 70% pgvector HNSW cosine + 30% GIN tsvector full-text search            |
| - Deterministic Verification: Verbatim string quote matcher                           |
| - Client Sparring: ElevenLabs Conversational AI + Gemma client state simulator        |
+---------------------------------------------------------------------------------------+
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






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

&lt;p&gt;Syapa is structured as a performant TypeScript monorepo (&lt;code&gt;pnpm&lt;/code&gt; workspaces) combining modern web tech with local open-source AI infrastructure:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Open-Source AI Stack at the Core
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Google Gemma (&lt;code&gt;gemma4:12b&lt;/code&gt; / &lt;code&gt;gemma-2-9b-it&lt;/code&gt;) via Ollama&lt;/strong&gt;:
Gemma powers the core intelligence pipeline. Using strict JSON schema generation, Gemma inspects the dialogue, analyzes cross-meeting behavioral patterns against past client calls, flags high-risk freelancer concessions, and drafts assertive counter-proposals.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;nomic-embed-text&lt;/code&gt; Local Embeddings&lt;/strong&gt;:
Transcripts are chunked into 350-word sliding windows and processed in &lt;strong&gt;one batched HTTP request&lt;/strong&gt; using &lt;code&gt;nomic-embed-text&lt;/code&gt; running on &lt;code&gt;localhost:11434&lt;/code&gt;. Vectors are normalized to 1024 dimensions and stored in PostgreSQL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PostgreSQL + &lt;code&gt;pgvector&lt;/code&gt; Hybrid Search&lt;/strong&gt;:
Client briefs and past transcripts are indexed using an &lt;code&gt;hnsw ("embedding" vector_cosine_ops)&lt;/code&gt; index alongside PostgreSQL &lt;code&gt;tsvector&lt;/code&gt; indexes. When practicing negotiations, Syapa pulls relevant context using a &lt;strong&gt;70% vector + 30% lexical full-text hybrid query&lt;/strong&gt; with sub-10ms latency.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Plain Chrome MV3 Extension (&lt;code&gt;apps/extension&lt;/code&gt;)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Loads in &lt;strong&gt;&amp;lt; 5 ms&lt;/strong&gt; with zero build or bundle overhead.&lt;/li&gt;
&lt;li&gt;Uses &lt;code&gt;navigator.mediaDevices.getDisplayMedia&lt;/code&gt; and &lt;code&gt;getUserMedia&lt;/code&gt; with an in-memory &lt;code&gt;AudioContext&lt;/code&gt; mixer. Tab audio is piped to local speakers so you can hear your client without audio feedback loops.&lt;/li&gt;
&lt;li&gt;Empty or silent recordings (&amp;lt;1000 bytes) are rejected automatically at the gateway before hitting any models.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Deterministic Quote Verification (&lt;code&gt;packages/ai/src/quotes.ts&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;LLMs often paraphrase when asked to quote what someone said. For freelance disputes, an ungrounded quote is fatal. Syapa runs a deterministic string-matching verification step in plain code after Gemma completes its analysis. If a quote cannot be verified 100% verbatim against the transcript, it is automatically discarded and logged.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Conversational AI Practice Room (&lt;code&gt;apps/web/src/app/practice&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;Integrated with the &lt;code&gt;@elevenlabs/react&lt;/code&gt; SDK, freelancers can vocally spar against realistic client personas like &lt;strong&gt;Mr. Sharma&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Runs a Class 9–12 coaching center.&lt;/li&gt;
&lt;li&gt;Stated budget: ₹12,000 | Absolute ceiling: ₹15,000.&lt;/li&gt;
&lt;li&gt;Hidden asks: Student fee payment gateway, PDF login portal, and Hindi localization.&lt;/li&gt;
&lt;li&gt;Freelancers practice holding their price ground and setting scope boundaries before the real call.&lt;/li&gt;
&lt;/ul&gt;




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

&lt;p&gt;Why not just hook this up to a proprietary closed API like OpenAI or Anthropic? For freelance intelligence, &lt;strong&gt;open innovation is not just a preference—it is a functional necessity&lt;/strong&gt;:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Client Confidentiality &amp;amp; NDA Compliance&lt;/strong&gt;:
Freelancers routinely discuss proprietary codebases, unreleased product roadmaps, and sensitive budget numbers on client calls. Routing unredacted audio or transcripts to closed cloud models violates standard client NDAs. By running &lt;strong&gt;Gemma&lt;/strong&gt; and &lt;strong&gt;&lt;code&gt;nomic-embed-text&lt;/code&gt;&lt;/strong&gt; locally through Ollama, &lt;strong&gt;client data never leaves the freelancer’s machine&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero Marginal Cost for Heavy Workloads&lt;/strong&gt;:
Transcripts and audio embeddings generate hundreds of thousands of tokens over the course of a multi-week project. Local open-weight models let freelancers run extensive cross-meeting pattern detection, RAG queries, and simulation sessions all day long for &lt;strong&gt;$0.00&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No Vendor Lock-In or Deprecation Surprises&lt;/strong&gt;:
Closed APIs regularly deprecate models, shift system prompt behaviors, or adjust safety guardrails that break structured output schemas. Open-weight models like Gemma give the developer complete control over execution, temperature, sampling, and reproducibility.&lt;/li&gt;
&lt;/ol&gt;




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

&lt;p&gt;Here is what channeling your inner sloth looks like in practice with Syapa:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Traditional Freelancer Routine&lt;/th&gt;
&lt;th&gt;The Syapa "Sloth" Way&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;45 mins&lt;/strong&gt; re-listening to the call &amp;amp; taking manual notes&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;0 mins&lt;/strong&gt;: Syapa automatically diarizes and summarizes the call&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;30 mins&lt;/strong&gt; combing through emails and SOWs to check if a feature was included&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;Instant&lt;/strong&gt;: Gemma highlights scope creep with verified verbatim quotes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;20 mins&lt;/strong&gt; stressing over how to politely say "that will cost extra"&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;1-click&lt;/strong&gt;: Copy the pre-drafted boundary email and change order proposal&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;Unbilled hours lost&lt;/strong&gt; to silent concessions you forgot you made&lt;/td&gt;
&lt;td&gt;
&lt;strong&gt;0 hours&lt;/strong&gt;: Risky promises are flagged immediately with risk analysis&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Total Time Saved:&lt;/strong&gt; ~1.5 to 2 hours per client meeting, plus thousands of dollars saved in prevented scope creep.&lt;/p&gt;




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

&lt;h3&gt;
  
  
  🌟 Best Use of Gemma ($200 Featured Category)
&lt;/h3&gt;

&lt;p&gt;Syapa relies heavily on &lt;strong&gt;Google Gemma&lt;/strong&gt; (&lt;code&gt;gemma4:12b&lt;/code&gt; / &lt;code&gt;gemma-2-9b-it&lt;/code&gt;) as its reasoning backbone:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma Structured Analysis&lt;/strong&gt;: Executes strict schema-enforced extraction of meeting agreements, action items, and risky commitments (&lt;a href="https://github.com/mannubaveja007/Syapa/blob/main/apps/web/src/lib/pipeline.ts" rel="noopener noreferrer"&gt;&lt;code&gt;apps/web/src/lib/pipeline.ts&lt;/code&gt;&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-Meeting Behavioral Pattern Analysis&lt;/strong&gt;: Gemma compares the current transcript against past completed client calls to detect recurring concession patterns.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dynamic Negotiation Simulator&lt;/strong&gt;: Gemma powers the "Bad Client" AI opponent, dynamically managing hidden emotional states, budget thresholds, and concession triggers during sparring sessions (&lt;a href="https://github.com/mannubaveja007/Syapa/blob/main/apps/web/src/app/api/simulator/%5Bid%5D/message/route.ts" rel="noopener noreferrer"&gt;&lt;code&gt;apps/web/src/app/api/simulator/[id]/message/route.ts&lt;/code&gt;&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  🎙️ Best Use of ElevenLabs ($100 Partner Category)
&lt;/h3&gt;

&lt;p&gt;Syapa integrates ElevenLabs across two distinct modalities:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;ElevenLabs Scribe v2 Speech-to-Text&lt;/strong&gt;: Server-side audio transcription with word-level speaker diarization, securely mapping audio into &lt;code&gt;"You"&lt;/code&gt; vs. &lt;code&gt;"Others"&lt;/code&gt; dialogue blocks without leaking API keys to the browser extension.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ElevenLabs Conversational AI SDK (&lt;code&gt;@elevenlabs/react&lt;/code&gt;)&lt;/strong&gt;: Powers low-latency real-time voice sparring with authentic client archetypes in the Practice Room.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Built with passion (and maximum conservation of energy 🦥) for Hacktoberfest 2026.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>ai</category>
      <category>opensource</category>
    </item>
    <item>
      <title>My Uncle’s Khata Notebook Was Failing Him --&gt; So I Built Hisabb</title>
      <dc:creator>mannubaveja007</dc:creator>
      <pubDate>Sun, 04 Oct 2026 20:32:20 +0000</pubDate>
      <link>https://dev.to/mannubaveja007/my-uncles-khata-notebook-was-failing-him-so-i-built-hisabb-525g</link>
      <guid>https://dev.to/mannubaveja007/my-uncles-khata-notebook-was-failing-him-so-i-built-hisabb-525g</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-weekend-2026-10-01"&gt;Hacktoberfest Weekend Challenge: Build for a Friend&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;Hisabb — बोलो. हिसाब हो गया.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I built Hisabb for my uncle, who runs a grocery shop and manages dozens of customers buying on &lt;em&gt;udhaar&lt;/em&gt;—credit—every day.&lt;/p&gt;

&lt;p&gt;He records everything in a physical notebook: customer names, groceries purchased, amounts owed, and payments received. But as transactions accumulate, finding a customer’s history means flipping through pages, calculating balances by hand, and checking whether a payment was already recorded.&lt;/p&gt;

&lt;p&gt;Sometimes entries are unclear, missed, or overwritten. That creates more than extra work—it can cause confusion between my uncle and his customers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hisabb brings that notebook into one simple digital ledger.&lt;/strong&gt; It helps him track each customer’s udhaar, payments, transaction history, and outstanding balance without searching through pages.&lt;/p&gt;

&lt;p&gt;Its voice-first workflow makes adding entries easier: speak a transaction in Hindi or Hinglish, review the extracted details, correct anything the speech recognition misunderstood, and save. Manual entry is available too.&lt;/p&gt;

&lt;p&gt;The goal is simple: &lt;strong&gt;less time managing hisab, fewer mistakes, and more trust between the shopkeeper and the customer.&lt;/strong&gt;&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;Start with our visual introduction:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://frontend-pi-one-84.vercel.app/welcome" rel="noopener noreferrer"&gt;Visit Hisabb’s welcome page&lt;/a&gt; best animation works are here! &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Explore the working ledger:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://frontend-pi-one-84.vercel.app/" rel="noopener noreferrer"&gt;Open Hisabb&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;/welcome&lt;/code&gt; page introduces Hisabb’s story and purpose; the ledger shows how that idea becomes a practical bookkeeping workflow.&lt;/p&gt;

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