> For the complete documentation index, see [llms.txt](https://mdev-1.gitbook.io/litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mdev-1.gitbook.io/litepaper/roadmap/phase-4-global-deployment-2027.md).

# Phase 4: Global Deployment (2027)

<figure><img src="/files/vdWz7T9eRTihbIOZQBMB" alt=""><figcaption></figcaption></figure>

By 2027, Motion xAI moves into global deployment.

* Hardware v.3 mass-produced and shipped.
* AI companion launches in Android + iOS apps.
* Web3 infrastructure is complete:
* Motion data tokenized into tradable units.
* Smart contracts automate payments and rewards.
* Governance DAO active with treasury spend.
* Developers and researchers start building on Motion xAI protocol, creating new apps and services.
* Expansion of signals: spine/arms/legs → heart rate, HRV, sleep, recovery.
* Democratising wellness data via normalising outputs from Oura, WHOOP, Apple Health, Samsung Health for portable use across ecosystems&#x20;
* Expansion of target market: corporate wellbeing programmes, non-sports rehabilitation and more.

This is where Motion xAI transitions from being “a product” to becoming a protocol.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mdev-1.gitbook.io/litepaper/roadmap/phase-4-global-deployment-2027.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.