> For the complete documentation index, see [llms.txt](https://docs.aethra.work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aethra.work/call-to-action.md).

# Call to Action

AETHRA is entering its decisive phase: moving from pilot testing to public launch. With the closed beta already at capacity, the next window of opportunity is October 13, 2025. This is when early participants will lock in their position at the core of the AETHRA network.

## Secure Early Access to the MVP

The public MVP goes live on October 13, 2025. Early access guarantees you priority onboarding and influence as new integrations roll out.

***

## Contribute to the Ecosystem

Pilot slots are closed, but community participation is open. By staking AETHRA and engaging in early feedback loops, you can help shape the roadmap and signal which industries and features should be prioritized next.

***

### vAETHRA: Future Governance

AETHRA’s governance layer, vAETHRA, will give participants the ability to:

* Decide how protocol incentives are distributed
* Influence ecosystem priorities and growth strategy
* Set credentialing and verification standards that define network trust

**Governance will be introduced in a later stage, once the platform has matured and usage data can guide meaningful decision-making. Early contributors will be first in line to participate.**

***

{% hint style="info" %}
The pilot may be closed, but the network is just opening. On October 13, 2025,  those who act now will already be positioned as the first wave of AETHRA builders, stakeholders, and decision-makers.
{% 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://docs.aethra.work/call-to-action.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.
