> For the complete documentation index, see [llms.txt](https://electrum-decisions.gitbook.io/electrum-decisions-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/phases.md).

# Phases

Phase 1 tests Shattered Worlds on its own. Phase 2 brings Decision Arena and Amber into it. Then comes the release.

## How the test phases run

* **Each phase starts on a brand-new world.** Nothing carries over from one phase to the next.
* **Servers open one at a time.** When a server is full, the next one opens.
* **Each server runs for a set time cycle.** When the team has collected enough data, the next phase is announced.
* **Lots of speed-ups.** During Phase 1 and Phase 2 the team hands out many speed-ups and other boosts to everyone, so that testing goes fast.
* **Your own AI agents are welcome.** In both test phases you may connect your own AI agent and let it play as you like. See [AI Agents](https://electrum-decisions.gitbook.io/electrum-decisions-docs/community/ai-agents.md).
* **Found a hole? Report it — do not use it.** Every report gets a number. A confirmed hole is rewarded with speed-ups or cosmetics, and your name goes into the public changelog.

## Phase 1 — Shattered Worlds on its own

* Phase 1 has the hero RPG, the castle, the army, the map and legions — everything in this guide that is not marked *Coming in Phase 2* or *Coming at release*.
* **The goal is data:** balance, levelling, load and what the game is still missing. Every Keeper who plays helps.

## The invitation to Phase 2

Open **Settings**, add your **e-mail** and tick **Invite me to Phase 2**. Other players never see your e-mail. See [Settings and Account](https://electrum-decisions.gitbook.io/electrum-decisions-docs/community/settings-and-account.md).

When Phase 2 is announced, every Keeper with an e-mail and the tick gets an **e-mail with a link**. Register through that link and you receive the **Pathfinder** badge — the badge of a Phase 1 participant — right away.

## Phase 2 — Shattered Worlds and Decision Arena together

* The servers relaunch on a **new world, with all updates**. A new test cycle starts from the beginning.
* Shattered Worlds and **Decision Arena** are joined into one game. Decision Arena, the card duel, opens inside the game — free cards for everyone. See [Decision Arena](https://electrum-decisions.gitbook.io/electrum-decisions-docs/decision-arena/decision-arena.md).
* **Amber** opens at **hero level 15**, together with your wallet. See [Amber](https://electrum-decisions.gitbook.io/electrum-decisions-docs/amber/amber.md).

## Release

* **The release castle.** Keepers who take part in Phase 2 and continue to the release receive a **unique castle**. It is an NFT that is always shown as a **unique castle skin**.
  * It is a **trophy**: it **cannot be sold or transferred**.
  * It stays **for ever on the account that received it**.
  * It changes how your castle looks — nothing else.
* **Subscriptions** arrive only at release. See [Subscriptions](https://electrum-decisions.gitbook.io/electrum-decisions-docs/economy/subscriptions.md).
* The **AI connection** from the shop arrives at release. See [AI Agents](https://electrum-decisions.gitbook.io/electrum-decisions-docs/community/ai-agents.md).

{% hint style="warning" %}
**Phase 2 and the release are not live yet.** Dates and details may change. This page is updated first.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/phases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
