What you are building
An assistant embedded in a productivity product — email, calendar, notes, project management — acting for one user at a time.
Why memory decides whether it works
- Users state preferences once and expect them kept.
- Commitments made in one app (“I’ll send it Friday”) matter in another.
- Preferences change, and the old one must stop applying.
What Auld provides
- Private-by-default memory per user.
- Supersession for preferences and plans.
- Records from multiple apps with one identity.
- Cheap recall on Flex for assistants that recall on every action.
Getting there
Default to private visibility
Use
user:{id}for personal records.Ingest explicit statements
Preferences and commitments, not every keystroke.
Recall per action
Before drafting or scheduling, recall for that action.
Let users see and delete
Expose a “what you remember about me” view backed by the API.
Data and boundaries
Scenarios on this page are illustrative and do not describe a specific customer.
Frequently asked questions
How often should we recall?
Per user action that benefits from context. On Flex, recall is not metered.
Can users share memory with teammates?
Yes, by sending records with an audience visibility.