- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
BRIDGE addresses a failure mode in multi-agent systems. Its contribution is selective repair of broken inter-agent handoffs, using dependency graphs, offline intervention calibration, and pre-release verification. Its reported performance gains are good, and the ablations are informative. However, several technical claims are stronger than the supplied evidence supports, especially regarding verification guarantees, causal attribution, and transactional correctness. One concern is the authors should have done a thorough paper survey to properly position their contribution.
Critical strengths
- The paper addresses an important problem. In a distributed system that every individual agent may appear competent, but the collective fails because an essential dependency is not accounted for between agents. The paper addresses this problem in three parts:
Provenance graph: Identify which required information was produced, delivered, consumed, or misrouted. HandoffProbe: Estimate offline whether a particular repair is likely to help or harm. Verified release: Allow a repaired message to proceed only after an explicit local postcondition passes.
- The important idea is not just repairing a message. It is deciding whether it's worthy to repair at all.
Critical weaknesses
1. The paper misses a number of critical related work addressing the same or similar problems. I would advise the authors to enumerate their contributions with respect to these recent papers.
AgentAsk (ACL 2026) , MOC (ICML 2026) , MAST (NeurIPS 2025), SagaLLM (PVLDB 2025)
2. There are at least three potential over-claims with no supporting evidence:
2.1 Narrow the transaction claim to local verify-before-release, or implement genuine cross-component recovery. Cross-component recovery is non-trivial.
2.2 Report the experimental unit and task-clustered statistical analysis, or the performance claims are not proven to be statistically reliable.
2.3 Compare with 30-year work in the transaction processing domain, started by Jim Gray in 1908s; and in particular, the recent work SagaLLM, to sharpen novelty claims.
Questions for authors
-
Please answer your contributions with respect to the list of related work. Can you do a direct novelty-by-mechanism comparison?
-
Can you do a false-positive repair study? In this study, consider cases in which a dependency appears missing or malformed, but the native workflow would already succeed. Then measure how often BRIDGE intervenes incorrectly, how much harm it causes, and whether calibration reliably rejects those interventions.
8 comments
Response to Reviewer BqaZ (part 2)
W2: Transaction Scope, Statistics, and Positioning
W2.1: Narrow the transaction claim to local verify-before-release, or implement genuine cross-component recovery.
We agree. We will replace the word "transactional" throughout the paper with "verified release" and "local verify-before-release":
- What BRIDGE does: Candidate repairs run in a local staging buffer. If the postcondition check passes (
Check = 1), the controller releases the updated message; otherwise, it restores the local graph state and sends the original message.
In the MAST dataset, 98.2% of traces involve code and reasoning dialogues rather than stateful external APIs (1.8%, AppWorld), and 88.1% of handoff errors co-occur with later execution errors. Checking handoffs before release stops missing context early without needing distributed locks.
W2.2: Report the experimental unit and task-clustered statistical analysis.
-
Experimental units: TeamBench and DeepSeek SILO-BENCH run 1 rollout per task across 90 tasks ( independent tasks). MAST evaluates 562 independent traces. On GPT SILO-BENCH (3 seeds across 90 tasks), Table 2 reports the sample standard deviation () across the 3 seeds (we will change to in Appendix D.2).
-
Task-clustered test: Treating each of the 90 tasks on GPT SILO-BENCH as one unit (), a two-sided paired Wilcoxon signed-rank test gives (19 tasks with net gains, 6 with net losses, 65 ties, and 0 tasks with ).
W2.3: Compare with 1980s transaction processing theory and SagaLLM to sharpen novelty claims.
Classic database transactions (Gray, 1980s) use locks and two-phase commit to guarantee all-or-nothing execution across nodes. SagaLLM adapts the saga pattern to multi-step LLM workflows by checking workflow constraints and running post-commit compensating actions when a step fails. BRIDGE addresses a narrower, earlier step: checking a single inter-agent message in a local buffer before sending it to the next agent. To compare global workflow validation with local handoff graph diagnosis on static traces, we adapted SagaLLM's two-phase validation pipeline to the 562 MAST traces under DeepSeek-V4.1-flash (using the same setup as Table 3 and Table 9):
| Method | Tokens / Trace ↓ | Mode 2.4 F1 | Mode 2.5 F1 | Macro-F1 | Overall F1 (%) ↑ (Table 3) | Control Handoff FPR (n=278) ↓ |
|---|---|---|---|---|---|---|
| Direct Prompting | 6,686 | .034 | .562 | .298 | 62.5 | 44.2% |
| BRIDGE (Ours) | 9,116 | .142 | .613 | .377 | 68.6 | 64.4% |
| SagaLLM (adapted) | 15,236 (+67.1%) | .145 | .614 | .379 | 68.8 | 74.8% |
Breakdown of SagaLLM alerts on the 278 control traces (which have no handoff failures):
| Control Subset | Traces (n) | Handoff False Positive Rate | Workflow Violation Rate | Compensation Triggered |
|---|---|---|---|---|
| All control traces | 278 | 74.8% (208/278) | 83.1% | 63.3% (176/278) |
| Controls with non-handoff errors (e.g., tool/runtime errors) | 221 | 84.2% | 91.9% | 71.0% |
| Clean controls (zero MAST errors) | 57 | 38.6% | 49.1% | 33.3% (19/57) |
This comparison shows how the two designs match their intended goals:
-
Diagnostic accuracy and token cost: SagaLLM and BRIDGE reach similar handoff F1 scores (Macro-F1 0.379 vs. 0.377, overall F1 68.8% vs. 68.6%, paired McNemar ). Because SagaLLM extracts workflow state tables and runs global validation in two calls, it uses 15,236 tokens per trace compared to 9,116 for BRIDGE (+67.1%).
-
Difference in target scope: On the 221 control traces that contain non-handoff errors (such as tool failures or runtime crashes), SagaLLM flags workflow violations on 91.9% of traces and triggers compensation on 71.0%. This happens because SagaLLM is designed to catch broad workflow execution failures, whereas the MAST metric here only scores handoff failures. BRIDGE focuses specifically on inter-agent handoff edges and further filters alerts through an offline utility gate before acting.
Response to Reviewer BqaZ (part 3)
Q2: False-Positive Repair Study
Q2: False-positive repair study.
Below are four examples from our benchmarks where Native execution succeeds, showing how BRIDGE avoids breaking working trajectories:
-
SILO-BENCH global distinct count task (utility gate abstention): Two agents hold private number sets and must count the total unique numbers (28). In Round 1, before the agents share their sets, the provenance graph flags a missing fact and proposes an
ASKaction. The utility gate abstains. In Rounds 2 to 6, the agents share their sets on their own and both submit 28. -
TeamBench protocol bridge task (utility gate abstention during coding): Twice during Planner-to-Executor handoffs, the draft message leaves out references to earlier contract details, which raises a candidate rewrite. The utility gate abstains both times, and the coding agent fixes all bugs and passes all 12 unit tests.
-
SILO-BENCH distributed XOR task (local rollback on failed check): During a forced
INTEGRATEprobe test, Agent 0 sends a short reply in Round 1. BRIDGE generates a candidate rewrite in the local staging buffer. Because the rewrite fails the postcondition check, BRIDGE discards the rewrite in the buffer and sends the original message. The agents finish the task normally and submit the correct answer (251). -
MAST clean programming trace (graph consumption tracking): In a clean trace where all tests pass, the tester agent updates a test as requested by the reviewer agent. In the final turn, the reviewer confirms the test is correct and adds a general comment. Direct Prompting and SagaLLM misclassify this final comment as an ignored instruction, whereas BRIDGE's provenance graph sees that all 5 earlier handoffs were already consumed and outputs
pass.
In short, the utility gate and local postcondition check work together as a two-stage filter that prevents unnecessary or faulty repairs from breaking successful runs. We will add this study to the Appendix, and we thank you again for your valuable suggestions.
Response to Reviewer BqaZ (part 1)
Thank you for your helpful comments on related work and system scope. Our responses to each point are given below.
W1: Related Work and Novelty
W1.1 & Q1: Missing related work (AgentAsk, MOC, MAST, SagaLLM) and direct novelty-by-mechanism comparison.
AgentAsk, MOC, and MAST are cited in Section 2 and compared in Tables 2–3. In the revised paper, we will add SagaLLM (PVLDB 2025) and include the following comparison of problem scopes and mechanisms:
AgentAsk (Lin et al., ACL 2026): Uses an LLM prompt to ask peers for clarification. Because it does not track whether facts were already delivered or gate interventions by expected utility, it can over-intervene (lowering GPT SILO-BENCH from 68.9% to 65.6%, vs. 77.8% for BRIDGE).
MOC (Guan et al., ICML 2026): Summarizes multi-hop message history to save tokens, but does not check whether the receiving agent actually uses the delivered facts (scoring 63.3% on GPT).
MAST (Cemri et al., NeurIPS 2025): Defines 14 failure modes for post-hoc trace analysis, without runtime intervention.
SagaLLM (Chang & Geng, PVLDB 2025): SagaLLM and BRIDGE study different problems at different stages of execution. SagaLLM focuses on multi-step workflow consistency and post-commit recovery: when an external action fails or violates a workflow constraint, SagaLLM generates and executes compensating actions to restore overall workflow state. In contrast, BRIDGE focuses on message handoffs between agents before the message is released downstream. The two approaches are complementary: BRIDGE filters handoff omissions before message delivery, while SagaLLM recovers external workflow state after multi-step execution failures.