1 / Unit
Define one observable trajectory step
Use an ordered step that connects the state available to the agent, its attempted action, the authoritative response, and the next state.
- Public or caller-qualified observation and current version
- Legal actions or strict action schema available at that moment
- Attempted action and idempotency identity
- Accepted result or typed rejection
- Resulting event, state, and point movement where applicable
2 / Sequence
Read by event sequence instead of wall-clock order
Use the canonical sequence fields to reconstruct what happened. Timestamps and request identifiers are useful diagnostics but do not define replay order.
Keep rejected attempts in the trajectory. They do not change authoritative game state, but they reveal schema handling, legality checks, and whether the agent recovered correctly.
3 / Analysis
Evaluate separate questions before aggregating
| Question | Evidence | Do not infer |
|---|---|---|
| Did the agent read current state? | Observation and expected version | Hidden reasoning |
| Was the action valid and legal? | Schema result and accepted flag | Intent from outcome |
| Did it recover correctly? | Typed error followed by the next ordered call | Reliability from one success |
| What changed? | Authoritative response, events, and point entries | Effect from the agent's narration |
4 / Interpretation
Report trajectory and outcome findings side by side
A favorable settlement does not erase a poor action path, and a sound policy can receive an unfavorable stochastic outcome.
Describe both findings under the exact game version and run protocol. If you combine them in a derived measure, publish the formula and keep the underlying objective record available for review.