# Roadmap

### Overview

Here are the upcoming evolutions of Madrix. Use this roadmap to plan adoption and internal releases.

{% hint style="info" %}
Roadmap is intent. Scope and order may change. What has been delivered goes into [Release Notes](/release-notes.md).
{% endhint %}

### Status

* **Now**: in progress. Delivery in the coming weeks.
* **Next**: prioritized. Will enter execution next.
* **Later**: direction. Depends on validation and capacity.
* **Under research**: validated problem. Solution still being designed.

## Now (next weeks)

#### Deploy and Cloud

* UX improvements in the flow of **Cloud Environments**.
* More clarity in pipeline errors (build vs runtime).
* Better post-deploy health-checks.

#### AI Chat Mode

* More predictable prompts for incremental changes.
* Better “mental diff” of what will be changed before approving.
* Safer re-execution in case of intermittent failure.

#### Quality and performance

* Reduction of loading times in Preview.
* Stability improvements during usage peaks.

##

## Next (30–60 days)

#### Editor Mode

* Faster navigation between modules, entities and UI.
* Improvements in editing rules and permissions.
* Earlier validations to avoid deploying with an obvious error.

#### Observability

* Logs more accessible by environment (Dev/Staging/Prod).
* Deploy events with clearer history.

#### Integrations

* Improvement in managing keys and secrets per environment.
* Simpler UX to connect common providers.

##

## Later (60–120 days)

#### Security and access

* Finer permission policies by module/entity.
* Evolutions in SSO and governance (as requested).

#### Platforms and extensibility

* More extension points for advanced customizations.
* Better support for enterprise standards (audit and compliance).

## Under research

* Ephemeral environments per branch/release.
* Faster and more controlled rollback in Prod.
* More opinionated project templates by industry.

## How to request a feature

When suggesting something, send:

1. **Goal** (what you need to achieve).
2. **Who uses** (profile and volume).
3. **Current flow** (where it hurts today).
4. **Definition of done** (how you will validate).

{% hint style="success" %}
The clearer the “definition of done”, the faster it gets prioritized.
{% endhint %}

***


---

# Agent Instructions: 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://docs.madrix.dev/roadmap.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.