> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/deprecation-notices/readme.md).

# Deprecation Notices

This page lists features slated for removal or replacement on the site, when the deprecation will be actioned, and

{% updates format="full" %}
{% update date="2026-11-01" %}

## Tag Recommendations 

With the advent of Adjudicated Tagging in release 1.117, Tag Recommendations are no longer the preferred mechanism of leveraging CSTs and ASTs for a fully human-in-the-loop Tagging workflow.

### Replacement

Instead of generating ASTs and CSTs as recommendations, switch the nest to Adjudicated Tagging mode with a single reviewer. Generating ASTs and CSTs will populate tags into that reviewer level data set, and a reviewer need only adjudicate those tags to make them final.

### Timeline

Deprecation notice will become active November 1 2026. On December 1 2026, the "Recommend" button will be removed entirely, though recommendations will still be available in the tagging module for users who previously generated them. On January 1 2027, recommendations will be entirely removed and no longer be displayed in any nest.
{% endupdate %}
{% endupdates %}


---

# 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.nested-knowledge.com/deprecation-notices/readme.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.