> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/guides/protocol-upgrades.md).

# Protocol Upgrades

{% hint style="info" %}
**Audience:** Nexus and TAP package developers.

**Goal:** Choose an application package upgrade path and preserve package, identity, business-state, and settlement evidence.
{% endhint %}

Use [Protocol Upgrades and Compatibility](/talus-docs-v2.1.0/concepts/14-protocol-upgrades-and-compatibility.md) to classify a change before choosing a package upgrade path. A successful protocol release does not by itself validate an update to a registered Tool, DAG, TAP, skill, Task, payment, or business object.

* [Upgrade an On-Chain Tool and Preserve Its Identity](/talus-docs-v2.1.0/guides/tool-development/build-onchain-tool-vertex-and-upgrade.md) for candidate verification, a compatible package-pointer change, and replay of the baseline operation.
* [Upgrade a TAP Package](/talus-docs-v2.1.0/guides/tap-development/upgrade-tap-package.md) for package, Tool, DAG, and application-state checks.

Use the release and network inputs in [Developer Setup](/talus-docs-v2.1.0/guides/getting-started/setup.md), and preserve package, identity, business-state, and settlement evidence throughout the upgrade.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talus.network/talus-docs-v2.1.0/guides/protocol-upgrades.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 `build a script that syncs our docs to a CMS` 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.