> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/guides/compatibility-and-retirements.md).

# Compatibility and Retirements

Find Classic integration guidance and release records, and keep Classic and Platform credentials, resources, and release history in separate scopes.

Use the documented contracts for every integration. Classic is a separate documented API with its own credentials and resources.

## Classic Integrations

Start with [Classic authentication](/developer-guide/getting-started/authentication.md), [Classic API resources](/developer-guide/classic-api/core-api.md), and the [Classic SDKs](/developer-guide/classic-api/sdks.md). [Terminology Mapping](/developer-guide/operations/reference/terminology-mapping.md) and [Memory Architecture & API Mapping](/developer-guide/operations/reference/memory-architecture.md) identify their Classic-specific scope. Platform credentials and resource IDs are not interchangeable with Classic ones.

## Release History

Use [Current Upgrade Guidance](https://docs.concurrence.com/api-reference/change-logs/upgrade-guide) for present compatibility decisions. [Release archives](https://docs.concurrence.com/api-reference/change-logs) record historical behavior and dates; evaluate current availability using the owning operation and workflow guide.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/guides/compatibility-and-retirements.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 `automate deployments from our CI pipeline` 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.