Docs menu
Sleep, knowledge and the morning briefing
What happens overnight: how experiences become trusted knowledge, how contradictions and forgetting work, and what the morning briefing contains.
Last updated Sep 12, 2026
Tulimoa Memory does its real work while your agent is idle. Once a night, starting at 02:17 UTC, a librarian model goes through everything the day left behind. Your agent never has to tidy up its own memory.
When a memory sleeps
- Experiences that are at least 30 minutes old and not consolidated yet are up for the night. Until then,
recallalready finds them among the raw experiences. - A memory sleeps once at least 3 new experiences are waiting, or when the oldest one has waited more than a day. A single note waits until the night after next at the latest.
- Each night has a token budget for the librarian that grows with the size of the memory, see the storage fee. Whatever does not fit waits for the next night.
- While a storage fee is unpaid, sleep pauses. Recall keeps working.
What the librarian does
Related experiences are grouped by meaning. For each group the librarian sees the experiences, with personal data already replaced by placeholders, plus the five closest pieces of existing knowledge, and proposes changes. Every change is checked for format, secrets and scope before it is applied.
- Merge. Duplicates and near-duplicates become one strong piece of knowledge instead of five weak ones.
- Abstract. What happened becomes what it means: a fact, an entity, a preference, a procedure, a concept or an open problem.
- Link. New knowledge is connected to what it relates to, is part of, is about, caused or came after, so tomorrow one cue pulls the whole thread.
- Replace. Outdated knowledge is superseded instead of piling up next to the new version.
From provisional to trusted
- New knowledge starts provisional. It becomes trusted once it was seen at least 3 times and is at least 7 days old.
- Contradictions go into quarantine. When provisional knowledge contradicts trusted knowledge, it is flagged, left out of
recalland listed under Needs review, in the briefing and in the dashboard. There you decide: New is right or Before is right. A single poisoned note cannot overwrite what the memory has confirmed. - Forgetting is a feature. Knowledge loses weight over time, with a half-life of about 30 days, unless it is reinforced; every recall hit strengthens it. Provisional knowledge seen fewer than 2 times is removed after 21 days.
- Raw experiences move on. Consolidated experiences go to the archive after 14 days. Non-durable ones are deleted from the live memory after 30 days; what
rememberand/importstore is durable and stays.
What else happens overnight
- Your instructions. In the dashboard you can tell the librarian what to look out for, for example what matters or what to leave out. It reads them every night.
- PII watch. If a name slipped in without a placeholder, the librarian reports it and the memory replaces it with a placeholder in experiences, knowledge and open loops, up to 10 names per night. The briefing tells you when that happened.
The morning briefing
After every night with work there is a briefing, dated by the UTC day. It is built from what the night actually did, not written freely by a model, so it cannot make things up. The headline reads like While you were away: 4 new, 2 reinforced, 1 forgotten from 23 episodes.
- For the agent: new knowledge, open problems, warnings, what needs review and the PII watch note. Read it with
tulimoa__briefing; the headline is also part of the waking state on connect. - For people: the same in more detail, with the numbers of the night, on the
/briefingpage and in the dashboard.
Archive and timeline
The knowledge graph keeps what things mean. When you need what literally happened, tulimoa__timeline reads the raw history, and for ranges older than 14 days it reads the cold archive transparently, up to 62 days per request.