> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/16.-best-practices-security-and-production-readiness/16.9-upgrade-and-maintenance-strategy.md).

# 16.9 Upgrade and Maintenance Strategy

Since smart contracts are immutable, developers must plan for upgrades in advance.

This may involve:

* designing modular contract architectures
* using proxy patterns for upgradeability
* maintaining version control for contracts and APIs

Regular maintenance is also required for node software, APIs, and infrastructure components to ensure compatibility with protocol updates.

Production readiness in FreCx is achieved through a combination of secure design, reliable infrastructure, and continuous monitoring. By following these best practices, developers can build applications that are not only functional, but also resilient, scalable, and secure.

FreCx provides the foundation, but the quality of applications built on top of it depends on disciplined engineering and adherence to these principles.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.frequencychain.org/16.-best-practices-security-and-production-readiness/16.9-upgrade-and-maintenance-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.