> For the complete documentation index, see [llms.txt](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/abilities-and-game-state/11-abilities-trigger-queue-and-continuous-effects/11-5-resolution.md).

# 11.5 Resolution

11.5.1 Follow an Ability’s instructions in written order.

11.5.2 Complete each instruction before beginning the next. Perform State-Based Conditions only after the entire Ability resolves, except when a rule explicitly requires an immediate check.

11.5.3 A permanent or indefinite change created by a resolving Ability must remain representable. Use a counter, reference token, or other unambiguous physical record.

11.5.4 Unless an Ability explicitly creates an effect on a player or in another zone, an indefinite change to a Momon ends when that card leaves the Arena because it becomes a new object.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://momon-wonder.gitbook.io/comprehensive-rules-1.0.0/abilities-and-game-state/11-abilities-trigger-queue-and-continuous-effects/11-5-resolution.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.