> 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/appendices/changelog-and-whats-new.md).

# Changelog & What’s New

Stay up to date on AETHRA’s platform development, governance events, and roadmap progress.\
This changelog tracks major public milestones from beta to post-MVP growth.

***

## June–August 2025 – Closed Beta Phase

* Closed Beta launched with 20 early testers across key sectors
* Initial AI matching and on-chain credential verification went live
* Early user feedback collected for roadmap refinement

***

## October 2025 – MVP v1.0 Launch

* Public MVP released to general users
* Live dashboard + analytics added
* UI/UX design updates based on pilot feedback

***

## November 2025 – Post-MVP Updates

* Enhanced multilingual support for employee portals
* Advanced AI filtering and shift-matching search interface

***

## Nov–Dec 2025 – Compliance & Enterprise Layer

* Enterprise data export & reporting APIs (audit-ready, regulator-facing)
* Automated compliance dashboard (real-time monitoring + exportable reports)

***

{% hint style="info" %}
This changelog is updated monthly in sync with the product deployment cadence (every 6–8 weeks).
{% 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/appendices/changelog-and-whats-new.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.
