> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usealmanac.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This handbook preview targets personal CLI 0.11.1. Check installed command help and the matching backend schema before using examples with another release. Examples with named people and placeholder IDs are fictional.

# Why Almanac has a wiki

> A conversation records what was said, and a connected account keeps the original emails, meetings and documents.

A conversation records what was said, and a connected account keeps the original emails, meetings and documents. Almanac's wiki maintains an account of what those records mean for a person's life and work. Its articles connect people, organizations, projects and subjects, with citations that let a later reader return to the evidence.

Imagine that Sam writes to say they have joined Meridian Labs. The email is the original statement, made at a particular time in a particular thread. A person article can incorporate the change into what Almanac knows about Sam, while keeping an earlier role in the history instead of erasing it. A source locator connects the claim to the thread in the authorized account. It gives the reader a way back to the original; it is not a copied email or proof that the thread can always be opened later. [Originals and evidence](/almanac/originals-and-evidence) explains that chain.

The article does more than preserve the announcement. It can put Sam's new role alongside the relationship with the person who uses Almanac, the Meridian project, and relevant earlier conversations. A future meeting brief then has a starting point that the person does not have to retell. The agent can follow links to the organization or project when those subjects have their own history. It need not read every old email to rediscover a connection that has already been explained. When the answer depends on what Sam said exactly, or on a fact that may have changed, the agent returns to the original. [Knowledge and entities](/almanac/knowledge-and-entities) describes the kinds of article and relationship available for that work.

An article gives a subject a stable home. Coverage depends on the active assignment: [Dream](/almanac/background-work) calls for pages accounting for the user and every discovered person and organization, while an ordinary chat need not become a comprehensive research sweep. A person or organization often does, because names, roles and relationships recur across conversations. A topic can explain a lasting subject that would otherwise be scattered across several records. It is an article, rather than a required label for every page. A single email, an imported file or a routine calendar occurrence usually remains an original to read or cite. Almanac can make a wiki event when an event deserves maintained understanding; the calendar entry does not automatically become one.

The wiki changes as understanding changes. If Sam later writes that the Meridian role ended, the older email still supports the historical claim. The person article needs a new account of the present, supported by the later message. A missing connection to the email may limit what Almanac can verify now; it does not make the previous source record a new authority about Sam's current job. Dream and Shadow maintain knowledge over different time horizons, but their saved pages remain subject to correction and to evidence that appears later. [Writing and tending pages](/almanac/writing-and-tending-pages) covers how to revise an article without discarding supported history.

This is also why the wiki has links and a small front door. A reader looking at the Meridian project may need Sam's relationship history; someone reading Sam's page may want the project decisions. Those are useful movements between subjects, not a reason to create a page for every named noun. The front door should introduce the person's world once there is meaningful knowledge to explore. Tasks still own actionable outcomes and status, while the wiki explains the people and circumstances around them. [Tasks and continuing work](/almanac/tasks) describes how that understanding becomes work when there is an outcome to carry forward.