LGAIDCMAMay 16

S-Bus: Automatic Read-Set Reconstruction for Multi-Agent LLM State Coordination

arXiv:2605.1707618.41 citationsHas Code
Predicted impact top 84% in LG · last 90 daysOriginality Incremental advance
AI Analysis

For developers of multi-agent LLM frameworks, S-Bus provides a practical middleware solution to prevent silent state corruption without requiring agent SDK changes.

S-Bus introduces a DeliveryLog mechanism that automatically reconstructs each LLM agent's read set from HTTP traffic to prevent structural race conditions in multi-agent systems. It achieves zero Type-I corruptions across 427,308 conflict tests, matching PostgreSQL SERIALIZABLE and Redis WATCH/MULTI, but is harmful in single-shard collaborative writing.

Concurrent LLM agents sharing mutable natural-language state produce Structural Race Conditions (SRCs): write-write and cross-shard stale-read conflicts that silently corrupt agent output. Existing multi-agent frameworks (LangGraph, CrewAI, AutoGen) provide no write-ownership semantics over shared state. We present S-Bus, an HTTP middleware whose central mechanism is a server-side DeliveryLog: a per-agent log of HTTP GET operations that automatically reconstructs each agent's read set at commit time without agent SDK changes under HTTP/1.1. The consistency property the DeliveryLog provides -- Observable-Read Isolation (ORI), a partial causal consistency over the HTTP-observable projection of the read set -- prevents structural race conditions when agents collaborate via shared shards. Three contributions: (C1) The DeliveryLog mechanism for automatic HTTP-traffic-based read-set reconstruction, with three-tier mechanised evidence: ReadSetSoundness and ORICommitSafety machine-checked in TLAPS (modulo one retained typing axiom); exhaustive TLC at N=3 (20,763,484 distinct states, zero violations); Dafny discharges 9 inductive soundness lemmas. (C2) Empirical structural-conflict prevention parity against PostgreSQL 17 SERIALIZABLE and Redis 7 WATCH/MULTI on shared-shard contention sweeps with 427,308 active HTTP-409 conflicts: zero Type-I corruptions across all three backends. (C3) ORI's operating envelope is topology-conditional: semantically neutral in dedicated-shard workloads; harmful in single-shard collaborative writing because preservation propagates concurrent contradictions. Source code: https://github.com/sajjadanwar0/sbus

Foundations

The foundational work for this paper's niche, ranked by how specifically the neighbourhood builds on it — not by global fame.

Your Notes