Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your agent passed 10,000 evals. It can still deadlock.

If your agent workflow has 20 routing variables — retry counters, confidence thresholds, tool-success flags, budget checks — the guards on its edges combine in 2^20 = 1,048,576 ways. Run 10,000 evals and you have sampled under 1% of them (0.95%, to be exact). The other 99% is where the stalls live. A green eval suite proves the workflow can work. It says nothing about the combinations you didn't…

A workflow agent with 20 routing variables has 2^20 or 1,048,576 potential evaluation combinations. Running 10,000 evaluations only samples less than 1% of these possibilities (0.95% precisely). The remaining 99% of combinations are where failures, or "stalls," can occur. A green evaluation suite indicates the workflow can function, but it provides no information about the unseen combinations, including scenarios where all outgoing edges from a node are simultaneously closed, leaving the agent with no path forward.

This failure mode can manifest in research agents with a critic loop: a planner calls a tool executor, a critic node assesses the outcome, and two edges depart from the critic. One edge loops back for further attempts if the retry count is under 3, while the other exits. If the copy-paste error occurs, both edges close, causing the agent to become stuck, burning tokens and wall-clock time without crashing or erroring.

This issue stems from the interaction of multiple guards, which sampling tests are ill-equipped to detect. Tracing tools can illustrate the stalled run but only after the agent has expended resources, potentially retrying against paid APIs multiple times. Observability can only identify stalls that have already transpired and cannot predict whether a stall is possible in an untested graph.

The solution lies in counting the trap states before deployment. The SharpLogic tool takes a workflow graph, converts the guard conditions into a boolean variable set, encodes the graph as a CNF formula (stall formula), and uses zero-dependency Rust to count the satisfying assignments. This count represents the number of condition combinations that result in a workflow stall.

The tool also provides witness assignments that demonstrate how the stall occurs, enabling developers to locate the problematic node and understand the cause. By integrating this counting process into a build pipeline, developers can verify the absence of stalls during development, ensuring the agent functions as intended before deployment.

SharpLogic can handle up to 64 guard variables, with most practical graphs far below this limit. The tool operates in microseconds to sub-millisecond time for real-world workflow graphs, significantly faster than the exponential time required for dense random formulas. SharpLogic is not a proof of the exponential time hypothesis but an engineering solution that operates independently of that theoretical framework.

Developers can try the tool without signing up or installing anything by pasting a graph JSON into the browser trial at sharplogic.vercel.app/#try.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

useSearchNavigate: Type-Safe URL State Without the Drift

A small hook over TanStack Router's navigate that keeps tabs, dialogs, and pages in the URL with types intact, and why the write lands after the commit instead of during render.

  • useSearchNavigate hook maintains URL state with type safety
  • Resolves drift issue when refreshing pages or changing tabs
  • Declares search schema on route, uses typed hook for reads

How I Fixed TTS Hallucinations Without Regenerating Everything

The audit had done its job. I knew where the generated audiobook didn’t match the manuscript. Now I had another problem. Most of the audio around those errors was already good. The pacing worked.

  • Regenerating entire chapter inefficient for localized issues
  • Treat generated audio as recorded audio for punch-in approach
  • Match existing master audio for seamless replacement

Building a Client-Side QR Code Debugger with 6 Optical Tests and 10 Languages

Have you ever scanned a QR code that looked perfectly fine on a high-resolution screen, but failed miserably when printed? It happens all the time.

  • RahaLune QR Code Debugger performs six optical tests on uploaded images
  • Interface available in 10 languages including Arabic and Urdu
  • Dynamically updates page content for localized search visibility

More from Wednesday 28 October →