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

# Context Vault Overview

> Workspace document memory for shared company knowledge.

Context Vault is MemContext's workspace knowledge system. It stores shared
company documents separately from personal assistant memory, extracts durable
facts from those documents, keeps citations back to the original source chunks,
and lets teams add curated company facts that may not be documented yet.

Use Context Vault when your application needs a shared knowledge base for a
team, customer, department, or organization. Use personal memory when the
knowledge belongs to one user or assistant.

The API path, product surface, and docs use the Context Vault name:
`/api/context-vault/...`.

## Core model

* `workspaceId` is the hard team boundary.
* `scope` is a hard lane inside a workspace, such as `hr`, `engineering`, or
  `billing`.
* `project` is a soft grouping inside a scope, such as `onboarding`,
  `api-platform`, or `q3-pricing`.
* Documents are stored as `memory_sources`.
* Source passages are stored as `memory_source_chunks`.
* Extracted company facts are stored as document memories.
* Curated company facts are stored as company memories.
* Citations are stored through `memory_evidence`.

## Main capabilities

* Upload PDFs, DOCX files, images, CSV, Markdown, HTML, and text.
* Ingest public file URLs and documentation URLs.
* Search source chunks, extracted memories, or both.
* Add atomic company facts for important context that is not in a document yet.
* Browse extracted memories by workspace, scope, and project.
* Submit feedback and corrections.
* Load evidence chunks for any extracted memory.

Context Vault does not synthesize a final answer by itself. The search endpoint
returns ranked chunks, document memories, and curated company facts so your
application can build its own grounded answer layer.