> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devtune.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Library

> Use the project Library to find agent deliverables, uploaded source material, version history, and workflow memory.

The **Library** is the project catalog for deliverables and source material. It keeps the content, its provenance, and its version history together so you can find the current item without losing older evidence.

## Open the Library

1. Open a project
2. Select **Library** in the project sidebar
3. Use the **Library** tab to browse the catalog or the **Knowledge** tab to manage company context

Project members can read the catalog. You need project management permission to upload files, change version links, change agent availability, edit the Knowledge Profile, or review proposals.

## What appears in the catalog

| Kind       | What it represents                                                                                       |
| ---------- | -------------------------------------------------------------------------------------------------------- |
| **Report** | A report produced by a managed-agent run. The originating run remains attached as provenance.            |
| **Brief**  | A generated action brief. Regenerating a brief preserves the outgoing version instead of overwriting it. |
| **Upload** | A PDF, DOCX, Markdown, or text file uploaded by a project manager.                                       |
| **Memory** | A project-specific learning written back by a managed-agent run, with its source and expiry.             |

Reports, briefs, and uploads are deliverables. Workflow memory uses the same catalog and search index so its provenance and agent availability stay visible.

## Item states

Each item has a version state:

* **Current** is the newest item in a version chain.
* **Superseded** is an older version retained for history and deliberate retrieval.

Uploads and other items can also show an indexing state:

* **Indexing** means text was accepted and the search index is being built.
* No indexing label means the item is indexed.
* **Unindexed** means no searchable text could be extracted. The original upload remains available to download.

## Version chains

DevTune links versions automatically when they come from the same generator and refer to the same subject. The newest item becomes **Current** and the previous item becomes **Superseded**. The catalog shows the current version by default and keeps previous versions under the same item history.

For uploads, select **Upload new version** from the current item's detail page. This creates a new item in the existing chain; it does not replace the stored history.

If DevTune grouped versions incorrectly, a project manager can:

* **Detach** a Superseded item from its successor
* **Relink** a detached Superseded item to the matching next version

Relinking is limited to items that belong to the same generator-and-subject chain. Current items cannot be detached through this control.

## API and MCP access

The public surfaces expose the same catalog operations:

* `GET /projects/{projectId}/library` lists items, Current-only by default.
* `GET /projects/{projectId}/library/{itemId}` returns content, provenance, agent availability, and version metadata.
* `PATCH /projects/{projectId}/library/{itemId}` changes agent availability or a Superseded item's successor link.

See the [REST API endpoint list](/api-reference/overview#available-endpoints) and [Library MCP tools](/api-reference/mcp-server#library-and-knowledge-permissions).

## Next steps

* [Upload source material](/library/uploads)
* [Search the Library and control agent grounding](/library/search-and-grounding)
* [Manage the Knowledge Profile and workflow memory](/library/knowledge)