> For the complete documentation index, see [llms.txt](https://vayl.gitbook.io/vayl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vayl.gitbook.io/vayl-docs/documentation/getting-started/your-first-memory.md). # Your first memory This walkthrough shows every reconciliation action. In a chat client you just talk — the model makes the tool calls. Each step shows what you say, the **MCP tool call** the client issues, and the result. To make these calls yourself, see Calling Vayl from code. ## Store facts > **You:** The customer is on the Pro plan, and their primary database is Postgres. ```json {"name": "remember", "arguments": {"text": "Customer is on the Pro plan", "user_id": "cust_1"}} {"name": "remember", "arguments": {"text": "Primary database is Postgres", "user_id": "cust_1"}} ``` Two facts, two slots (`plan`, `primary_database`), both active. ## Supersede — a value changes > **You:** Actually, the customer moved to the Free plan. ```json {"name": "remember", "arguments": {"text": "Customer moved to the Free plan", "user_id": "cust_1"}} ``` `plan` is now **Free**; **Pro** is retired to history. There are never two live values for one slot. ## Retract — a value is removed > **You:** We dropped the Postgres database. ```json {"name": "forget", "arguments": {"text": "We dropped the Postgres database", "user_id": "cust_1"}} ``` `primary_database` is retracted — a recall returns "I don't know", not a stale "Postgres". ## Ask what's true now > **You:** What plan is the customer on? ```json {"name": "recall", "arguments": {"question": "what plan is the customer on?", "user_id": "cust_1"}} ``` → **"Free"** — reconciled state, not a list of every value ever mentioned. ## Ask what changed > **You:** What plan were they on before? ```json {"name": "recall", "arguments": {"question": "what plan before?", "user_id": "cust_1", "include_history": true}} ``` → **"Pro, then Free."** History is opt-in; it never leaks into a normal recall. ## See the provenance ```json {"name": "recall", "arguments": {"question": "what plan?", "user_id": "cust_1", "explain": true}} ``` Returns the exact facts behind the answer — source, confidence, and what each superseded. {% hint style="success" %} A superseded or retracted value **cannot** resurface as current: retired facts aren't loaded on a normal recall at all. History is opt-in, never the default. {% endhint %} ## Next * Calling Vayl from code — invoke these tools from a script or over HTTP. * [Core concepts](/vayl-docs/documentation/core-concepts/core-concepts.md) — the full reconciliation model. --- # 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://vayl.gitbook.io/vayl-docs/documentation/getting-started/your-first-memory.md?ask=&goal= ``` `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.