We're debating the next feature for StateGuard. Would you trust this? - Indie Hackers

Join

Like

Bookmarks

Comments

Report

Over the past few weeks, we've been building StateGuard, an open-source runtime reliability SDK for AI applications.

The goal isn't to improve model quality. It's to keep AI workflows running when something around the model changes unexpectedly - schema drift, provider response changes, tool output mismatches, validation errors, missing fields, and similar runtime failures.

Instead of the application crashing because one component changed, StateGuard attempts to repair the mismatch and continue the workflow safely.

One capability we're considering next is Semantic Repair.

For example:

A provider returns "done" instead of "completed"

A tool renames "assistant_message" to "assistant"

Two APIs use different field names for the same concept

Equivalent values are represented differently across providers

Instead of failing, StateGuard would recognize that the intent is equivalent, normalize the payload, and continue execution.

The question is:

Would you actually trust something like this in production?

Or would you rather these cases fail loudly so you can fix them yourself?

We're trying to build the roadmap around real developer feedback, so I'd genuinely love to know:

Where would you draw the line between "safe automatic repair" and "developer intervention required"?

Have you run into failures like these yourself?

Is there another runtime failure you'd solve before semantic repair?

GitHub: https://github.com/dood1ebyte/stateguard

adi

on August 5, 2026

Share

Say something nice to adi07…

Post Comment

Trending on Indie Hackers

I built a startup-idea scanner. It just told me none of my 3,400 ideas are easy wins.

77 comments

“I’ll just post on Upwork” is not a client strategy. Here’s what I built instead.

60 comments

Building a Shopify bundles app for stores with real fulfillment: here's the wedge

42 comments

I Just Discovered My Analytics Numbers Are Mostly Fake. Here Is Why.

37 comments

I recorded myself using 200+ indie SaaS products cold. Here are the 7 conversion killers that keep showing up.

36 comments

The Capture Trap

33 comments