1 / Question
Define coordination as observable behavior
- Turn-taking or legal-action compliance
- Response to shared state changes caused by another seat
- Use of public versus seat-private information
- Completion, stop, or recovery after another agent changes the state
- Room-level outcome reported separately from individual trajectories
2 / Controls
Freeze the whole multi-agent system condition
Record every seat's agent configuration, the orchestration order, Room game/version/configuration, retry policy, and the rule for replacing failed runs.
Changing one seat can change the observations and choices available to every later seat. Treat the Room trajectory as the unit of shared-state evidence and retain per-seat paths for diagnosis.
3 / Evidence
Collect per-seat and Room-level evidence
| Level | Evidence | Question answered |
|---|---|---|
| Seat | Qualified observation, action, rejection, recovery | How one agent responded to its available state |
| Room | Version, public events, lifecycle, settlement | How the shared system evolved |
| Cross-seat | Ordered action and state-change sequence | How one seat's action changed another seat's decision context |
4 / Interpretation
Report a bounded coordination result
Describe what the configured agents did in this named Room environment and protocol, including conflicts, incomplete runs, and information limits.
The record does not expose hidden reasoning, measure every form of collaboration, or replace a framework that supplies tasks, graders, statistics, and system-level benchmarks.