> For the complete documentation index, see [llms.txt](https://k-ai.gitbook.io/knowledge-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://k-ai.gitbook.io/knowledge-ai/reference/changelog.md).

# Changelog

## 2026-06-23 — Audit conflict parity & priority

* Audit API now 48 operations; Audit MCP surface now 21 tools.
* New tool `audit_question_conflict_ignore` — mark a question conflict as `IGNORED` (false positive / no change needed), mirroring `audit_full_audit_conflict_ignore`. Question conflicts now expose the full `OPEN · ANSWERED · RECOMMENDATIONS_READY · MANAGED · IGNORED` state set.
* Priority surfacing on full-audit conflicts: `audit_full_audit_conflict_list` accepts `only_linked_to_question`, and conflicts linked to a mandatory question are flagged `is_important` (with `linked_questions`). These share priority with question conflicts.

## 2026-05-13 — DKP refonte

* Documentation rebuilt around the Document Knowledge Platform positioning.
* 5-layer conceptual architecture documented (Sources → Ingestion → Semantic Document Layer → Governance & Quality → Exposure).
* Three OpenAPI 3.1 specifications published: Instance API (33 ops), Retrieval API (5 ops), Audit API (47 ops with 20 MCP).
* Authentication surfaces consolidated into a single section with a chooser table.
* Glossary of 22 DKP terms added.

## 2026-04-13 — API surface split

* `/search` and `/conversation` removed from the K-AI Instance API. Replacements: `retrieval_semantic_nodes_search` and host-LLM-driven conversation via MCP.
* Retrieval API (5 ops) and Audit API (47 ops) extracted as standalone surfaces hosted at `api-retrieval.kai-studio.ai` and `api-audit.kai-studio.ai`.
* MCP exposure added on both surfaces. Retrieval MCP and Audit MCP both stable.

## Earlier

Earlier history captured in the internal monorepo git logs.


---

# 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://k-ai.gitbook.io/knowledge-ai/reference/changelog.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.