Memory for knowledge base assistants

What you are building

An assistant over internal documentation, wikis and decision records, used by employees to answer “how do we…” and “what did we decide about…”.

Why memory decides whether it works

• Documents are revised, and retrieval often returns the old version because it matches the question better.
• Decisions are made in meetings and threads, not only in documents.
• Some documents are restricted to teams.

What Auld provides

• Document sections as records with effective dates; revisions supersede earlier versions.
• Decisions from meetings and threads alongside documents.
• Audience visibility for team-restricted material.
• asOf recall for “what was the policy in March?”.

Getting there

1. 01

   Split documents by section

   Use stable ids like policy-travel#approvals.

2. 02

   Send revisions with effective dates

   Same id for corrections; new id for a new version if you want both kept.

3. 03

   Add decision sources

   Meeting notes and announcement threads.

4. 04

   Cite in answers

   Return document title and version with every answer.

Data and boundaries

Scenarios on this page are illustrative and do not describe a specific customer.

Frequently asked questions