ScopeLedger: a local AI tool for spotting out-of-scope client requests

·8 views

ScopeLedger is an open-source tool built by a developer for freelancers and small agencies to handle 'one more thing' requests that expand fixed-price projects. Users paste agreed deliverables alongside new client requests, and a locally run Gemma model suggests whether each ask is included, may be extra work, or needs discussion, with checkable source lines. The owner reviews and overrides every classification, sets the rate and effort, and exports a change-order draft without sending invoices or assuming client agreement. The author plans a $19 one-time local tool but says the price is unvalidated and no paying users have been acquired yet. Evaluation on eight synthetic development cases showed Gemma 3 4B matching six, a result the author notes is not a held-out benchmark.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Open-source Rust service wrapper runs Java apps on Windows, Mac and Linux

A new MIT-licensed Java service wrapper has been released on GitHub under the theonedev project, written in Rust. It has been tested intensively on Windows and Linux (amd64 and arm64) as well as Mac Silicon. OneDev uses the wrapper to run its Java application as a service on these platforms. Its configuration is a subset of the Java Service Wrapper (JSW), focusing solely on service wrapping and omitting JVM monitoring.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

BillCraft AI: Privacy-First Invoice Generator and Receipt Reader for Freelancers

BillCraft AI is an open-source invoice tool aimed at freelancers, contractors, and small business owners who want to avoid manual bookkeeping. It offers an invoice generator with saved business profiles, automatic totals, AI-assisted item descriptions, and branded PDF export. A companion reader uses local OCR and the open-weight Qwen 2.5 7B model to extract line items from receipts and PDFs, then checks the math on the server. The developers say the design keeps financial data off third-party cloud servers and contrasts it with subscription-based SaaS accounting tools costing $30 to $70 per month. The project was built for the Hacktoberfest Open-Source AI Challenge and is available as a live web app and on GitHub.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Guide Outlines Backend Exception Tracking for Express Pricing Rule Rollouts

A technical guide describes how a small Node.js Express service should capture backend exceptions while rolling out a property-pricing rule. It recommends attaching release, environment, request context, and privacy-reviewed identifiers at the Express error boundary, and triaging by error group rather than paging on every event. The author argues that silent failures, such as scheduled rollouts that never start, need separate heartbeat and counter monitoring beyond exception capture. The piece also presents a runnable Go transport that posts validated error events with key-based authentication, bounded retries, Retry-After handling, and exponential backoff. It notes that the Infrai provider lacks alert routing, source-map decoding, session replay, trace queries, and heartbeat monitoring, so those tasks must be assigned elsewhere.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Causal RL Framework Aims to Explain and Schedule Maintenance for Soft Robots

A developer describes building an explainable causal reinforcement learning pipeline to maintain bio-inspired soft robots, such as a silicone octopus-like arm that kept developing micro-tears. Standard deep RL agents maximize task reward but cannot identify why hardware is degrading, since soft-body failures like fatigue, hysteresis, creep, and delamination are not directly observable. The approach uses embodied sensing and a structural causal model linking sensor readings, actions, latent degradation, and maintenance events, so the agent can reason about interventions on the causes of wear. The author reports that the rate of change in strain sensor readings was a stronger early failure predictor than absolute values. The write-up presents the method as a way to make maintenance policies both effective and explainable.

0 comments Read more at DEV Community