- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
In this paper, the authors borrow from control to create a framework for AI error monitoring that prevents cascading errors. This is a very important topic, and I think control theory is the right framework for this, but the paper is too hard to read, and has many other missed opptunitues detailed below.
Critical strengths
Cascading errors are a topic I am very interested in, so I was very excited to see this paper. I also think that transferring and translating concepts from control theory is a very good approach for this problem. I also didn't find errors in the paper.
Critical weaknesses
Despite the above, the paper does poorly as a translational paper, which is where I feel its potential contributions are.
First, it is hard to read, and I believe it may be inaccessible to those who do not already have some knowledge / background in control.
Second, but most importantly, it really doesn't do a good just making the case of where and under what conditions the framework will be useful to several issues.
-- There is an implicit underlying assumption that errors are directional, which is not made clear. -- The use of continuous time is not well justified, as no example that is not sequential is given. -- The authors do not make the case for why this is better than, for example, stopping all noticeable errors. It assumes that is not desirable but does not make the case for it, and therefore implicitly assumes that all errors are as consequential (which is not realistic). -- The limitation section is extra painful -- it is a shopping list of problems.
The biggest missed opportunity here is that I think this can work quite well for bias rather than all errors, where it makes sense we may want to allow X% bias, but not Y% -- which we may never be able to detect by only observing 1 transition at a time.
Overall, I think the theoretical contributions in themselves and the existing experiments do not merit sufficient contribution. However, adding convincing examples and making a case for where this will work better than alternatives will make a big difference here.
Questions for authors
-- Who do you think is the audience for this paper? And do you think it is clearly written for them?
-- Can you give real, clear examples of where this will work well?
-- Can you clearly articulate both assumptions and requirements for the framework to be successfully applied?
6 comments
Just commenting to say I have read this response, and I am not reassured by it that the issues I mentioned can be resolved. For now, I am keeping my score the same.
Thank you for reading our response. We understand that it has not resolved your concerns. For ease of reference, the most relevant parts of the revised PDF are:
- Practical value and comparison with simpler policies: Sec. 6 (p. 10) and App. G.4 (pp. 58–59), including when stopping every flagged error is preferable.
- Audience and concrete example: Sec. 1 and Fig. 1 (pp. 1–2).
- Conditions for applying the framework: end of Sec. 3 (p. 4) and Table 1 (p. 5).
- Unequal error consequences and your bias suggestion: Prop. 8 and Sec. 4.3 (pp. 5–7).
- Readability for readers without a control background: plain-language primer and glossary, App. G (starting on p. 56).
Could you indicate which concern remains decisive—for example, the paper’s readability, the conditions for applying the framework, or the evidence for its practical benefit?
We recognize that the empirical evidence remains synthetic and does not establish effectiveness in deployment. Your clarification would help us give a focused response during the remaining discussion.
Response to Reviewer Rwai
Thank you for the thoughtful review and concrete suggestions. You asked where this framework works better than the obvious alternative, stopping every error that can be noticed. The revision answers this with measurements, and the Discussion (Sec. 6) now opens with it.
When a calibrated level is better. We see three situations.
A concrete example (Fig. 1, App. G). An intake agent wrongly marks a refund as eligible, and three agents downstream read its conclusion. If each copies the error with probability 0.4, quarantining 17% of errors is enough to stop cascades. Now suppose half the cases are hard, where agents copy with probability 0.8, and the other half are never copied. A monitor that watches one handoff at a time still sees 0.4, but now 58% of errors must be quarantined. Only showing the same case to several agents reveals the difference. The same measurements also told us where to put an independent reviewer: last, behind agents that defer, was predicted to be riskiest, and for M2 it was (17.4% vs. 5.6% unsafe when placed first).
Q1: Audience. The paper is for engineers who build or audit multi-agent pipelines and need to decide where to put a reviewer, how much to quarantine, and how to know it is enough. The abstract and introduction now start from these decisions, Sec. 3 opens with an intuitive picture, and the abstract says "branching process" instead of "Hawkes process". We present the work as a research method, not a validated operational control.
Q3: Requirements. One needs an error that can be labeled and that something downstream uses, a way to show a handoff to fresh agents (we used 100 errors, 8 agents each), a tolerance for each error type, and a way to block a flagged conclusion. Each error type has its own tolerance, so errors need not be equally consequential. Table 1 lists each assumption and where it is relaxed or tested. The Limitations are now grouped into model assumptions, measurement scope, and external validity.
Bias (Sec. 4.3). Thank you, we adopted this suggestion. A tolerated bias becomes a tolerance on how common the biased decision is. For example, a 2% bias toward approval that later agents pass on 80% of the time settles at 10% of decisions, and keeping it at 5% requires quarantining at least a quarter of them. In M1's eight-agent chains (E7), the one-step model got this prevalence wrong in both directions, while per-case rates came close.
Direction of errors and continuous time. Errors need not flow one way: each error type has its own row in the interaction matrix, influence goes from a conclusion to whoever reads it, and feedback loops are allowed. Continuous time is there for asynchronous agents and monitor capacity; the thresholds depend only on the expected number of downstream errors, so they also hold in discrete turns. E9 tests a five-turn dialogue, where a reader sees the whole thread, not only its parent's conclusion. Errors spread 1.85 times further, so a dialogue has to be calibrated in its own format.
When stopping everything is better, and other limitations. If each conclusion is read by several agents and flags are accurate and cheap, stopping every flagged error is the best policy: live, with two or three readers per conclusion, it needed fewer inspections than any calibrated level. The framework does not help when propagation cannot be blocked without blocking the decision itself, or when the tolerance is zero. Finding out which situation applies took about 1,600 model calls per model; without measurement, assuming every error is copied gives a safe but conservative level. You were right that our summed containment rate is not a cost; the paper now calls it a proxy. Placement held for M2, not M1; one test in Table 1 failed; and two of E9's four predictions failed (App. E.7).
We believe the measured comparison and the example answer the question you raised. If you have a particular setting in mind, we would be happy to discuss how the method applies to it.