verde-memory10.1 KB
View saved version →
---
name: verde-memory
description: Use when the user wants to save, find, update, or publish their team's shared knowledge in Verde — decisions, conventions, project facts, processes, lessons — or asks a question about their own team's projects, decisions, or history that Verde's memory should answer. Not for general-knowledge questions, calendar or scheduling tasks, or storing passwords, keys, or other secrets.
---
# Verde — recall, save, and keep team knowledge current
Verde is the team's persistent, shared memory, reached through the Verde plugin's tools. A **vault** belongs to a team and holds **buckets** (folders); buckets hold **documents**. Every document carries a visibility: **public** (on the open internet once published), **company** (the whole team), or **private** (the signed-in user only). A document may be narrower than its bucket, never wider.
Tools: `list_vaults`, `list_buckets`, `search_memories`, `get_memory`, `list_recent_memories`, `list_comments` (read); `create_bucket`, `update_bucket`, `add_bucket_fields`, `propose_memory`, `update_memory`, `set_properties`, `supersede_memory`, `archive_memory`, `publish_memory`, `add_comment` (write). Every tool takes `vault` as a `team/vault` slug from `list_vaults`.
## Facts you must not infer
- **Which vault or bucket** — always take it from `list_vaults` / `list_buckets`.
- **That something is not in Verde** — only `search_memories` can establish that.
- **Dates** — convert "next Friday" to the real date before saving.
- **That the user wants a public document published** — only an explicit approval in this conversation, after seeing the exact text, counts.
## Workflow 1 — Recall (a question about the team's projects, decisions, conventions, or history)
1. `search_memories` with a natural-language `query`: a short plain-words description of what you need — the topic and the kind of fact ("how we approve deploys", "Team plan pricing decision") — not a list of keywords or identifiers. Add `include_historical: true` when the user asks how something changed or what it used to be.
2. Results carry short excerpts, `status`, `is_current`, and a `url`. Pick the relevant hits and fetch full text with `get_memory` — pass several ids in `ids` in one call. Follow `references` / `referenced_by` ids the same way when they matter.
3. Answer from the documents. Name the document title, say when it was last updated, and distinguish the current version from superseded history explicitly ("current: $29/seat; superseded: $19/seat").
4. Share the `url` when the person would want to open the document itself (a design doc, decision record, plan). Skip it for a one-line fact.
5. A miss is not an answer. Before saying Verde has nothing, search two or three more times with different wording — synonyms for the key terms, the broader topic, a likely document title — and drop any filters you added. Only then say so plainly. Once the user settles the answer in conversation, offer to save it (Workflow 2).
Where a document contradicts your own assumption, the document wins. Where the document is clearly stale, say so and offer to supersede it (Workflow 3).
## Workflow 2 — Save (the user states something durable, or asks to remember it)
Durable = a decision and its reasoning, a stable preference or convention, a project fact, constraint, or deadline, a correction of a previous belief, a process or fix that worked.
1. **Get agreement.** Offer in one line ("Save this to Verde?") and wait for a yes — unless the user already asked Verde to save or remember it, or the connection has Automatic Memory on (see below).
2. **Check for duplicates.** `search_memories` for the topic. If a document already covers it, switch to Workflow 3 instead of creating a second one.
3. **Place it by description.** `list_vaults` (each vault carries a `description` of what belongs in it), then `list_buckets` for the vault (each bucket likewise). Choose the vault and bucket whose descriptions fit; do not ask the uPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
