- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper presents EviTrans, a composable state transition framework for video state tracking and reasoning. To address the limitations of conventional video question answering methods, which struggle to maintain long-term historical states, handle event dependencies, and rectify early-stage errors, EviTrans converts visual observations into executable state transition functions with evidence associations, rather than fixed state delta values. Through typed query contracts, entity binding, and event decoding, the framework enables structured state updates. It leverages a Persistent Segment Tree to compose state transitions across temporal intervals, supporting historical version preservation, efficient revision, and query reuse.
Experiments demonstrate that EviTrans achieves an overall score of 51.11 on the VSTAT dataset, outperforming multiple baseline methods. Compared with block-wise sequential execution, it reduces the latency from modification to answer generation by 22.2% and cuts memory usage for version storage by 52.1%. This study shows that explicit and composable state transitions can improve the accuracy and maintainability of long-horizon video reasoning.
Critical strengths
-
Improves the accuracy of video reasoning. EviTrans converts events occurring in videos into state transitions and continuously updates the world state, enabling the model to better understand the chronological order and mutual influences among events, and avoiding double-counting or omitted state changes. Meanwhile, query programs are adopted to directly compute answers, mitigating potential errors during LLM inference.
-
Enables efficient historical revision and information reuse. EviTrans employs a Persistent Segment Tree to manage state transitions within videos. If misrecognition occurs for prior events, only relevant records need to be updated, instead of reconstructing the entire historical structure. Furthermore, different queries can reuse the existing world state to reduce redundant computation, boosting inference efficiency and saving memory.
Critical weaknesses
-
There is a lack of stronger video reasoning baselines. Although ProViQ and VideoTree are relevant methods, they focus on programmatic VQA and hierarchical video representation respectively, and may not represent the most competitive solutions for stateful video reasoning. The related work section of the paper also discusses structured video memory approaches such as StreamForest and Event-Causal RAG, yet the experiments do not include direct comparisons against these methods.
-
The paper primarily conducts end-to-end evaluation only on VSTAT, which fails to demonstrate generalization and raises concerns of benchmark-specific design.
The core contribution of EviTrans is a general stateful video reasoning framework, yet VSTAT mainly targets tasks including counting, localization, attribute prediction, and state tracking. There is insufficient evidence to show that this framework generalizes to more diverse video understanding scenarios, such as complex human interactions, multi-event reasoning in long videos, and open-ended question answering.
Additionally, the paper adopts predefined query contracts, state schemas, and domain adapters. These components require manually defined state fields and operational rules tailored to the task. Consequently, the strong performance on VSTAT may partially stem from task-specific handcrafted rules rather than a highly general state transition framework.
Without cross-benchmark evaluation, it remains difficult to quantify the amount of extra manual engineering required when migrating the framework to new tasks.
Questions for authors
-
ProViQ and VideoTree are adopted as the main compared methods, while other structured video memory approaches including StreamForest and Event-Causal RAG are only discussed in related work without experimental comparison. Could the authors add direct experimental results against these stateful video reasoning baselines and analyze the performance gaps?
-
The evaluation is limited to the VSTAT benchmark, which raises concerns about benchmark-specific design and limited generalization. Since EviTrans is claimed as a general stateful video reasoning framework, could the authors provide cross-benchmark evaluation on additional video reasoning benchmarks covering complex human interactions, long-video multi-event reasoning, or open-ended VQA, to verify its generalization and reduce reliance on task-specific handcrafted rules (query contracts, state schemas, domain adapters)?
2 comments
Response to Rebuttal
I thank the authors for their rebuttal. While it was helpful, I still find the paper’s overall contribution and novelty to be limited, and the explanations provided in the rebuttal remain insufficient. I believe further revisions are needed and therefore maintain my original score.
Thank you for identifying closer baselines and the evidence needed to assess transfer.
W1 & Q1. Structured video-memory baselines.
StreamForest organizes visual tokens into event-level memory, while Event-Causal RAG retrieves observed State-Event-State records. EviTrans represents intervals as executable transitions conditioned on incoming state and boundary memory. These differences motivate a direct system-level comparison.
Table R4: VSTAT results available for comparison.
W2 & Q2. Cross-benchmark scope and task adaptation.
CATER Task 3 complements VSTAT with an independent evaluation of object identity and final-position inference under occlusion and recursive containment. Table R5 presents the cross-benchmark results.
Table R5: CATER Task 3 results.
Explicit state raises accuracy from 41.19% to 63.66%, and deterministic execution further improves it to 71.65% with either backend. These results demonstrate the benefit of explicit state representation and execution beyond VSTAT.
Task adaptation specifies position and containment fields, event and binding rules, geometry mapping, and a final-grid query through the transition interface. We will provide the adapter code and document the task-specific changes.