> 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/foundations/05-owner-controller-and-marking-tokens.md).

# 5. Owner, Controller, and Marking Tokens

5.1 A card’s Owner is the player whose deck the card belonged to at the start of the game. Ownership never changes during the game.

5.2 A card’s Controller is the player indicated by its Marking Token while it is on the Arena.

5.3 A card that enters the Arena under a player’s control receives a Marking Token showing that player before any On Summon trigger is placed into the Trigger Queue.

5.4 A successful Snatch changes only the target Momon’s Controller. Flip or replace its Marking Token to show the new Controller.

5.5 Removing a card from the Arena removes its Marking Token. The token returns to the shared supply.

5.6 The game uses a shared supply sufficient to mark all sixteen Arena Spaces. A physical Marking Token must not limit a legal game action; use an equivalent unambiguous marker if a component is missing.

5.7 A Ward Token is a separate physical token used only to represent Ward on a Momon. When a Momon gains Ward, place one Ward Token on it. A Momon can have at most one Ward Token. A Ward Token is not a Marking Token, cannot be moved by an effect, and must remain associated with the Momon it marks. If a Ward Token is missing or the supply is insufficient, use a clear substitute marker; the absence of the original component does not end Ward. When Ward ends, remove the Ward Token and return it to the shared supply when possible.


---

# 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/foundations/05-owner-controller-and-marking-tokens.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.