Skip to main content
Begin with a question about something the person has saved. Root search finds maintained knowledge and work; it does not search their live email or every past message. If you need an original, go directly to email, conversations, or public research. A managed Almanac agent already has its identity. For a local installation that has not been connected, complete local setup first.

​
Find and read a record

Search returns summaries. Choose an actual returned ID or path and read the full record. Here people/sam is a fictional example, not a built-in record:
The complete record includes its body, structured fields, citations and revision. That revision tells you which state you inspected. If the search is empty, the workspace may simply have no saved person matching Sam. You can browse existing people with almanac list --type person --limit 5; do not invent a record or identity to make the example work.

​
Make an informed change

Suppose the requested change is a better description. Inspect the person’s schema, then compose the new description from supported information:
For a record you actually read at revision 3, this illustrates a field edit:
Use the real returned revision and a new request key for your actual decision. The example is not permission to change a person’s data or evidence that Sam works there. New factual claims need sources and citations. Editing records covers body patches, preserving collections, and revision conflicts. After a successful write, inspect the returned record and read it again when needed to confirm the intended state. Saving knowledge is different from sending an email or starting agent work; Almanac’s object model explains those boundaries.