# Expansion Layers

To enhance gameplay depth, personalization, and community participation, Rebellion introduces optional expansion layers. These features are designed to increase engagement while maintaining fair, skill-based competition.

***

#### Power-Ups (Optional Gamified Features)

Available in select leagues, power-ups provide additional strategic choices without undermining core balance:

* **Captain** – Designate one asset to receive a 1.5× score multiplier.
* **Hedge Card** – Reduce the negative impact of a single underperforming asset by 50%.
* **Sector Focus** – Earn double points if three or more assets from the same category outperform during the league period.

***

#### NFTs & Cosmetics

Cosmetic and identity-based features are incorporated to increase player personalization and status signaling:

* Cosmetic NFTs such as trophies, badges, and portfolio skins can be earned or purchased.
* These do not affect gameplay or scoring and are strictly non-pay-to-win.
* Players can display earned badges and collectibles on public profiles.

***

#### DAO Integration (Planned)

In future phases, Rebellion will open key parts of the platform to decentralized governance:

* Community members will be able to propose new asset categories, league themes, or scoring adjustments.
* Governance may extend to voting on rule modifications, feature prioritization, and platform economics.
* DAO-based proposals will be gated by staking or contribution metrics to ensure credible participation.

***

These layers are designed to evolve with the user base, allowing the most engaged players to shape the direction of the platform over time.


---

# Agent Instructions: 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:

```
GET https://rebellion.gitbook.io/rebellion/platform/expansion-layers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
