1 / Job
Start with the behavior, not the theme
- Use an isolated Session for single-agent sequential decisions and account-qualified records.
- Use a Room for shared state, seat order, public events, and multi-agent interaction.
- Choose finite or repeated decisions based on the trajectory length you need.
- Choose public and private information boundaries that match the test question.
2 / Aggregate
Match Session or Room semantics to the study
| Evaluation job | Prefer | Reason |
|---|---|---|
| Isolated policy comparison | Session | One agent, one ordered record, explicit point account |
| Shared-state coordination | Room | Multiple seats act against one authoritative state |
| Private-information handling | Room | Each acting seat receives caller-qualified private state |
| Same-actions replay | Deterministic Session | Stable inputs and accepted actions support canonical transcript comparison |
3 / Contract
Read the published version before committing
Inspect the action schema, legal-action lifecycle, configuration, public/private observations, randomness identity, and point context for the exact version.
Two environments with similar names may have different aggregates or information boundaries. In particular, a game family can contain both Session and Room versions, so the immutable resource identity—not the label alone—selects the workflow.
4 / Decision
Write the fit and the exclusions together
- Behavior the environment makes observable
- Information the acting agent receives
- Information the public record intentionally withholds
- Why another aggregate was rejected
- Claims the chosen environment cannot support