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

# Release process

What Alpha and General availability mean when you see them in a release note.

mediarithmics is a platform in constant evolution. A new feature reaches you in two phases.

{% stepper %}
{% step %}

### Alpha

The feature is open to a small number of clients working directly with the mediarithmics product team, who grant access and expect regular feedback in return. Iteration is fast and rough edges are expected: the point of the phase is to confirm the feature is useful and usable before it is opened up.
{% endstep %}

{% step %}

### General availability

The feature is production grade and available to every client whose contract is compatible with it. It is documented publicly from this point on.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Where a page in this documentation says a feature is in Alpha, this is what it means - and what to expect before it reaches General availability.
{% endhint %}

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Change log</strong></td><td>Every release, grouped by year.</td><td><a href="/release-notes/readme.md">Change log</a></td></tr></tbody></table>


---

# 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.mediarithmics.io/release-notes/release-process.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.
