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

# Status and roadmap

This page is honest on purpose. **Implemented** means built, wired and tested. It does not mean proven with every third-party account. The full ledger, always current, is in [All capabilities](/reference/capabilities.md).

## Before mainnet launch (owner steps)

These need people and accounts, not code. The operator panel tracks them live (see [Operator panel](/running-the-platform/admin-panel.md)).

1. Deploy the three contracts and set their addresses.
2. External audit of the contracts and the executor, then custody of the executor key in a KMS or separate signer.
3. Private server settings: session secret, executor key, admin address, Privy, Pinata, platform AI key, Sentry.
4. One live smoke test per provider on testnet.
5. Backup and restore test, server and domain, legal review of Terms and Privacy.

## Coming soon

TikTok, AI influencer media, publish-and-run apps, browser sessions, asset acquisition, collectibles market and funding, swaps into arbitrary tokens, Elysium-native perps and stocks, and an external algorithm engine. Each is marked Coming soon in the capability ledger until it is built.

## Hosted-service deposits

Paying HYPE for thinking on the platform's account is off until the operator turns it on. Bringing your own key and agent-funded credits already work. See [Paying for thinking](/money/thinking-costs.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://docs.elevateelysium.xyz/reference/status.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.