> For the complete documentation index, see [llms.txt](https://serotolabs.gitbook.io/tradeclash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://serotolabs.gitbook.io/tradeclash/the-globe/game-surface.md).

# Globe as Game Surface

The 3D globe is not decoration. It's the primary interface — the game table where auctions happen, regions pulse, and results flash.

***

## Region Mapping

Each globe region maps to a lot category:

| Region            | Category         | Example Markets                                       |
| ----------------- | ---------------- | ----------------------------------------------------- |
| **North America** | Politics         | Elections, legislation, appointments                  |
| **Europe**        | Macro            | Interest rates, inflation, economic policy            |
| **Asia**          | Tech & Culture   | Product launches, regulatory actions, cultural events |
| **Middle East**   | Geopolitics      | Conflicts, diplomacy, sanctions                       |
| **South America** | Sports           | Match outcomes, transfers, tournaments                |
| **Africa**        | Emerging Markets | Development milestones, commodity events              |
| **Oceania**       | Entertainment    | Awards, releases, media events                        |

Categories shape the character of each lot. A Politics lot pulls from political prediction markets. A Macro lot from economic ones. Category familiarity is a real edge.

***

## Visual States

The globe communicates game state through visual feedback:

**Idle** — No active auction. Globe shows the prediction market dashboard with market activity across regions. Subtle ambient movement.

**Active auction** — The lot's region pulses with an orange ring. Camera pans smoothly to the region when a new street starts. Not a cinematic swoop — fast and functional.

**Reveal** — Brief color flash on the region: green for profit, red for overpay. The moment lands.

**Between lots** — \~10 second cooldown. Globe returns to dashboard state. Next lot's region begins a subtle glow before dealing.

***

## The Low-Poly Aesthetic

The globe uses a low-poly Earth model — distinctive and performant. It's not trying to be Google Earth. The simplified geometry gives it character and keeps frame rates high across devices.

Visual design follows the game's overall aesthetic: dark background (pure black to near-black), subtle borders, warm orange accent for active states, emerald green for wins, rose red for losses. No harsh overlays — region highlights use subtle glow in the category's color.

***

## Camera Behavior

* **Street start**: Smooth pan to the active lot's region. Quick, not dramatic.
* **Between lots**: Slow ambient rotation. The globe as screensaver.
* **Dashboard mode**: Player-controlled rotation and zoom. Tap a region to see markets.

The camera serves information. It points you where the action is without making you wait for an animation to finish.


---

# 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://serotolabs.gitbook.io/tradeclash/the-globe/game-surface.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.