<?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: Joy</title>
    <description>The latest articles on DEV Community by Joy (@joyy-dev).</description>
    <link>https://dev.to/joyy-dev</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%2F4158738%2Ffa0cd79b-c72e-45f9-8534-03ccb227b58d.png</url>
      <title>DEV Community: Joy</title>
      <link>https://dev.to/joyy-dev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/joyy-dev"/>
    <language>en</language>
    <item>
      <title>I Built an AI Séance to Bring Abandoned GitHub Repositories Back to Life</title>
      <dc:creator>Joy</dc:creator>
      <pubDate>Sun, 01 Nov 2026 01:00:08 +0000</pubDate>
      <link>https://dev.to/joyy-dev/i-built-an-ai-seance-to-bring-abandoned-github-repositories-back-to-life-4m00</link>
      <guid>https://dev.to/joyy-dev/i-built-an-ai-seance-to-bring-abandoned-github-repositories-back-to-life-4m00</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;br&gt;
​&lt;br&gt;
Imagine opening an unfamiliar repository. The README is incomplete, the architecture is unclear, and the commit history contains messages like &lt;code&gt;WIP&lt;/code&gt; and &lt;code&gt;fix stuff&lt;/code&gt;.&lt;br&gt;
​&lt;br&gt;
The code survived. Understanding it takes an investigation.&lt;br&gt;
​&lt;br&gt;
I have spent too much time trying to connect those fragments when exploring neglected projects. For private code, sending everything to a hosted AI service is not always an acceptable shortcut either.&lt;br&gt;
​&lt;br&gt;
That led me to &lt;strong&gt;RepoSéance&lt;/strong&gt;: a local-first software archaeology workbench built with &lt;strong&gt;Flutter for Windows&lt;/strong&gt;, &lt;strong&gt;Gemma 4 E2B&lt;/strong&gt;, and &lt;strong&gt;Ollama&lt;/strong&gt;.&lt;br&gt;
​&lt;br&gt;
“Back to life” is the metaphor, not an automatic repair feature. RepoSéance helps a developer investigate what remains; it does not rebuild, modify, or run the project it inspects.&lt;br&gt;
​&lt;/p&gt;
&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;​&lt;br&gt;
RepoSéance combines deterministic repository inspection with local model inference. Dart collects and organises the evidence; Gemma interprets selected excerpts.&lt;br&gt;
​&lt;br&gt;
The application can:&lt;br&gt;
​&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;inspect a bounded selection of tracked repository files;&lt;/li&gt;
&lt;li&gt;generate a structured report about apparent purpose, components, and technical characteristics;&lt;/li&gt;
&lt;li&gt;display recent commit records;&lt;/li&gt;
&lt;li&gt;answer questions using evidence selected from the current snapshot; and&lt;/li&gt;
&lt;li&gt;export a Markdown report, optionally including Q&amp;amp;A.
​
The references are inspectable. A developer can open the captured excerpt behind a finding instead of accepting a confident explanation on trust.
​
## The ghost is the context
​
I interpreted &lt;strong&gt;Ghost in the Machine&lt;/strong&gt; as the technical context left behind in a codebase: source files, manifests, comments, documentation, and commit records.
​
Those fragments can help explain a project. They cannot reliably reveal a former maintainer’s private intentions.
​
RepoSéance therefore needs to distinguish an observation from an inference—and admit when the inspected material cannot answer a question.
​
## Demo
​
  &lt;iframe src="https://www.youtube.com/embed/9OWl-o_bTao" width="710" height="399"&gt;
  &lt;/iframe&gt;

​
The walkthrough shows the real Windows application inspecting its own &lt;code&gt;reposeance&lt;/code&gt; repository on &lt;code&gt;main&lt;/code&gt;, opening captured file and commit evidence, trying Q&amp;amp;A, and preparing a Markdown export. It is not a demonstration of reviving an abandoned third-party project.
​
The video is edited for viewing: waiting periods are shortened and disclosed onscreen. The autopsy report in this recording displays &lt;strong&gt;136.6 seconds&lt;/strong&gt;. The Q&amp;amp;A examples include insufficient-evidence responses; I do not present those as successful factual answers.
​
The fixture test below is a &lt;strong&gt;separate evaluation case&lt;/strong&gt;, not the repository shown in that walkthrough.
​
## A question it answered—and why I could check it
​
For a controlled test, I used &lt;code&gt;forgotten_inventory&lt;/code&gt;, a &lt;strong&gt;synthetic Flutter-like repository created for evaluation&lt;/strong&gt;. It is not a real abandoned project or an external user trial.
​
I asked:
​
&amp;gt; What dependencies and packages are declared in pubspec.yaml?
​
In that fixture run, the response returned &lt;code&gt;not_found: false&lt;/code&gt; in approximately &lt;strong&gt;36.1 seconds&lt;/strong&gt; and made three observed claims, each citing &lt;code&gt;E001&lt;/code&gt;:
​&lt;/li&gt;
&lt;li&gt;The project declares &lt;code&gt;flutter&lt;/code&gt; as a dependency.&lt;/li&gt;
&lt;li&gt;It declares &lt;code&gt;flutter_barcode_scanner&lt;/code&gt; with version constraint &lt;code&gt;^2.0.0&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;It declares &lt;code&gt;sqflite&lt;/code&gt; with version constraint &lt;code&gt;^2.3.0&lt;/code&gt;.
​
The relevant part of the captured &lt;code&gt;pubspec.yaml&lt;/code&gt; excerpt was:
​
&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;dependencies&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;flutter&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;sdk&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;flutter&lt;/span&gt;
  &lt;span class="na"&gt;sqflite&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;^2.3.0&lt;/span&gt;
  &lt;span class="na"&gt;flutter_barcode_scanner&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;^2.0.0&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;​&lt;br&gt;
These claims are directly supported by the manifest. They establish &lt;strong&gt;declared dependencies&lt;/strong&gt;, not that every package is installed, imported, or used correctly at runtime.&lt;br&gt;
​&lt;br&gt;
That is a modest result, but an inspectable one. A deeper claim about persistence would require implementation evidence—not just the presence of &lt;code&gt;sqflite&lt;/code&gt; in a manifest.&lt;br&gt;
​&lt;br&gt;
I also tested the question:&lt;br&gt;
​&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Why SQLite instead of PostgreSQL?&lt;br&gt;
​&lt;br&gt;
In that separate fixture case, Gemma returned &lt;code&gt;not_found: true&lt;/code&gt;, an empty claims list, and an explanation that the supplied evidence did not document the decision. That refusal came from the model; passing application schema checks is a separate step.&lt;br&gt;
​&lt;br&gt;
A useful factual answer and a justified refusal are different outcomes. I want the application to handle both without pretending they are interchangeable.&lt;br&gt;
​&lt;/p&gt;
&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;​&lt;br&gt;
&lt;/p&gt;


&lt;/blockquote&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Local Git repository
        |
        v
Bounded file scanner + read-only Git inspection
        |
        v
Captured evidence snapshot
        |
        +--&amp;gt; Lexical retrieval for Q&amp;amp;A
        |
        v
Selected evidence + structured prompt
        |
        v
Local Ollama HTTP API --&amp;gt; Gemma 4 E2B
        |
        v
Dart response validation + request-level evidence checks
        |
        v
Report / answer / captured evidence preview
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;​&lt;br&gt;
&lt;strong&gt;Inspection is not execution.&lt;/strong&gt; Git is invoked with argument lists and shell execution disabled. RepoSéance does not run the target repository’s builds, tests, or package scripts, and the model does not receive filesystem or shell tools.&lt;br&gt;
​&lt;br&gt;
&lt;strong&gt;The snapshot is partial.&lt;/strong&gt; The scanner bounds candidate enumeration, selected files, traversal depth, and extracted text. In the recorded run, the selected-file limit was 50 and the depth limit was four; the report disclosed skipped files and omitted candidates.&lt;br&gt;
​&lt;br&gt;
&lt;strong&gt;References belong to the application.&lt;/strong&gt; File excerpts and commit records receive evidence IDs. Captured file content is fingerprinted with SHA-256, and returned IDs are checked against the evidence supplied for that request. The UI resolves references through those records rather than trusting model-generated paths.&lt;br&gt;
​&lt;br&gt;
&lt;strong&gt;Q&amp;amp;A uses lightweight retrieval.&lt;/strong&gt; A lexical matcher selects relevant snippets before inference. No vector database is required, but literal matching can miss a concept expressed through different terminology—for example, a question about a “database” when the useful manifest names &lt;code&gt;sqflite&lt;/code&gt;.&lt;br&gt;
​&lt;/p&gt;
&lt;h2&gt;
  
  
  The hard part was not making the model sound certain
&lt;/h2&gt;

&lt;p&gt;​&lt;br&gt;
The difficult part was getting a compact local model to produce bounded structured output without inventing references or exhausting the output budget.&lt;br&gt;
​&lt;br&gt;
I used structured response contracts, bounded output settings, &lt;code&gt;think: false&lt;/code&gt;, and application-side validation. But these controls solve different problems:&lt;br&gt;
​&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Output settings constrain generation; they do not guarantee correctness or determinism.&lt;/li&gt;
&lt;li&gt;Schema checks enforce the expected response shape.&lt;/li&gt;
&lt;li&gt;The request-level allowlist rejects references to evidence not supplied for that question.&lt;/li&gt;
&lt;li&gt;Human inspection is still needed to assess whether an excerpt supports a conclusion.
​
&lt;strong&gt;A valid citation is provenance, not semantic proof.&lt;/strong&gt; SHA-256 does not make an interpretation true, and rejecting an unknown ID does not eliminate all hallucinations.
​
Repository text is also untrusted input. Prompt delimiters and instructions help distinguish evidence from commands, but they do not make prompt injection impossible. The model’s lack of execution tools is an important separate boundary.
​
## How I checked the release
​
My recorded local release checks were:
​
| Check | Recorded result |
| --- | --- |
| &lt;code&gt;flutter analyze&lt;/code&gt; | Exit 0; no issues reported |
| Test suite | 146 passing tests, with no reported failures or skips |
| &lt;code&gt;flutter build windows --release&lt;/code&gt; | Exit 0; Windows release runner built |
| Live local-model checks | Structured autopsy generation and Q&amp;amp;A through local Ollama |
| Invalid-reference probe | Unsupplied &lt;code&gt;E999&lt;/code&gt; rejected in the adversarial check |
| Export checks | Automated checks for formatting, path sanitisation, and credential masking |
​
These are my local results, not an independent security audit or a guarantee of correct answers on arbitrary repositories. The three manifest claims above are a small, directly inspectable example—not a general model-accuracy score.
​
## Why open-weight AI matters here
​
Gemma is not an optional chatbot attached to a conventional report. Its interpretation of the selected evidence is part of the central analysis workflow.
​
Running it through local Ollama matters because:
​&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repository excerpts can stay with a local inference runtime.&lt;/strong&gt; The analysis path uses &lt;code&gt;127.0.0.1:11434&lt;/code&gt; instead of requiring a hosted model API.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;There is no hosted per-token inference bill.&lt;/strong&gt; Hardware, storage, electricity, and setup still have costs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The runtime is under the developer’s control.&lt;/strong&gt; Compatible models and settings can be changed, although alternatives need their own quality and compatibility checks.
​
The trade-off is visible: CPU inference is not instant. The recorded self-analysis took 136.6 seconds; the separate fixture dependency question took about 36.1 seconds. Those are different requests, not a controlled comparison or a universal performance benchmark.
​
The development machine was a Windows 11 laptop with 16 GB RAM, using CPU inference. I have not tested analysis with the internet connection disabled. The application’s loopback-only design should not be presented as a completed offline test or proof about every process on the machine.
​
## Limits and next steps
​
This is an early Windows release, not a replacement for a maintainer’s investigation.
​&lt;/li&gt;
&lt;li&gt;Untracked, excluded, oversized, or otherwise uninspected files may change the interpretation.&lt;/li&gt;
&lt;li&gt;Filename-based secret exclusions and export masking are best-effort protections, not comprehensive credential detection.&lt;/li&gt;
&lt;li&gt;Lexical retrieval may omit the most useful evidence.&lt;/li&gt;
&lt;li&gt;A compact model can produce an incorrect inference even with a real citation.&lt;/li&gt;
&lt;li&gt;Commit subjects record what was written in version control; they do not establish the exact change or its motivation without further evidence.
​
My next priorities are better evidence selection, stronger request-isolation regression coverage, and syntax-aware indexing. Historical diff analysis and other desktop platforms are future work, not current release capabilities.
​
## Code and Windows release
​&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source:&lt;/strong&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/Joyy-dev" rel="noopener noreferrer"&gt;
        Joyy-dev
      &lt;/a&gt; / &lt;a href="https://github.com/Joyy-dev/reposeance" rel="noopener noreferrer"&gt;
        reposeance
      &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;RepoSéance 👻&lt;/h1&gt;
&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Summon the ghost in the machine.&lt;/strong&gt;&lt;br&gt;
A local-first, privacy-respecting AI software archaeology workbench that reconstructs the purpose, architecture, and development history of unfamiliar or abandoned Git repositories — powered by Google's Gemma model running 100% locally on your machine with verifiable, source-grounded evidence citations.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Built for &lt;strong&gt;DEV Hacktoberfest 2026 Week 4: "Ghost in the Machine"&lt;/strong&gt;.&lt;/p&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;⚡ Highlights &amp;amp; Key Features&lt;/h2&gt;
&lt;/div&gt;

&lt;ul&gt;
&lt;li&gt;🔒 &lt;strong&gt;100% Local &amp;amp; Offline&lt;/strong&gt;: Operates entirely on your machine via direct loopback HTTP (&lt;code&gt;127.0.0.1:11434&lt;/code&gt;) to local Ollama. Zero outbound telemetry, zero cloud API keys, zero cloud egress.&lt;/li&gt;
&lt;li&gt;🛡️ &lt;strong&gt;Zero-Execution Sandbox&lt;/strong&gt;: Inspects repository text and Git metadata deterministically. &lt;strong&gt;Never&lt;/strong&gt; executes arbitrary build scripts, test runners, npm scripts, or hooks found inside untrusted target repositories.&lt;/li&gt;
&lt;li&gt;📜 &lt;strong&gt;Evidence-Grounded Citations&lt;/strong&gt;: Every claim in the generated autopsy and Q&amp;amp;A references concrete evidence items (e.g. &lt;code&gt;[E001]&lt;/code&gt;). Claims cannot hallucinate uninspected files or confabulate non-existent commits.&lt;/li&gt;
&lt;li&gt;🧠…&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/Joyy-dev/reposeance" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows package:&lt;/strong&gt; &lt;a href="https://github.com/Joyy-dev/reposeance/releases/tag/v1.0.0" rel="noopener noreferrer"&gt;RepoSéance v1.0.0&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Initial project commit:&lt;/strong&gt; &lt;a href="https://github.com/Joyy-dev/reposeance/commit/be72cfa0d8294439b812b7197d76c332c6c52287" rel="noopener noreferrer"&gt;&lt;code&gt;be72cfa&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Implementation freeze:&lt;/strong&gt; &lt;a href="https://github.com/Joyy-dev/reposeance/commit/042ccfae938a20966f7f321d9dc2f1d3963d0aee" rel="noopener noreferrer"&gt;&lt;code&gt;042ccfa&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Published release tag target:&lt;/strong&gt; &lt;a href="https://github.com/Joyy-dev/reposeance/commit/b52e8671ffb150a4f78f56980abcc02732379845" rel="noopener noreferrer"&gt;&lt;code&gt;b52e867&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Application license:&lt;/strong&gt; &lt;a href="https://github.com/Joyy-dev/reposeance/blob/main/LICENSE" rel="noopener noreferrer"&gt;MIT&lt;/a&gt;
​
The later release commit adds the README and MIT license; it does not change the application implementation frozen at &lt;code&gt;042ccfa&lt;/code&gt;. Ollama and the local model remain external prerequisites; see the release instructions before running the Windows package.
​
## Prize category 
​
I am entering &lt;strong&gt;Best Use of Gemma&lt;/strong&gt;. Gemma performs the local interpretation behind the report and Q&amp;amp;A, rather than serving as an incidental feature.
​
---
​
I do not expect an AI model to recover every lost decision. I want it to help a developer examine what remains, show the evidence behind a useful answer, and stop when that evidence runs out.
​
&lt;strong&gt;The ghost is not the developer. It is the context they left behind.&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>gemma</category>
      <category>flutter</category>
    </item>
    <item>
      <title>I Got Tired of Fixing the Same Flutter Error Twice — So I Built StackSoothe</title>
      <dc:creator>Joy</dc:creator>
      <pubDate>Mon, 26 Oct 2026 05:09:50 +0000</pubDate>
      <link>https://dev.to/joyy-dev/i-got-tired-of-fixing-the-same-flutter-error-twice-so-i-built-stacksoothe-9mf</link>
      <guid>https://dev.to/joyy-dev/i-got-tired-of-fixing-the-same-flutter-error-twice-so-i-built-stacksoothe-9mf</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: Slow and Steady&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;




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

&lt;p&gt;If you develop with Flutter, you may know the frustration of spending half an hour debugging an error, fixing it, and then meeting the same problem again a few months later.&lt;/p&gt;

&lt;p&gt;Maybe it is a &lt;code&gt;use_build_context_synchronously&lt;/code&gt; warning, a &lt;code&gt;LateInitializationError&lt;/code&gt;, or a &lt;code&gt;RenderFlex&lt;/code&gt; overflow. The routine can feel familiar: copy the stack trace, search for an explanation, share a code snippet with an AI assistant, sort through suggestions, and work out the fix again.&lt;/p&gt;

&lt;p&gt;I built &lt;strong&gt;StackSoothe&lt;/strong&gt;, a local-first debugging assistant for Flutter and Dart developers. It uses a local open-weight model to diagnose an error the first time. Once I have checked the advice and explicitly marked the fix as verified, StackSoothe can remember that solution and retrieve it when the same error and context recur.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;┌─────────────────────────────────┐
│     StackSoothe Desktop App     │  (Flutter / Dart Windows Runner)
│   - Fix Notebook (%LOCALAPPDATA%)│
│   - Deterministic SHA-256 Keys  │
└────────────────┬────────────────┘
                 │ HTTP (127.0.0.1:11435) with Ephemeral Bearer Token
                 ▼
┌─────────────────────────────────┐
│   Local Node/TypeScript Service │  (Single-concurrency loopback shim)
│   - Exact Host Header Validation │
│   - Strict Zod Schema Validation │
└────────────────┬────────────────┘
                 │ HTTP (127.0.0.1:11434)
                 ▼
┌─────────────────────────────────┐
│          Local Ollama           │  (qwen3:1.7b, 100% Local Inference)
└─────────────────────────────────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The idea is simple: do the difficult diagnosis once, apply human judgment, and avoid repeating the same work unnecessarily.&lt;/p&gt;
&lt;h2&gt;
  
  
  The “Slow and Steady” payoff
&lt;/h2&gt;

&lt;p&gt;StackSoothe follows five steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Diagnose locally.&lt;/strong&gt; Paste a runtime error and relevant source context. StackSoothe sends them to &lt;code&gt;qwen3:1.7b&lt;/code&gt;, running locally through Ollama, and asks for a structured diagnosis with a likely cause, suggested steps, severity, and confidence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a human in the loop.&lt;/strong&gt; Every new diagnosis begins as &lt;code&gt;UNVERIFIED&lt;/code&gt;. The model cannot mark its own answer as a confirmed fix; the developer must do that.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fingerprint the problem.&lt;/strong&gt; When a fix is verified, StackSoothe computes a SHA-256 fingerprint from the canonicalized error, source context, and project/runtime details.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recall an exact repeat.&lt;/strong&gt; When that fingerprint matches a verified record, StackSoothe retrieves the saved solution without another model call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Be cautious about changed context.&lt;/strong&gt; If the error appears in a different project, modified source context, or a changed runtime environment, StackSoothe warns that the old fix may be stale instead of silently reusing it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In the current synthetic benchmark, an exact repeat lookup took &lt;strong&gt;1.98 milliseconds&lt;/strong&gt; and avoided another model call. That is a measured lookup result, not a claim that every debugging task will be solved in milliseconds: the initial model diagnosis is much slower.&lt;/p&gt;
&lt;h2&gt;
  
  
  Demo and source code
&lt;/h2&gt;

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

&lt;p&gt;The 2-minute walkthrough demonstrates:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;First-occurrence diagnosis via local &lt;code&gt;qwen3:1.7b&lt;/code&gt; (initial state: &lt;code&gt;UNVERIFIED&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Explicit developer verification of the proposed fix.&lt;/li&gt;
&lt;li&gt;Retrieval of a verified solution on an exact recurrence, without another model call.&lt;/li&gt;
&lt;li&gt;A warning when the same error appears with modified source context.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source repository:&lt;/strong&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/joyy-dev-organization" rel="noopener noreferrer"&gt;
        joyy-dev-organization
      &lt;/a&gt; / &lt;a href="https://github.com/joyy-dev-organization/stackSoothe" rel="noopener noreferrer"&gt;
        stackSoothe
      &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;StackSoothe — Local Flutter &amp;amp; Dart Debugging Assistant&lt;/h1&gt;
&lt;/div&gt;

&lt;p&gt;&lt;a href="https://opensource.org/licenses/MIT" rel="nofollow noopener noreferrer"&gt;&lt;img src="https://camo.githubusercontent.com/08cef40a9105b6526ca22088bc514fbfdbc9aac1ddbf8d4e6c750e3a88a44dca/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4c6963656e73652d4d49542d626c75652e737667" alt="License: MIT"&gt;&lt;/a&gt;
&lt;a href="https://github.com/joyy-dev-organization/stackSoothe/releases/tag/v0.1.0-challenge" rel="noopener noreferrer"&gt;&lt;img src="https://camo.githubusercontent.com/625fdfe6885764c8e1b73c98378578fdd43d9386322b9fcde44547228b51c871/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f52656c656173652d76302e312e302d2d6368616c6c656e67652d677265656e2e737667" alt="Release: v0.1.0-challenge"&gt;&lt;/a&gt;
&lt;a href="https://github.com/joyy-dev-organization/stackSoothe" rel="noopener noreferrer"&gt;&lt;img src="https://camo.githubusercontent.com/e0e54d6dc252f1a59043257c2a8e1007b0be6bd0ae5b1e25b638f6162a02d7db/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f506c6174666f726d2d57696e646f77732532307836342d6c69676874677265792e737667" alt="Platform: Windows x64"&gt;&lt;/a&gt;
&lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19" rel="nofollow"&gt;&lt;img src="https://camo.githubusercontent.com/46ec50202b472d094dba2fe6aa00ef52964a86123e29fcb6b55161cc7beee0d4/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4861636b746f62657266657374253230323032362d536c6f772532302532362532305374656164792d6f72616e67652e737667" alt="Theme: Slow and Steady"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;StackSoothe is an open-source, local-first debugging assistant for Flutter and Dart developers. Built around the Hacktoberfest 2026 &lt;strong&gt;"Slow and Steady"&lt;/strong&gt; theme, it eliminates redundant manual troubleshooting: paste confusing runtime logs once, receive an honest structured diagnosis from a local open-weight model, verify the fix locally, and recall verified solutions upon future recurrences with &lt;strong&gt;zero additional model inference&lt;/strong&gt; (under 2 ms).&lt;/p&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;The "Slow and Steady" Payoff&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;Flutter developers repeatedly encounter identical runtime failures (e.g. &lt;code&gt;BuildContext&lt;/code&gt; used across async gaps, null-check operators on uninitialized fields, &lt;code&gt;RenderFlex&lt;/code&gt; layout overflows). Re-explaining the same error to a chat interface or searching old forum threads is tedious, unwanted work.&lt;/p&gt;

&lt;p&gt;StackSoothe automates that repetition:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;First Occurrence&lt;/strong&gt;: Diagnosed locally by &lt;code&gt;qwen3:1.7b&lt;/code&gt; running on Ollama. The report details likely cause, actionable fix steps, severity, and confidence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User Verification&lt;/strong&gt;: Diagnosis starts &lt;code&gt;UNVERIFIED&lt;/code&gt;. Only an explicit human action transitions it…&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/joyy-dev-organization/stackSoothe" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows standalone release:&lt;/strong&gt; &lt;a href="https://github.com/joyy-dev-organization/stackSoothe/releases/tag/v0.1.0-challenge" rel="noopener noreferrer"&gt;v0.1.0-challenge Package (45.8 MB)&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;License:&lt;/strong&gt; MIT License&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Windows preview is an unsigned release candidate. It requires Ollama and the &lt;code&gt;qwen3:1.7b&lt;/code&gt; model; follow the repository quick-start instructions before running it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I built it
&lt;/h2&gt;

&lt;p&gt;StackSoothe has three main pieces:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Flutter desktop app:&lt;/strong&gt; the Windows interface and local Fix Notebook.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Node.js/TypeScript service:&lt;/strong&gt; a small local service that validates requests and responses before and after model inference.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ollama with &lt;code&gt;qwen3:1.7b&lt;/code&gt;:&lt;/strong&gt; local open-weight inference for the first diagnosis.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The service binds to &lt;code&gt;127.0.0.1:11435&lt;/code&gt; and communicates with Ollama at &lt;code&gt;127.0.0.1:11434&lt;/code&gt;. It uses an ephemeral bearer token, validates host and origin information, and checks model output against a strict Zod schema. The private desktop flow is designed to keep source snippets, stack traces, and stored fixes on the developer's machine. Offline diagnosis works after Ollama and the model have been installed.&lt;/p&gt;

&lt;p&gt;There is one important privacy trade-off: the Fix Notebook is stored as local JSON and is &lt;strong&gt;not encrypted at rest&lt;/strong&gt;. It relies on the operating system's file permissions. I wanted that limitation to be explicit rather than describing local storage as automatically secure in every respect.&lt;/p&gt;

&lt;h3&gt;
  
  
  A bug I found while instrumenting diagnosis
&lt;/h3&gt;

&lt;p&gt;During tracing work, I found an edge case where a timed-out model request could be reported as if the user had cancelled it. The schema-validation failure path could also discard useful token and timing metrics. I updated the abort-signal handling to distinguish timeouts from user cancellation and preserved the timing metadata when schema validation fails. Regression tests were added for those cases.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I evaluated it
&lt;/h2&gt;

&lt;p&gt;The repository's current evaluation documentation describes &lt;strong&gt;12 predeclared synthetic cases&lt;/strong&gt;: eight diagnostic cases and four state/reuse cases. The recorded results include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Raw schema validity: &lt;strong&gt;8/8&lt;/strong&gt; diagnostic cases.&lt;/li&gt;
&lt;li&gt;Schema validity after at most one repair retry: &lt;strong&gt;8/8&lt;/strong&gt; diagnostic cases.&lt;/li&gt;
&lt;li&gt;Semantic checks for groundedness, uncertainty handling, and prompt-injection safety: &lt;strong&gt;8/8&lt;/strong&gt; diagnostic cases.&lt;/li&gt;
&lt;li&gt;State and reuse checks: &lt;strong&gt;4/4&lt;/strong&gt; cases.&lt;/li&gt;
&lt;li&gt;Exact repeat recall: &lt;strong&gt;1.98 ms&lt;/strong&gt;, with no new model call for the measured exact matches.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On the recorded Windows 11 test machine with 16 GB RAM and shared Intel UHD graphics, cold-start latency was &lt;strong&gt;50.8 seconds&lt;/strong&gt;. Warm inference had a reported median of &lt;strong&gt;74.1 seconds&lt;/strong&gt;, with a range of &lt;strong&gt;46.8–100.1 seconds&lt;/strong&gt;. These timings depend on the machine and model state; local inference is not necessarily faster than a hosted model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No external human developer trial has been conducted.&lt;/strong&gt; These results are limited to synthetic cases and machine measurements. They demonstrate the behavior tested so far, not proven improvements in developer productivity across a wider population.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why open innovation matters
&lt;/h2&gt;

&lt;p&gt;The local model is not an optional chatbot bolted onto a conventional debugger. It performs the initial diagnosis that starts the workflow.&lt;/p&gt;

&lt;p&gt;Open-weight models and local inference matter to StackSoothe for three reasons:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Privacy and control:&lt;/strong&gt; source code and stack traces from private projects can be sensitive. After initial model setup, the diagnosis flow can run locally without sending those inputs to a hosted AI provider.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model choice:&lt;/strong&gt; developers can inspect the setup and replace the model or adjust the prompt and output schema instead of depending on a remote provider's API behavior.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Less repeated computation:&lt;/strong&gt; once a developer verifies a fix, an exact recurrence can use the local notebook rather than making another inference request. This avoids redundant model calls, although the application still uses the computer's resources and local inference may be slow.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The trade-off is real: on my recorded test machine, the first diagnosis took tens of seconds. The payoff is not that every answer is instant; it is that a verified solution can be recalled almost instantly when the same problem returns.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sentry Agent Tracing
&lt;/h2&gt;

&lt;p&gt;I am entering the &lt;strong&gt;Best Use of Sentry Agent Tracing&lt;/strong&gt; partner category. &lt;/p&gt;

&lt;p&gt;StackSoothe implements manual GenAI span tracing conforming to &lt;a href="https://docs.sentry.io/platforms/javascript/guides/node/tracing/instrumentation/automatic-instrumentation/#ai-models" rel="noopener noreferrer"&gt;OpenTelemetry and Sentry AI Agent guidelines&lt;/a&gt; via a dedicated diagnostic harness (&lt;code&gt;STACKSOOTHE_SENTRY_ENABLED=1&lt;/code&gt;). The diagnostic harness includes automated tests that inspect serialized tracing payloads. These tests verify that source snippets, stack traces, model completions, and authorization tokens are not attached to the tested spans or tags.&lt;/p&gt;

&lt;p&gt;The regular desktop workflow remains exporter-free by default. These tests validate the specific tracing paths covered by the harness; they are not a blanket guarantee about every possible data flow.&lt;/p&gt;

&lt;h3&gt;
  
  
  Trace &amp;amp; Span Structure
&lt;/h3&gt;

&lt;p&gt;Each model diagnosis is wrapped in a root GenAI chat span:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Operation (&lt;code&gt;op&lt;/code&gt;)&lt;/strong&gt;: &lt;code&gt;gen_ai.chat&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Span Name&lt;/strong&gt;: &lt;code&gt;chat qwen3:1.7b&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Span Attributes&lt;/strong&gt;:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&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;"gen_ai.operation.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;"chat"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"gen_ai.provider.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;"ollama"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"gen_ai.request.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;"qwen3:1.7b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"gen_ai.response.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;"qwen3:1.7b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"gen_ai.usage.input_tokens"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;402&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"gen_ai.usage.output_tokens"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;445&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"gen_ai.duration_ms"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;50800&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"ollama.timing.load_ms"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;3450&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"ollama.timing.prompt_eval_ms"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;4728&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"ollama.timing.eval_ms"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;42576&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;h3&gt;
  
  
  Waterfall Visualization
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Transaction] stacksoothe-diagnosis (50.8s)
 └─ [Span] gen_ai.chat: chat qwen3:1.7b (50.8s) [status: ok]
     ├─ Model Weights Load:   [████] 3.45s
     ├─ Prompt Evaluation:    [██████] 4.73s
     └─ Token Generation:     [████████████████████████████████████] 42.58s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Strict Privacy Allowlist
&lt;/h3&gt;

&lt;p&gt;To guarantee that private source code and stack traces are never exfiltrated, an automated test (&lt;a href="https://github.com/joyy-dev-organization/stackSoothe/blob/main/service/test/sentry-spike.test.ts" rel="noopener noreferrer"&gt;&lt;code&gt;sentry-spike.test.ts&lt;/code&gt;&lt;/a&gt;) strictly asserts that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;errorLog&lt;/code&gt;, &lt;code&gt;sourceCode&lt;/code&gt;, model completions, and authorization tokens are &lt;strong&gt;never attached&lt;/strong&gt; to span attributes or tags.&lt;/li&gt;
&lt;li&gt;Span tags are strictly restricted to low-cardinality enums and numeric timings (&lt;code&gt;TIMEOUT&lt;/code&gt;, &lt;code&gt;MODEL_UNAVAILABLE&lt;/code&gt;, &lt;code&gt;SCHEMA_VALIDATION_FAILED&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Verifiable Artifacts &amp;amp; Test Evidence
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Trace Manifest&lt;/strong&gt;: Full JSON dump of 4 diagnostic paths (Success, Network Unavailable, Schema Failure, Timeout) in &lt;a href="https://github.com/joyy-dev-organization/stackSoothe/blob/main/service/fixtures/m3-evidence-manifest.json" rel="noopener noreferrer"&gt;&lt;code&gt;m3-evidence-manifest.json&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Defect Reproducer&lt;/strong&gt;: Unit test verifying error span tagging and timing retention during schema failures in &lt;a href="https://github.com/joyy-dev-organization/stackSoothe/blob/main/service/test/defect-reproducer.test.ts" rel="noopener noreferrer"&gt;&lt;code&gt;defect-reproducer.test.ts&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Limitations and next steps
&lt;/h2&gt;

&lt;p&gt;StackSoothe is a prototype, not a replacement for developer judgment. Local model output can be wrong, the initial diagnosis can be slow, and the Fix Notebook is not encrypted at rest. The evaluation is synthetic, and external user testing remains a next step.&lt;/p&gt;

&lt;p&gt;The goal is modest: help Flutter developers stop spending time solving the &lt;em&gt;exact same&lt;/em&gt; problem from scratch. Diagnose once, verify carefully, and make the next occurrence less work.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>flutter</category>
      <category>ai</category>
    </item>
    <item>
      <title>SoloDesk: Local AI Workspace for Freelancer Scope Protection with Mastra &amp; Flutter</title>
      <dc:creator>Joy</dc:creator>
      <pubDate>Sun, 18 Oct 2026 22:10:05 +0000</pubDate>
      <link>https://dev.to/joyy-dev/solodesk-local-ai-workspace-for-freelancer-scope-protection-with-mastra-flutter-93d</link>
      <guid>https://dev.to/joyy-dev/solodesk-local-ai-workspace-for-freelancer-scope-protection-with-mastra-flutter-93d</guid>
      <description>&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;Independent freelancers lose thousands of dollars every year to two expensive, recurring communication traps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Unstated Brief Assumptions&lt;/strong&gt;: Accepting client briefs that conceal unstated deliverables, missing dielines, undefined deadlines, and zero commercial clarity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unbudgeted Scope Creep&lt;/strong&gt;: Receiving "just one quick little change" halfway through a project that quietly adds days of uncompensated labor.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most freelancers cannot use cloud-hosted AI tools (like ChatGPT or Claude) to analyze their client contracts because doing so violates client Non-Disclosure Agreements (NDAs), exposes unreleased product IP, and leaks confidential commercial terms to third-party model providers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SoloDesk&lt;/strong&gt; is a private, local Windows desktop productivity workspace built for solo freelancers. It provides deterministic, AI-assisted boundary protection directly on consumer laptop hardware without sending a single byte of client data to the cloud:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;BriefCheck&lt;/strong&gt;: Ingests unstructured client inquiries, extracts verified factual requirements, isolates unstated assumptions, flags critical omissions, and generates clarifying questions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ScopeShield&lt;/strong&gt;: Semantically compares incoming client change requests against an approved, SQLite-locked scope version, producing itemized classifications (&lt;code&gt;INCLUDED&lt;/code&gt;, &lt;code&gt;POTENTIALLY_OUTSIDE&lt;/code&gt;, &lt;code&gt;NEEDS_CLARIFICATION&lt;/code&gt;) with cited contract excerpts and editable, courteous draft replies.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PolitePay&lt;/strong&gt;: Multi-currency invoice tracking (USD, EUR, GBP, NGN, KES, CAD, AUD) with integer minor-unit math and calendar-date rules; generates polite, fact-grounded payment reminder drafts across gentle, polite, and firm tones without inventing unauthorized late fees.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LeadLoop&lt;/strong&gt;: Inbound lead qualification pipeline with currency-segregated unweighted totals and local follow-up drafting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repeat Work&lt;/strong&gt;: Retainer tracking and model-assisted renewal proposal drafting preventing fabricated acceptance claims.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SoloDesk Boundary Policy&lt;/strong&gt;: Explicit system invariant stating that SoloDesk never processes payments, sends messages, or provides legal advice. All outputs are strictly advisory drafts for human review.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Proposed Value &amp;amp; Willingness to Pay
&lt;/h3&gt;

&lt;p&gt;SoloDesk addresses an immediate financial loss: absorbing a single out-of-scope feature or unbudgeted revision round costs a freelancer between $250 and $1,500 in unbilled time. Based on these economics, our commercial hypothesis is a &lt;strong&gt;$19/month or $149 lifetime local desktop license&lt;/strong&gt;. &lt;em&gt;(Note: This is an empirical pricing hypothesis based on freelancer pain points; per our anti-fabrication guidelines, no live commercial revenue has been collected prior to challenge release).&lt;/em&gt;&lt;/p&gt;




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

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Video Walkthrough&lt;/strong&gt;:   &lt;iframe src="https://www.youtube.com/embed/SiAsgrCJvAU" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;br&gt;
The walkthrough shows the Windows interface, client/project creation, BriefCheck running against the local model, ScopeShield comparing a request, and invoice/service-plan interactions. The figures and records shown are demonstration data, not evidence of business revenue.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Windows Desktop Release&lt;/strong&gt;: &lt;a href="https://github.com/joyy-dev-organization/solodesk/releases/tag/v0.1.0-challenge" rel="noopener noreferrer"&gt;Download SoloDesk v0.1.0-challenge (Zip)&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Prerequisites &amp;amp; Quick Start
&lt;/h3&gt;

&lt;p&gt;SoloDesk runs locally on 64-bit Windows 10/11:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Ollama&lt;/strong&gt;: Install &lt;a href="https://ollama.com" rel="noopener noreferrer"&gt;Ollama for Windows&lt;/a&gt; and pull the open-weight model:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="w"&gt;   &lt;/span&gt;&lt;span class="n"&gt;ollama&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;pull&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;qwen3:1.7b&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Download &amp;amp; Extract&lt;/strong&gt;: Download &lt;code&gt;solodesk-v0.1.0-windows-x64.zip&lt;/code&gt; from our GitHub releases.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Launch&lt;/strong&gt;:
Run &lt;code&gt;launch-solodesk.bat&lt;/code&gt; (or start the Mastra service in &lt;code&gt;service/&lt;/code&gt; and run &lt;code&gt;solodesk.exe&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Offline Validation&lt;/strong&gt;: Disconnect Wi-Fi and execute BriefCheck or ScopeShield—all inference runs 100% locally.&lt;/li&gt;
&lt;/ol&gt;


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

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub Repository&lt;/strong&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/joyy-dev-organization" rel="noopener noreferrer"&gt;
        joyy-dev-organization
      &lt;/a&gt; / &lt;a href="https://github.com/joyy-dev-organization/solodesk" rel="noopener noreferrer"&gt;
        solodesk
      &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;SoloDesk&lt;/h1&gt;
&lt;/div&gt;

&lt;p&gt;SoloDesk is a private, local desktop productivity workspace designed for independent freelancers. It assists with brief analysis (&lt;strong&gt;BriefCheck&lt;/strong&gt;), scope verification (&lt;strong&gt;ScopeShield&lt;/strong&gt;), polite payment tracking (&lt;strong&gt;PolitePay&lt;/strong&gt;), client pipeline tracking (&lt;strong&gt;LeadLoop&lt;/strong&gt;), and follow-up proposal drafting (&lt;strong&gt;Repeat Work&lt;/strong&gt;) using local open-weight models (&lt;code&gt;qwen3:1.7b&lt;/code&gt;) and inspectable Mastra agent workflows, without sending client data to third-party cloud inference services.&lt;/p&gt;

&lt;div class="markdown-alert markdown-alert-note"&gt;
&lt;p class="markdown-alert-title"&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Release Status&lt;/strong&gt;: &lt;code&gt;v0.1.0-challenge&lt;/code&gt; · &lt;strong&gt;Feature Freeze Active&lt;/strong&gt; (as of Sunday 2026-10-18T12:00 Africa/Lagos). All completed features and roadmap boundaries are locked for challenge submission.&lt;/p&gt;
&lt;/div&gt;




&lt;div class="markdown-heading"&gt;
&lt;h2 class="heading-element"&gt;Submission Metadata &amp;amp; Challenge Traceability&lt;/h2&gt;
&lt;/div&gt;

&lt;p&gt;&lt;/p&gt;&lt;div class="table-wrapper-paragraph"&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;table&gt;

&lt;thead&gt;

&lt;tr&gt;

&lt;th&gt;Attribute&lt;/th&gt;

&lt;th&gt;Challenge Value&lt;/th&gt;

&lt;/tr&gt;

&lt;/thead&gt;

&lt;tbody&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Challenge&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;Hacktoberfest 2026 / DEV Challenge (Week 2: Best Use of Mastra)&lt;/td&gt;

&lt;/tr&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Prize Category&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;Best Use of Mastra (Orchestrating agents over local open models)&lt;/td&gt;

&lt;/tr&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Release Tag&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;&lt;a href="https://github.com/joyy-dev-organization/solodesk/releases/tag/v0.1.0-challenge" rel="noopener noreferrer"&gt;&lt;code&gt;v0.1.0-challenge&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;

&lt;/tr&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Baseline Submission Commit&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;
&lt;br&gt;
&lt;code&gt;dd47789&lt;/code&gt; (and M9 release packaging commits)&lt;/td&gt;

&lt;/tr&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Repository URL&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;
&lt;a href="https://github.com/joyy-dev-organization/solodesk" rel="noopener noreferrer"&gt;&lt;/a&gt;&lt;a href="https://github.com/joyy-dev-organization/solodesk" rel="noopener noreferrer"&gt;https://github.com/joyy-dev-organization/solodesk&lt;/a&gt;
&lt;/td&gt;

&lt;/tr&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Public DEV Post URL&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;&lt;em&gt;[Pending Publication]&lt;/em&gt;&lt;/td&gt;

&lt;/tr&gt;

&lt;tr&gt;

&lt;td&gt;&lt;strong&gt;Video Walkthrough Demo&lt;/strong&gt;&lt;/td&gt;

&lt;td&gt;&lt;em&gt;[Pending Upload]&lt;/em&gt;&lt;/td&gt;

&lt;/tr&gt;

&lt;/tbody&gt;

&lt;/table&gt;&lt;/div&gt;…&lt;p&gt;&lt;/p&gt;&lt;/div&gt;
&lt;br&gt;
  &lt;/div&gt;
&lt;br&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/joyy-dev-organization/solodesk" rel="noopener noreferrer"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;br&gt;
&lt;/div&gt;

&lt;/li&gt;

&lt;li&gt;
&lt;strong&gt;Release Tag&lt;/strong&gt;: &lt;a href="https://github.com/joyy-dev-organization/solodesk/releases/tag/v0.1.0-challenge" rel="noopener noreferrer"&gt;&lt;code&gt;v0.1.0-challenge&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;

&lt;li&gt;
&lt;strong&gt;License&lt;/strong&gt;: Permissive &lt;a href="https://github.com/joyy-dev-organization/solodesk/blob/main/LICENSE" rel="noopener noreferrer"&gt;MIT License&lt;/a&gt; © 2026 ladydiamond&lt;/li&gt;

&lt;/ul&gt;




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

&lt;p&gt;SoloDesk is architected as a clean two-tier local system separating high-performance native desktop rendering from deterministic agent workflow orchestration:&lt;br&gt;
&lt;/p&gt;

&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart LR
    subgraph UI ["Native Flutter Windows Desktop"]
        direction TB
        AppShell["App Shell &amp;amp; Navigation"]
        Screens["BriefCheck · ScopeShield · PolitePay · LeadLoop · RepeatWork"]
        SQLite[("Local SQLite V4 DB\n%APPDATA%\\solodesk\\solodesk.db\n(Immutability Triggers)")]
        AppShell --&amp;gt; Screens
        Screens &amp;lt;--&amp;gt; SQLite
    end

    subgraph Service ["Local Loopback Service (127.0.0.1:3141)"]
        direction TB
        Auth["Bearer Token Auth (.runtime-token)\n+ CORS Origin Rejection"]
        Mutex["Atomic Concurrency Mutex\n(120s Timeout)"]
        Mastra["Mastra Deterministic Workflows\n(BriefCheck · ScopeShield · PolitePay · OfferDraft)"]
        Normalizer["Schema Normalizers\n(Zod Validation + Anti-Invention Filters)"]
        Auth --&amp;gt; Mutex --&amp;gt; Mastra --&amp;gt; Normalizer
    end

    subgraph Inference ["Local Ollama Runtime (127.0.0.1:11434)"]
        Ollama["Ollama Engine\nqwen3:1.7b (Open-Weight Model)\nOLLAMA_NO_CLOUD=1"]
    end

    Screens &amp;lt;== "HTTP Loopback (JSON)" ==&amp;gt; Auth
    Mastra &amp;lt;== "Loopback Model Stream" ==&amp;gt; Ollama&lt;/code&gt;&lt;/pre&gt;



&lt;h3&gt;
  
  
  1. Flutter Windows Desktop Shell
&lt;/h3&gt;

&lt;p&gt;Built with Flutter 3.44 and Dart 3.12, providing responsive desktop ergonomics, sidebar navigation, real-time elapsed request timers, dark mode slate theme, and direct SQLite integration (&lt;code&gt;sqflite_common_ffi&lt;/code&gt;). Scope immutability is enforced at the database engine level via SQLite triggers that abort any &lt;code&gt;UPDATE&lt;/code&gt; or &lt;code&gt;DELETE&lt;/code&gt; operations on approved scopes.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Local Mastra Workflow Engine (&lt;code&gt;@mastra/core&lt;/code&gt; 1.78.0)
&lt;/h3&gt;

&lt;p&gt;The local backend is a standalone TypeScript service running strictly on loopback &lt;code&gt;127.0.0.1:3141&lt;/code&gt;. Instead of unconstrained prompt chaining, we orchestrate multi-step deterministic workflows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;BriefCheckWorkflow&lt;/code&gt; (5 Steps)&lt;/strong&gt;: &lt;code&gt;validate-input&lt;/code&gt; → &lt;code&gt;select-niche-checklist&lt;/code&gt; (Design, Writing, General) → &lt;code&gt;analyze-with-agent&lt;/code&gt; → &lt;code&gt;validate-output&lt;/code&gt; → &lt;code&gt;return-draft&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;ScopeShieldWorkflow&lt;/code&gt; (5 Steps)&lt;/strong&gt;: &lt;code&gt;validate-scope-request&lt;/code&gt; → &lt;code&gt;load-approved-context&lt;/code&gt; → &lt;code&gt;compare-with-agent&lt;/code&gt; → &lt;code&gt;validate-evidence-classification&lt;/code&gt; → &lt;code&gt;return-editable-reply&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;InvoiceReminderWorkflow&lt;/code&gt; (4 Steps)&lt;/strong&gt;: &lt;code&gt;validate-invoice-facts&lt;/code&gt; → &lt;code&gt;prepare-reminder-prompt&lt;/code&gt; → &lt;code&gt;generate-draft-with-agent&lt;/code&gt; → &lt;code&gt;validate-and-normalize&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;OfferDraftWorkflow&lt;/code&gt; (4 Steps)&lt;/strong&gt;: &lt;code&gt;validate-plan-facts&lt;/code&gt; → &lt;code&gt;prepare-offer-prompt&lt;/code&gt; → &lt;code&gt;generate-offer-draft&lt;/code&gt; → &lt;code&gt;validate-and-normalize-offer&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Local Security Boundary
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Loopback Isolation&lt;/strong&gt;: Binds strictly to &lt;code&gt;127.0.0.1:3141&lt;/code&gt;. External network interfaces are never opened.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CSRF &amp;amp; DNS Rebinding Defense&lt;/strong&gt;: Inspects incoming HTTP headers; browser &lt;code&gt;Origin&lt;/code&gt; headers are rejected with HTTP 403 Forbidden.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ephemeral Bearer Authentication&lt;/strong&gt;: The service generates a cryptographic &lt;code&gt;.runtime-token&lt;/code&gt; upon startup; the Flutter client discovers this token via local process resolution.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single-Concurrency Mutex&lt;/strong&gt;: Small local models running on CPU/shared RAM cannot handle parallel requests. An atomic mutex queues incoming requests and protects the local Ollama instance.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. 12-Case Live Evaluation &amp;amp; Benchmark Telemetry
&lt;/h3&gt;

&lt;p&gt;In Milestone 8, we evaluated SoloDesk against a pre-registered 12-case synthetic benchmark across Design, Writing, and General freelance niches (6 BriefCheck cases, 6 ScopeShield cases) running live against &lt;code&gt;qwen3:1.7b&lt;/code&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Schema Validation Rate&lt;/strong&gt;: &lt;strong&gt;100% (12/12)&lt;/strong&gt; parsed cleanly against Zod schemas.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Average 6-Point Human Rubric Score&lt;/strong&gt;: &lt;strong&gt;5.8 / 6.0&lt;/strong&gt; (assessing grounding, no missing fact fabrication, justified classifications, advisory replies, schema validity, and latency measurement).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cold Start Latency&lt;/strong&gt;: &lt;strong&gt;17.4s&lt;/strong&gt; (cold model load).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Warm Average Latency&lt;/strong&gt;: &lt;strong&gt;38.9s&lt;/strong&gt; (range: 28.3s – 67.1s).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Peak Process RSS Memory&lt;/strong&gt;: &lt;strong&gt;175.5 MB&lt;/strong&gt; (safe for shared 16GB RAM laptop hardware).&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Hardest Verified Bug &amp;amp; Solution
&lt;/h3&gt;

&lt;p&gt;During M2 testing, our synthetic demo toggle became stuck on "Demo Data: ON". Inspection of &lt;code&gt;%APPDATA%\solodesk\solodesk.db&lt;/code&gt; revealed that SQLite's &lt;code&gt;CREATE TRIGGER IF NOT EXISTS&lt;/code&gt; is a no-op if the trigger already exists on disk. An earlier trigger lacking synthetic record bypass prevented purging synthetic records by throwing SQLite error 1811 (&lt;code&gt;IMMUTABILITY_VIOLATION&lt;/code&gt;). We solved this by implementing &lt;code&gt;_ensureTriggers&lt;/code&gt; inside SQLite's &lt;code&gt;onOpen&lt;/code&gt; hook, automatically dropping and recreating triggers on database startup, and wrapping the multi-table purge inside an atomic &lt;code&gt;db.transaction(...)&lt;/code&gt;.&lt;/p&gt;




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

&lt;p&gt;Open innovation is not just an ideological preference—for solo freelancers, &lt;strong&gt;it is the only architecture that makes business sense&lt;/strong&gt;:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Client Confidentiality &amp;amp; NDA Compliance&lt;/strong&gt;: A freelance developer building a stealth startup MVP or a designer branding an unannounced product cannot paste client requirements into cloud-hosted LLM endpoints. Open-weight models (&lt;code&gt;qwen3:1.7b&lt;/code&gt;) running on local open-source orchestration (Mastra) guarantee that sensitive trade secrets never leave the workstation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inspectable, Deterministic Orchestration&lt;/strong&gt;: Cloud AI wrappers are notorious for silent model drifts and prompt breakages. Mastra lets us inspect every pipeline step, validate inputs and outputs against Zod schemas, and catch hallucinations before they reach the user.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;True Vendor Independence &amp;amp; Offline Autonomy&lt;/strong&gt;: Freelancers work from coffee shops, client sites, trains, and flights. SoloDesk works completely disconnected from the internet. There are no API rate limits, surprise token billing, or deprecation notices.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Honest Architectural Trade-Offs
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Inference Latency&lt;/strong&gt;: Running quantized open models on consumer laptop CPUs (Intel UHD graphics) takes &lt;strong&gt;25s to 60s per inference&lt;/strong&gt;, compared to 2s on cloud APIs. We cushion this with responsive background polling, real-time elapsed timers, and cancelable requests.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Small-Model Boundary Limits&lt;/strong&gt;: 1.7B parameter models can struggle with subjective aesthetic nuances ("make it really pop"). We resolve this by enforcing defensive post-processing normalizers that convert ambiguous aesthetic requests into structured clarifying questions rather than ungrounded assumptions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storage at Rest&lt;/strong&gt;: Our local SQLite database is stored unencrypted in &lt;code&gt;%APPDATA%\solodesk\&lt;/code&gt; and relies on host OS user permissions.&lt;/li&gt;
&lt;/ul&gt;




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

&lt;h3&gt;
  
  
  Best Use of Mastra
&lt;/h3&gt;

&lt;p&gt;SoloDesk qualifies for &lt;strong&gt;Best Use of Mastra&lt;/strong&gt; by demonstrating genuine, deeply integrated, and inspectable use of &lt;code&gt;@mastra/core&lt;/code&gt; across all four operational business domains:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic Multi-Step Workflows&lt;/strong&gt;: We reject monolithic prompt chaining in favor of discrete, typed Mastra steps (&lt;code&gt;createWorkflow&lt;/code&gt;, &lt;code&gt;createStep&lt;/code&gt;) that enforce input validation, domain checklists, and post-inference output normalization.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;BriefCheckWorkflow&lt;/code&gt;&lt;/strong&gt;: 5-step workflow utilizing specialized domain checklists (Design, Writing, General) and strict anti-invention constraints prohibiting fabricated prices or unstated deadlines.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;ScopeShieldWorkflow&lt;/code&gt;&lt;/strong&gt;: 5-step comparison workflow taking structured SQLite scope items and incoming client requests to produce itemized semantic classifications with text-anchored citations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;InvoiceReminderWorkflow&lt;/code&gt; &amp;amp; &lt;code&gt;OfferDraftWorkflow&lt;/code&gt;&lt;/strong&gt;: Multi-step drafting workflows enforcing strict arithmetic invariants (minor units, calendar dates) and preventing small models from inventing unauthorized collection penalties or claiming a client already accepted a renewal.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Local Open-Weight Model Integration&lt;/strong&gt;: Mastra interfaces directly with local Ollama (&lt;code&gt;qwen3:1.7b&lt;/code&gt;) over loopback, proving that sophisticated multi-agent orchestration does not require cloud LLM dependencies.&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>mastra</category>
      <category>flutter</category>
    </item>
  </channel>
</rss>
