GraphBit: A Graph-based Agentic Framework for Non-Linear Agent Orchestration

Yeahia Sarker, Md Rahmat Ullah, Musa Molla, Shafiq Joty

arXiv:2605.13848 · 2026-05-16 공개 · arXiv · PDF

agentic-framework graph-based error-recovery memory-architecture tool-invocation state-transitions gaia-benchmark rust-engine

Abstract

Agentic LLM frameworks that rely on prompted orchestration, where the model itself determines workflow transitions, often suffer from hallucinated routing, infinite loops, and non-reproducible execution. We introduce GraphBit, an engine-orchestrated framework that defines workflows explicitly and deterministically as a directed acyclic graph (DAG). Unlike prompted orchestration, agents in GraphBit operate as typed functions, while a Rust-based engine governs routing, state transitions, and tool invocation, ensuring reproducibility and auditability. The engine supports parallel branch execution, conditional control flow over structured state predicates, and configurable error recovery. A three-tier memory architecture consisting of ephemeral scratch space, structured state, and external connectors isolates context across stages, preventing cascading context bloat that degrades reasoning in long-running pipelines. Across GAIA benchmark tasks spanning zero-tool, document-augmented, and web-enabled workflows, GraphBit outperforms six existing frameworks, achieving the highest accuracy (67.6 percent), zero framework-induced hallucinations, the lowest latency (11.9 ms overhead), and the highest throughput. Ablation studies demonstrate that each memory tier contributes measurably to performance, with deterministic execution providing the greatest gains on tool-intensive tasks representative of real-world deployments.

한국어 요약

📋 한 줄 요약

**[AI Agent / Orchestration]** 결정적 DAG 기반 엔진 오케스트레이션과 3단계 메모리 구조를 갖춘 Rust 기반 에이전트 프레임워크 GraphBit을 제안하여, 환각 라우팅과 무한 루프 문제를 해결한다.

🎯 핵심 기여도

💡 핵심 아이디어

"오케스트레이터를 LLM에게 맡기면 LLM이 망친다"는 진단 아래, LLM은 typed 함수로만 다루고 흐름 제어와 상태 관리는 결정적 엔진이 책임지도록 책임 분리를 한다. 이로써 재현성·감사 가능성·도구 집약적 작업에서의 안정성을 모두 확보한다.

🔬 기술적 접근법

📊 주요 결과

💭 의의 및 한계

**의의**: 실서비스에 적합한 reliability/auditability/속도 특성을 갖춘 에이전트 인프라 설계의 모범을 제시. **한계**: DAG 사전 정의를 요구하므로 동적·자유로운 탐색이 필요한 작업에는 표현력의 한계, 정의/유지 비용이 추가됨.

🚀 실용적 활용