> 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/04-zones-information-and-arena-geometry.md).

# 4. Zones, Information, and Arena Geometry

## 4.1 Game Zones

4.1.1 The game has three zones: Arena, Hand, and Void.

4.1.2 The Arena is one shared public zone containing sixteen distinct Spaces arranged in a 4 × 4 grid.

4.1.3 Each player has a separate Hand and a separate Void.

4.1.4 A card can exist in only one zone and, while on the Arena, in only one Arena Space.

## 4.2 Arena

4.2.1 Every card on the Arena is face-up and has exactly one Marking Token showing its current Controller.

4.2.2 Cards on the Arena remain oriented toward their Owner. A card does not rotate when its Controller changes.

4.2.3 All Arena cards and their current characteristics are public information. Players may inspect them at any time that doing so does not delay play.

## 4.3 Arena Coordinates

4.3.1 If the Arena Mat prints coordinates, those printed coordinates are authoritative.

4.3.2 If the Arena Mat has no coordinates, determine coordinates from the First Player’s seated perspective: columns A through D run from left to right, and rows 1 through 4 run from nearest to farthest.

4.3.3 Coordinates never rotate or change during the game. Snatch-Sight remains Owner-relative and is not redefined by the coordinate system.

4.3.4 Distance between Arena Spaces is measured by Chebyshev distance: the greater of the absolute column difference and the absolute row difference. Diagonal adjacency therefore has distance 1.

## 4.4 Hand

4.4.1 A Hand is a private zone. Its Owner may inspect and reorder the cards in it.

4.4.2 A Hand has no maximum size.

## 4.5 Void

4.5.1 Whenever a card enters a Void, it enters face-down unless a specific effect states that it enters face-up.

4.5.2 A face-down card in a Void is private information. The Owner of that Void may inspect it; the opponent may not.

4.5.3 A face-up card in a Void is public information.

4.5.4 A Void has no maximum size.

4.5.5 When a card leaves the Arena, put it into its Owner’s Void face-down unless the effect moving it states another destination or face orientation.

## 4.6 Public Information

4.6.1 A player must accurately communicate public characteristics, Controller information, known continuous modifiers, and any required visible markers.

4.6.2 A player may not conceal, alter, or misrepresent public information.

## 4.7 Reveal

4.7.1 To Reveal a card is to show it face-up to all players for the duration of the instruction.

4.7.2 After a Reveal instruction finishes, a card that remains in a private zone returns to its prior face orientation unless the instruction states otherwise.


---

# 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/04-zones-information-and-arena-geometry.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.