# The Library

Every key the store holds, as a tree, and a reader that shows each memory with who wrote it.

The Library shows every key that you may read, as a tree of folders. Open a key to read the memory, its writer and its history.

## Find a memory

1. Open **Library**.
2. Open a folder, or type part of a key or a title in **Filter by key or title**.
3. Open a key. The reader shows the memory.

The top folders always show, each with the count of what you may read in it. A folder below them, and `other/`, shows only when you may read something in it. When the tree is too large to show in full, the Library says so. Search still finds every item.

## The folders

| Folder | What it holds |
|---|---|
| `learning/` | one distilled learning each: what was measured or decided, and why |
| `idea/` | ideas, private to their writer by default |
| `config/` | the settings of a group or the company |
| `highlight/` | what the store holds on a project, and how to query it |
| `skills/` | the skills of your organization, see [Skills for your agent](https://mana.scalarmind.com/docs/skills.md) |
| `records/` | the project records |
| `vaults/` | each vault you imported, under its name, with its own folders |
| `other/` | every other key, such as `note/`, at its own path |

[Memory keys](https://mana.scalarmind.com/docs/record-keys.md) says what each key family is for.

**Where an unusual key sits**

A key outside the families sits under `other/` with its folders: `project/mana/plan` sits at `other/project/mana/plan`. A memory with no key sits in `other/` itself. So does a key of one part only, a family name alone such as `highlight`, or a key with an empty part such as `learning//x`.

## The reader

The reader shows a learning as its four lines, and a project record or a `.md` note of a vault as its Markdown. A `.txt` or `.json` file of a vault shows as plain text. It shows a skill with its upstream and the memories bound to it. The reader shows who wrote it, when, how many revisions it has, and whether an agent has used it.

- One line names the revision that this one replaced, with its reason. **History** opens every revision.
- **Ask your assistant about this** takes the key to your agent, as on [Search](https://mana.scalarmind.com/docs/search.md).
- An admin also sees **Delete this memory**. [Your data](https://mana.scalarmind.com/docs/your-data.md#delete-a-memory) says what a deletion does.

## Links between records

A link in the text opens the record that it names, when you may read that record. A link to a record that you may not read shows as its text, as a link to a record that does not exist does.

- In a vault note, a Markdown link such as `[the plan](Plan.md)` or a wikilink such as `[[Plan]]` opens a note of the same vault, as Obsidian finds it. A link to a heading, such as `[[Plan#Goals]]`, opens the note at that heading.
- In a memory, a project record or a skill, a key such as `learning/x` or `[[learning/x]]` opens the record with that key. The Mana rules tell each agent to cite a record as `[[key]]` in what it stores.

**Linked from**, under the text, lists the newest 50 records with a link to this one, and counts them. It lists and counts only the records that you may read. When no record has a link to this one, it does not show.