> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/whitepaper/chapter-14-the-four-stage-growth-roadmap.md).

# Chapter 14 · The Four-Stage Growth Roadmap

Four seasons of a tower

The protocol advances in four stages on predetermined on-chain triggers — as a tower goes from foundation to topping out, and then to living alongside time:

| Phase                                                             | Mission                                                                                                                                                                                                             | Trigger                                            |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| <mark style="color:$primary;">I · Laying the foundation</mark>    | Genesis stacking opens, completing the hundred-tier curve and the issuance of 52,500,000 VITA. The first builders arrive and the foundation is laid on the genesis block.                                           | Tier 100 sells out, or the set time window expires |
| <mark style="color:$primary;">II · Gathering the bricks</mark>    | The concentrated activation window opens and builders across the network vest their identities; initial liquidity and the protocol's Bitcoin reserve accumulate together as the bedrock begins to be poured.        | Activation window and protocol conditions met      |
| <mark style="color:$primary;">III · The tower in operation</mark> | Core functions come fully online, the Bitcoin reserve channel runs at full speed and the ecosystem enters durable operation. The tower's lamps are lit and the Ring of Life begins to turn.                         | Liquidity and safety thresholds reached            |
| <mark style="color:$primary;">IV · Perpetual growth</mark>        | The VITA Foundation hands contract authority in full to the DAO governance council, and the protocol becomes driven wholly by code and community consensus. The tower stands, and the bedrock thickens without end. | Handover conditions met                            |

Every transition fires automatically on on-chain conditions and is flagged publicly in contract state, so anyone can verify in real time where the protocol stands in its growth.


---

# 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://vitaprotocol.gitbook.io/vita/vita-protocol/whitepaper/chapter-14-the-four-stage-growth-roadmap.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.