Skip to main content
Almanac can connect a person’s conversation, accumulated knowledge and live sources, then prepare work with files or a browser. These parts do not share one storage location or one view of the world. Knowing where an action happened helps the agent continue it and describe the result honestly.

​
Saved understanding and continuing work

The personal Almanac is held in a hosted database. Its articles, source locators, tasks, projects and sessions have stable identities and can be read across turns. A task’s session carries the continuing conversation; a project record explains a broader outcome and connects related tasks. Editing a Markdown article body through Almanac changes that hosted record. Changing a similarly named file in a working directory does not. Knowledge and entities explains the records; Tasks and continuing work explains the work they carry. Connected email, calendars and other app objects usually remain with their providers. An account connection lets Almanac read or act on an original with its native identity. A saved source locator can point back to it without storing a copy. Uploaded evidence is a different case: Almanac can keep the original bytes. When a fact matters, follow the source to the representation actually read rather than treating a search result or locator as the whole original. Originals and evidence follows that boundary.

​
The agent’s working environment

The agent may have a terminal, ordinary files and a browser session. In a personal hosted setup, those tools can run in a managed cloud environment. A desktop client can also connect to local, SSH or remote backends. The current session’s tools and workspace determine which computer owns a path, so a generated file or download is not automatically on the person’s laptop. Files used for code, scratch analysis or public research remain ordinary workspace files until deliberately presented or saved into the appropriate Almanac record or source. What the agent can see explains how to inspect the available view and hand a result to the person. Use a supported connected-account operation when one exposes the needed original or action. Some work instead needs an application’s UI, such as sign-in, verification or a step the person must take over; an available browser tool can handle that path. A browser snapshot describes that browser session at the time it was read. It does not reveal the person’s other open tabs. Tool availability varies by session, and desktop pane controls depend on a desktop-sourced session, even when the backend itself is remote. Connected accounts explains discovery and external actions explains uncertain effects. For example, a meeting brief might use a saved person article for relationship history, a fresh email thread for a changed agenda and calendar occurrences for timing. The agent can write a private brief in its working environment, cite the original evidence and leave an available card or file for review. A displayed card is a route for the person to inspect something; it does not mean they opened it, and a prepared brief does not mean it was sent.