> 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/feature-scope-mvp/post-mvp-roadmap.md).

# Post-MVP Roadmap

This page outlines upcoming features and development priorities after the MVP launch. Items listed here are planned, not yet released.

Following our October 13, 2025 MVP launch, AETHRA will evolve on a steady **6–8 week release cadence** with updates shaped by pilot insights and community governance.

* **October - November 2025:**
  * Enhanced multi-language support for employee portals
  * Advanced filtering and search within AI matching results
* **December 2025:**
  * Enterprise integrations: support for secure data import/export, directory synchronization, and single sign-on
  * Automated compliance reporting dashboards
* **January–February 2026:**
  * Community-driven feature releases based on governance proposals
  * Mobile app beta for real-time, on-the-go shift management
* **Beyond:**
  * Expansion into additional industries (education, public services, finance)
  * Scaling pilot programs into production deployments
  * Ecosystem partnerships to extend adoption

{% hint style="warning" %}
*Note:* Feature timelines are provisional and may shift based on pilot outcomes and user feedback. Official updates will be published in the [*Changelog*](/appendices/changelog-and-whats-new.md)*.*
{% 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/feature-scope-mvp/post-mvp-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.