Examples¶
Seven runnable scenarios, from one vault and one agent up to every memory type in one topology. Each folder has its code, its data and a README that walks through it.
| # | Example | What it shows |
|---|---|---|
| 01 | Single-Vault RAG | Single vault, single agent. Semantic RAG over PDF, MD, TXT, DOCX with source attribution. ~100 lines. |
| 02 | Multi-Agent Isolation | Two agents, two vaults. Each agent has no retrieval path to the other's vault: isolation enforced at the infrastructure layer, not through metadata filtering. ~200 lines. |
| 03 | Persistent Memory | An agent that recalls context across sessions using semantic queries. "financial constraints" retrieves "cut cloud costs by 15%" written three days prior. |
| 04 | Access Control | Three agents, five vaults: private, shared between a subset, and public. A tiered support system where access boundaries reflect organizational boundaries. |
| 05 | Procedural Memory | One agent, two vault types, semantic and skill, integrated via MCP. Retrieves knowledge for what to say and skills for how to say it. |
| 06 | Episodic Memory | One account followed across six months. Facts are superseded instead of overwritten, so the briefing uses only what holds today while April is still reconstructable. |
| 07 | Full Memory Topology | Everything in one place: three agents, six vaults, all three memory types, access rules, a year of facts replayed with their dates. The capstone example, a small bakery, and the dataset behind the live demo. |
Each folder installs with pip install -r requirements.txt. Examples 01 to 06 call an LLM, so their READMEs say which provider and key to set; example 07 needs none. Example 07 is the dataset behind the live demo: run it, then ctxvault ui from its folder to see the same memory live.