> 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/your-castle/research.md).

# Research

The University — military and peaceful sciences and troop tiers.

The **University** opens at Castle level 5. It researches **sciences**:

* **Military sciences** strengthen your troops — their attack, defence and health.
* **Peaceful sciences** speed up construction, gathering and healing.
* **Troop tiers** — new, stronger tiers of every kind of troop. The higher the tier, the stronger and the dearer the troops.

## The science tree

The University has **five tiers**. Tier I is open from the start; tiers II, III, IV and V open at University levels **5, 10, 15 and 20**. Every science goes up to **level 10**.

### Military sciences

For each of the three troops — **Shard Wardens**, **Harpooners**, **Spark Archers**:

| Science     | What it improves            |
| ----------- | --------------------------- |
| **Attack**  | The attack of that troop    |
| **Defence** | The defence of that troop   |
| **Speed**   | How fast that troop marches |

A military science of tier N works on the troops of **tier N** of its kind — so as you hire higher tiers, research the matching tier.

### Peaceful sciences

| Science          | What it improves                         |
| ---------------- | ---------------------------------------- |
| **Construction** | Every construction is faster             |
| **Hiring**       | Hiring of troops and gatherers is faster |
| **Gathering**    | Gathering on asteroids is faster         |
| **Healing**      | Healing in the Infirmary is faster       |

To research a science of a higher tier, research the same science of the tier before it first.

## How research works

* New tiers of sciences open with the levels of the **Castle** and the **University**.
* Every science has its own levels. The tree shows a line lit up when the way to a science is open.
* A science of tier N works on the troops of tier N of its kind.
* A closed tier can still be opened and looked at — you see what to build for.
* The University researches **one science at a time**. At release, a second research slot will be offered as a separate purchase — see [Subscriptions](https://electrum-decisions.gitbook.io/electrum-decisions-docs/economy/subscriptions.md).

Some sciences matter for the map: for example, gathering on higher-level asteroids needs the science **Deep Gathering**.

## Legion sciences

A legion has its own sciences, paid from the **legion treasury**. They widen the reach of the Legion Castle and the beacons, and every member gets their bonus. They are started by the head and the officers. See [The Legion Castle and Territory](https://electrum-decisions.gitbook.io/electrum-decisions-docs/legions/legion-castle-and-territory.md).


---

# 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/your-castle/research.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.
