Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clarityq.ai/llms.txt

Use this file to discover all available pages before exploring further.

Product memory stores durable facts, definitions, and rules that apply to everyone working on a product. The Context Builder is where you create and manage these entries. Product memory is for context that doesn’t belong in the Semantic Catalog but matters every time someone asks a question — business definitions, naming conventions, data quirks, and querying preferences.

​
What Belongs in Product Memory

Good product memory entries are short, factual, and broadly applicable:
  • “All monetary amounts are stored in cents — divide by 100 to get dollars.”
  • “When asked about ‘last month’, use the previous full calendar month, not trailing 30 days.”
  • “The users table includes both real users and bot accounts. Always filter by is_bot = false unless explicitly asked about bots.”
Don’t use product memory for:
  • Metric or dimension definitions — those belong in the Semantic Catalog
  • Repeatable analysis workflows — those belong in Skills
  • Personal preferences — those belong in personal memory

​
Creating a Product Memory Entry

You can add product memory from two places:
  • Memory page → Product Memory tab — Click Add memory to start a guided flow.
  • Builder chat — Type /product-memory add or describe what you want the agent to remember in natural language (e.g., “remember that revenue should always exclude refunds”).
Each entry has a title (a short label identifying the topic) and content (the actual fact, rule, or instruction to remember). The agent structures both for you. Before saving, the agent checks for existing entries that might overlap or contradict the new one and warns you if it finds any.

​
Editing and Deleting

  • Edit — From the Memory page, click the edit icon on any entry. Or type /product-memory edit <name> in a Builder chat.
  • Delete — Click the delete icon on the Memory page, or type /product-memory delete <name> in chat.
Product memory follows the same draft-and-deploy cycle as other Context Layer components — changes are staged in your draft and only go live when you deploy.
Keep each memory item focused on a single rule or definition. Don’t bundle unrelated policies into one entry.