- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes Global Latent Workspace (GLW), which is a learned communication interface for a particular set of agent workflows. Three independently prompted experts first generate 120 continuous candidate states, 40 states initialize a workspace, and a controller skips or blends the remaining candidates into those positions. Then a final frozen reader consumes the workspace as embeddings. The controller evaluates the candidate vectors and decide when to skip / rewrite the workspace vectors that are used as context for the reader model, and it is trained to maximize final outcome correctness; Everything else is frozen.
The evaluation covers 6 multiple choice benchmarks with Qwen3-4B/8B. Training is done on ARC-Challenge and transferability is observed on other datasets (QASC/SciQ/CommonsenseQA/MedMCQA). GLW exceeds LatentMAS baseline on all 6 8B tasks and 5 out of 6 4B tasks.
Critical strengths
-
The system setup is clear and easy to understand.
-
The benchmark performance improvement over LatentMAS is meaningful, especially when it seems to have transferred to other datasets.
Critical weaknesses
-
The improvement over a TextMAS is less substantial when compared to LatentMAS (0.33 - 2.67 pp across 8B, and regressions on w/6 tasks at 4B). Although the generated text is substantially reduced, the reported communication metrics do not establish whether its overall accuracy-cost tradeoff justifies controller training.
-
The main transfer results use ARC-Challenge as the controller-training source and evaluated a limited collection of multiple-choice tasks. Although CommonsenseQA and MedMCQA provide useful shifts, the results leave open how transfer depends on the training source and how well the learned communication extends to more distinct domains.
Questions for authors
-
To address weakness 1, it would be beneficial to report the controller-training cost and complete inference cost on specific hardware, alongside accuracy uncertainty (e.g. paired confidence interval) for GLW and TextMAS?
-
To address weakness 2, it would be beneficial to a) include questions from a more distinct domain such as LegalMCQA, and b) train another controller on, e.g. CommonsenseQA, and evaluate the controllers on the same else datasets - ARC, MedMCQA, SciQ etc.
-
Clarification: could you specify if you choose one controller version using ARC validation and reuse it everywhere, or use each benchmark’s validation results to choose a version?