Skip to main content
Almanac compiles context from a person’s conversations, connected accounts and work into understanding that carries forward. People, preferences, decisions and projects become connected rather than having to be explained again for each request. That understanding helps the agent do relevant work and keep track of what matters. This wiki explains the product, how Almanac works with a person, and the practical interfaces it uses. The CLI is an internal way to act on that world; it is not the organizing idea of the product. Read the subject relevant to the task. You do not need to load this entire manual before using Almanac. Command help and live schemas supply exact options; these pages explain the choices, handoffs and consequences behind them.

​
Find the right starting point

​
A connected example

Suppose Sam emails that they joined Meridian Labs. The email remains in the connected account. Almanac can retain a source locator for that thread, update Sam’s person record with a cited explanation, and associate a follow-up task with Sam and a project. These are related objects with different responsibilities; copying the email into every object would lose that distinction. The evidence chapter follows that handoff. The editing chapter explains how to preserve the record’s existing understanding while changing it. The work chapter explains how the follow-up keeps its conversation. Examples involving Sam, Northstar, Meridian and Atlas are fictional. Returned IDs, revisions and resource handles must come from your own results.