One memory, fed by your files and by the work.
What your agents establish stays established, and you can see what it holds and erase it.
Memory
Two shelves- What workedLearnings
When a customer's bank details change by email, wait for the signed change notice before updating them.Why: lookalike senders have redirected payments this way.
Source: 4 sessions by 2026-09-24 - What your files sayClaims
Meridian Books is $62,400 in arrears across invoices INV-88201 and INV-88344.
Meridian BooksWhat is owedOwen will send the revised fuel surcharge schedule.
Owen Brandt, by 15 October 2026
Fed by your files and by finished runs
Documents make it useful on day one. Finished runs add what the team learns along the way.
- Documents and meeting notes, as markdown, text, HTML, PDF or Word files
- A new version of a document replaces the values the old one held
- Public web pages, watched and refreshed when they change
- Every run your agents finish
Two shelves, each with its own job
Learnings hold what worked, and claims hold what your files say and what is owed.
- Learnings: what to do and what to skip, offered while the work runs
- Claims: what your files say, dated, with the sources attached
- Obligations are claims too: commitments from meeting notes, in the note's own words, with the date they are due
- An obligation can be marked done or dropped, or moved to a new date
Erased with its source
Delete a document and the claims and learnings that rested only on it go too, with a receipt.
- The receipt counts what was removed, by kind
- A claim that has other sources keeps them and loses only the citation
- Deleting an agent removes its claims and documents
Bring us one Workflow your team runs every day.
We show it running in the assistant your team already uses, with an example from your industry. 30 minutes, no data needed.