Responsibility-Routed Rule Evolution is in the title and is listed as a contribution, but Sec. 4.3 leaves most of the explanation to App. E, Table 3 does not separate its gain from adding the EL/CL/VL rules themselves, and the case for routing rests on one single-run experiment on one backbone (Fig. 4).
The dataset is under-specified: Sec. 3.2 never defines the "processed alarm table" every method receives, Table 1 reports row counts but no input sizes in tokens, and the claim in Sec. 3.2 and App. A.1 that the full evidence does not fit in one prompt is never tested.
Summary of novelty:
The components are individually known: a ReAct-style tool agent on a mini-SWE-agent harness, hypothesis generation followed by verification and revision (HERO [R1], SpecRCA [R2], GALA [R3, R4]), graph-bounded investigation (GALA [R3, R4]), and LLM-driven prompt evolution (TextGrad (Yuksekgonul et al., 2024), AvaTaR (Wu et al., 2024), eARCO [R5]). What is new is the telecom-specific topology-impact verifier and the restriction of each evolution edit to one of three rule layers. The second is a modest change to existing prompt optimizers, and since the paper compares against neither RCA agents nor existing optimizers, the share of the gain that comes from AVERT's specific design cannot be determined.
Detailed comments to the authors:
The verifier and the TelcoOutageBench evaluation are solid engineering work, and the per-backbone ablation in Table 4 is more thorough than is usual for agent papers. The comments below concern how the method and data are presented and what the method is compared against.
-
Fig. 1 places three "layers" around a robot icon and does not show the actual sequence described in Sec. 4 (hypothesis, then EL, CL and VL, then verification and revision), and its CL box uses a different font and border color from EL and VL. Fig. 2 does not match Fig. 1 or Sec. 4.1, for example by calling diagnose before the evidence tools and leaving the dashed "Feedback: failed verification" arrow unexplained, and Fig. 3 shows visible editing artifacts (a pasted label in box 4, a patched line in box 2 in a different font, and swapped ACCEPT/ROLLBACK arrowhead colors).
-
Table 2 compares AVERT only with Direct Prompt and one in-house heuristic, and neither the cited telecom agent TN-AutoRCA (Wu et al., 2025) nor any existing prompt optimizer (e.g., eARCO [R5], TextGrad (Yuksekgonul et al., 2024)) is run. Related Work (Sec. 2) also misses earlier cloud RCA agents [R6-R9], and recent RCA agents built on the same hypothesize-then-verify idea with graph guidance, such as HERO [R1], SpecRCA [R2] and GALA [R3, R4], and these last make the verifier-in-the-loop contribution less distinctive than claimed.
-
The term "tool-verified agent" is never defined, and the paper does not say how many agents or LLM calls AVERT uses or whether the agent must call the verifier before answering. The verifier itself (App. D.3) only checks that the predicted failures cut all paths of the affected sites, so it cannot tell cause types apart or reject an over-broad hypothesis, and the "falsifiable" claim in contribution 2 is therefore overstated.
-
Rule Evolution is in the title, but Sec. 4.3 leaves the acceptance rule and routing details to App. E, and the "routing" is GPT-5.4's judgment rather than a defined credit-assignment procedure. Table 3 goes straight from no rules to evolved rules, so the gain from evolution is not separated from adding the hand-written EL/CL/VL prompt, and the case for routing rests on a single run on one backbone (Fig. 4).
-
The paper never explains how the "processed alarm table" is built from the raw alarms or whether that step used the labels, and it gives no collection period, selection criteria or annotator agreement. It also gives no token counts for the claim that raw alarms do not fit in one prompt.
-
The gains are not uniform, and the paper does not discuss this: for example, AVERT lowers Match F1 on Qwen3.5-9B, and the evolved rules lower RCA Score on Claude Opus-4.6 and DeepSeek-v3.2 (Table 2, Sec. 5.2). The benchmark contains only 22 hardware failures, and no per-cause-type results are reported, so it is unclear whether the method works beyond the power and fiber majority.
References (new; works already in the submission are cited by its own author-year keys):
R1. J. Lyu, J. Yi, P. Chen, S. Liang, L. Pan. HERO: Hypothesis-Centered Root-Cause Analysis for Microservice Incidents. ASE 2026. https://doi.org/10.1145/3832783.3837509
R2. L. Zhang et al. Hypothesize-Then-Verify: Speculative Root Cause Analysis for Microservices with Pathwise Parallelism (SpecRCA). ICSE-NIER 2026. https://arxiv.org/abs/2601.02736
R3. Y. Tian, Y. Liu, Z. Chong, Z. Huang, H.-A. Jacobsen. GALA: Can Graph-Augmented Large Language Model Agentic Workflows Elevate Root Cause Analysis? arXiv preprint, 2025. https://arxiv.org/abs/2508.12472
R4. Y. Tian, Y. Liu, Z. Chong, Z. Huang, Y. Li, H.-A. Jacobsen. GALA: Graph-Augmented LLM Agents for Root Cause Analysis and Incident Response in Microservices. ASE 2026. https://arxiv.org/abs/2608.08968
R5. D. Goel, R. Magazine, S. Ghosh, A. Nambi, P. Deshpande, X. Zhang, C. Bansal, S. Rajmohan. eARCO: Efficient Automated Root Cause Analysis with Prompt Optimization. ASE 2025 Industry Showcase. https://arxiv.org/abs/2504.11505
R6. Z. Wang et al. RCAgent: Cloud Root Cause Analysis by Autonomous Agents with Tool-Augmented Large Language Models. CIKM 2024. https://doi.org/10.1145/3627673.3680016
R7. Y. Chen et al. Automatic Root Cause Analysis via Large Language Models for Cloud Incidents (RCACopilot). EuroSys 2024. https://doi.org/10.1145/3627703.3629553
R8. W. Zhang et al. mABC: Multi-Agent Blockchain-Inspired Collaboration for Root Cause Analysis in Micro-Services Architecture. Findings of EMNLP 2024. https://arxiv.org/abs/2404.12135
R9. J. Xu et al. OpenRCA: Can Large Language Models Locate the Root Cause of Software Failures? ICLR 2025. https://proceedings.iclr.cc/paper_files/paper/2025/file/d29b8d53678015079e1d245c023e49d2-Paper-Conference.pdf