# Overview

Welcome to Cardano – Upgrades, this space will provide relevant information on major updates and hard forks.

Each major update or change will have its own sub-section including, where applicable,  general information and overviews, any readiness or deployment information and frequently asked questions. Following deployment any lessons learned, feedback and completion reports.

The information in this space is overseen by Intersects [Technical Steering Committee](https://technicalsteeringcommittee.docs.intersectmbo.org/) and its relevant working groups, such as the hard fork working group and deployment working group.

{% hint style="info" %}
Currently the hard fork working group meets twice every week, Tuesdays at 3pm UTC and Thusdays at 2pm UTC, using Luma events from the following calendar: <https://luma.com/calendar/cal-TMjYNpSY4huYYif>
{% endhint %}

{% hint style="info" %}
It is suggested that you bookmark this space and regularly refer back as new upgrades are announced and more details are added!
{% endhint %}

***

**Planned upgrades**

| Name                                                                     |
| ------------------------------------------------------------------------ |
| [van Rossem upgrade](/van-rossem-upgrade/van-rossem-upgrade-overview.md) |

**Completed upgrades**

| Name           |
| -------------- |
| Plomin upgrade |
| Chang upgrade  |

Note that information on previous upgrades may be temporarily hidden during any active upgrade. This is to ensure that only relevant information is available and aims avoid the propagation of potentially misleading or historical information.&#x20;


---

# 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://cardanoupgrades.docs.intersectmbo.org/overview/readme.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.