Skip to main content
Almanac keeps durable understanding in articles about recognizable subjects. A person, organisation, place, event, creative work, topic or general page can each have prose, structured facts and links to related records. The article’s identity stays stable as its account of the subject changes. Sam’s person article might explain how they know the user, what they worked on together and why a meeting with them matters. Its structured roles can refer to a Meridian Labs organisation record, whose own article carries Meridian’s history and people. The prose connects those facts into an account a reader can understand. A mention of Meridian in a sentence gives the reader a route to follow; a structured organisation reference identifies the relationship for the rest of Almanac. Both can be useful, and they do different work. A record has a stable ID and a readable path. The path is an address in the hosted Almanac, not a file on the agent’s computer. Its revision lets an editor notice when someone else has changed the record since it was read. A person can add a note of their own in user_notes; that annotation belongs to them, and the agent does not edit it. Writing and tending pages explains how an agent updates the shared article body and fields without overwriting other work. The seven kinds give recurring subjects a fitting shape. A place can connect a location to other places; an event can retain understanding about a meaningful occasion and its participants; a creative work can connect a book, film or other work to its creators and original source. A topic is an article about a subject that crosses several people or events. It need not be a folder or a label attached to every page. A general page can hold lasting understanding that does not fit a more specific kind. Current schemas define the available fields and references; a title alone does not establish which record kind to use. These articles are selective. A calendar occurrence remains in the calendar unless there is something about that event worth maintaining as knowledge. An email thread remains an original conversation in its connected account; it does not become a person or page merely because it names one. Originals and evidence explains how an article can cite either original without copying it. Why Almanac has a wiki explains what the maintained article adds to those originals. Knowledge also differs from open work. Sam’s article may say that a Meridian briefing is planned, but the briefing’s outcome and state belong to a task. A project can hold the broader purpose and decisions; its linked tasks hold their individual status. That separation lets a reader learn the relationship from the article and then find the work that still needs doing. Tasks and continuing work follows the conversation into a tracked outcome.