Cover image

Saved, Still Rebuilt: The Search Cost of Reusing AI Workflows

TL;DR for operators An AI system can save a successful workflow and still spend substantial effort reconstructing how that workflow was originally assembled. Efficient reuse depends on whether the completed procedure is directly available to subsequent planning as a callable operation. FormCraft proposes a capability architecture in which primitive and composed operations share typed interfaces, retain their formation provenance, and can participate in further compatible composition. Verification determines which operations enter a persistent library. ...

November 2, 2026 · 8 min · Zelina
Cover image

Hear First, Commit Later: Voice-Light's Turn-Taking Tradeoff

TL;DR for operators A conversational voice assistant must decide when to respond, when to stop speaking, and which parts of its generated response actually reached the user. These decisions have different costs and should not depend on a single turn-taking prediction. Voice-Light demonstrates a hybrid architecture that separates uncertain evidence from consequential actions. Acoustic onset can trigger reversible playback ducking, while stronger evidence governs interruption and cancellation. Language and speech generation can begin privately before the user’s turn is confirmed complete, and only browser-acknowledged playback enters durable conversation history. ...

October 23, 2026 · 9 min · Zelina
Cover image

When Old Instructions Outlive Their Authority

TL;DR for operators An AI agent can retain every instruction in a conversation and still execute the wrong task. The problem becomes acute when users replace requirements, withdraw constraints, or revise decisions on which earlier work depended. A controlled study introduces IntentFlux, a benchmark that measures this failure under changing user instructions.1 In a turn-matched experiment, mean task score falls from 0.734 without revisions to 0.469 with revisions. Additional conversation length alone cannot explain the difference. ...

October 22, 2026 · 8 min · Zelina
Cover image

Every Tool Call Succeeded. The Workflow Still Failed.

TL;DR for operators An AI agent can complete every reported tool call while leaving a business workflow in an inconsistent state. The critical distinction is between successful invocations and the external effects that remain after the workflow commits or aborts. A study of 98,291 remotely discovered Model Context Protocol (MCP) tools found that 74.0% emitted at least one standard annotation field. Yet the standard annotation vocabulary could not fully express any of eight transactional capabilities identified by the researchers. ...

October 21, 2026 · 8 min · Zelina
Cover image

Before You Retry the Agent, Check the Evidence

TL;DR for operators An agent can already have the information needed to answer a question and still produce the wrong answer. Diehl and Lim’s Evidence-Inference Reconstruction (EIR)1 addresses that failure mode by storing retrieved source sentences separately from the agent’s evolving interpretations, then generating the scored answer in a fresh call that sees only the original question and accumulated evidence. ...

October 18, 2026 · 7 min · Zelina
Cover image

The Navigator Is Not the Motor: What VISOR Gets Right About Embodied AI Architecture

TL;DR for operators A familiar robotics design question is where to draw the boundary between understanding and control: should one learned system interpret the scene, choose where to go next, and explain that choice, or should those functions remain distributed across separate perception and planning modules? VISOR1 tests a middle position. Its 3B model combines language understanding, visual-spatial reasoning, target recognition, and high-level destination selection, while a conventional planner handles the low-level movement. It is not the strongest navigator on the leaderboard, but on OVON its post-trained model records a 21.70% success rate on Val Seen and 22.00% on Val Unseen, an unusually small seen-to-unseen change even though stronger baselines achieve much higher absolute success rates. ...

September 8, 2026 · 9 min · Zelina
Cover image

Success Is Not the System: Rethinking How AI Agents Should Be Evaluated

TL;DR for operators An enterprise agent can finish a workflow and still be a poor production system. It may require repeated retries, call the wrong tool before recovering, exceed an acceptable cost envelope, fail under small environmental changes, or depend on a human to stop a consequential action. Bin Xu’s survey, AI Agent Systems: Architectures, Applications, and Evaluation, treats those behaviors as part of the system being evaluated, not as incidental implementation details.1 Its central abstraction places the model inside an execution loop with memory, tools, verifiers, and an environment. Section 6 then evaluates the resulting system across multiple dimensions rather than collapsing performance into task success. ...

September 7, 2026 · 5 min · Zelina
Cover image

More Memory, Worse Decisions: Why Agent Recall Needs Routing

TL;DR for operators An agent has a recurring allocation problem: how much of its past should it bring back before answering a question or choosing its next action? More history increases the chance that useful evidence is available, but it also increases the amount of material competing with the information that matters now. ...

August 27, 2026 · 8 min · Zelina
Cover image

The Reviewer Was Right. The Workflow Still Failed.

TL;DR for operators A quality-control component can correctly identify a defect and still add little value if the next stage ignores the correction. That distinction matters for AI workflows built around critics, reviewers, validators, or approval agents: reviewer accuracy measures whether the warning is right, not whether the warning changes what the system ultimately does. ...

August 18, 2026 · 7 min · Zelina
Cover image

Role Call: Who Your Agents Are Actually Listening To

TL;DR for operators Teams are easy to label. Understanding who actually listens to whom is harder. Hong’s paper on learned coordination conventions proposes a diagnostic for inspecting how cooperative reinforcement-learning agents route information between predefined roles.1 The central move is architectural: place role labels in both the querying agent’s representation and each ally’s representation, then use cross-attention to expose a role-to-role routing matrix. ...

July 10, 2026 · 20 min · Zelina