> ## Documentation Index
> Fetch the complete documentation index at: https://velt-mintlify-e6426361.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Memory (Beta)

> Memory turns your team's review and approval activity into a searchable, queryable knowledge base with grounded answers, suggestions, and insights.

Memory is Velt's review-intelligence layer. It records every review decision your team (and your AI agents) make, lets you add your own reference material, and gives you REST APIs to search, question, and learn from all of it.

## What is Memory?

As people and agents make review decisions in Velt, Memory records each one as a **judgment**: the decision, the reasoning, who decided, and what they decided on. On top of that, you can ingest your **reference material** (guidelines, standards, policy docs) as knowledge sources.

With that foundation you can:

* **Search** past decisions semantically ("how have we judged copy with medical claims?").
* **Ask** natural-language questions and get grounded answers with citations.
* **Suggest** a decision for a new item, based on precedent.
* Surface **reviewer profiles**, detected **patterns**, aggregate **stats**, and proactive **alerts**.

## How it works

### Reviews create judgments automatically

Every review decision made in Velt becomes a judgment. You don't write judgments through the API; a new workspace starts empty and fills in as review activity happens.

### You ingest knowledge

Upload guidelines, standards, and policy docs (PDF, CSV, XLSX, or plain text). Memory converts each file to canonical markdown, extracts rules, and embeds it for semantic search.

### You query the combined base

Call `search` for raw decision records, `ask` for a grounded natural-language answer with citations, or `suggest` for a precedent-based recommendation on a new item.

### Memory derives insights over time

Reviewer profiles, decision patterns, workspace stats, and proactive alerts are computed from accumulated judgments.

## Core concepts

| Concept                                | What it is                                                                                                                                                                                                                                     |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Judgment**                           | An enriched record of one review decision: decision, reasoning, reviewer, content type, and scope, plus an agent block when an AI agent decided. The thing `search` / `ask` / `suggest` read over. Created automatically from review activity. |
| **Knowledge source**                   | Reference material you ingest (PDF / CSV / XLSX / text). Memory converts it to canonical markdown, extracts rules, and embeds it.                                                                                                              |
| **Scope**                              | `apiKey` (workspace), `organization`, or `document`; narrow reads to the right level. `documentId` requires `organizationId`.                                                                                                                  |
| **Embedding type**                     | `review` (decision + reasoning, the default) vs `content` (the reviewed item).                                                                                                                                                                 |
| **Filters**                            | Narrow results by `decision`, `judgeType` (human/agent), `contentType`, `reviewerId`, `annotationId`, or `dateRange`.                                                                                                                          |
| **Retrieval modes**                    | `search`/`ask` use vector search by default; set `recencyDays` for "what happened recently", or `filters.annotationId` to read one comment thread.                                                                                             |
| **Pattern / Reviewer profile / Alert** | Derived insights Memory computes from your judgments.                                                                                                                                                                                          |

## Where the data comes from

* **Judgments** are produced automatically as your team reviews and approves work in Velt; there's no "create judgment" endpoint. Expect Memory to be sparse on a new workspace and to get richer as review activity accumulates. Comment data from older SDK clients is enriched into Memory too, including a one-time backfill of historical data.
* **Knowledge sources** are the part you control directly: ingest the guidelines and standards you want Memory (and your agents) to reason against.
* **Profiles, patterns, and alerts** are derived from judgments over time, so they also need some review history before they're meaningful.

<Note>
  **Honesty by design:** if Memory has no relevant context, `ask` returns an empty answer with `confidence: 0` rather than inventing one. Treat that as "nothing learned about this yet"; it's expected for brand-new workspaces.
</Note>

## Limitations

* **Ingestion is asynchronous:** `ingest` returns `status: "processing"`; poll `ingest-status` for the terminal state.
* **File limits:** inline uploads up to 5 MB, by-reference uploads up to 30 MB; PDF / CSV / XLSX / plain text only.
* **Judgments are read-only via the API:** they're created from review activity, not written directly.
* **New workspaces start empty:** `ask` returns an empty answer and `suggest`/insights stay sparse until enough review history exists.

## Get started

<CardGroup cols={2}>
  <Card title="Setup" icon="gear" href="/ai/memory/setup">
    A hands-on walkthrough: add a knowledge source, ask a question, search past decisions, and pull a grounded suggestion.
  </Card>

  <Card title="REST API Reference" icon="code" href="/api-reference/rest-apis/v2/memory/search">
    All endpoints organized into Search & Q\&A, Knowledge, Insights, and Alerts, with full request and response schemas.
  </Card>
</CardGroup>