# 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](https://app.gitbook.com/s/XnYvLewhXbdSQIvAlbqN/release-notes).
{% 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 %}

***