> ## Documentation Index > Fetch the complete documentation index at: https://docs.alicein.xyz/llms.txt > Use this file to discover all available pages before exploring further. # The knowledge view > Read everything your project knows, and follow how one record led to another. Open it from the **Knowledge** mark next to **Search**, in the legend row at the top right of the workspace. This is the written record: what the project knows, and how each record connects to the others. Search here by text or by record ID. `/` or `Ctrl`/`⌘`+`K` finds a *card or enabler* on the map — that is a different search. ## What is in it Down the left, knowledge by kind, each with a live count: | | | | - | - | | **Standing** | What the project *is* — identity, positioning, voice. The documents your agents read to understand you. | | **Knowledge** | What you have learned: research, analyses, runbooks. | | **Decisions** | Every call made, with its reasoning. | | **Plans** | Design documents for work you intend to do. | | **Lessons** | Rules the project taught your agents, each citing the event that taught it. | | **Attached notes** | Short notes bound to a specific file, module or card — see [Memory](/concepts/memory). | | **Proposals** | Changes an agent has put to you. | | **Activity** | What happened: work done, deliveries, questions. Git commit rows stay out unless you ask for them. | | **Subjects** | The parts of your system things are recorded against. | | **Work** | Your cards and enablers, as records with links rather than as a board. | **Hide commit events** sits on the list and on a record's connections. It is on by default, so Activity is the notes and decisions, not one row per git commit. Turn it off when you want those commit records in the list and in the links. A search for the word "commit" still finds notes that mention a commit. That is not the git log. ## Reading a record Every record opens on three tabs. * **Connections** — what it points to on the left, what points to it on the right, with the relationship named on each link: *evidence*, *corrects*, *supersedes*, *about*. Filter to one relationship when the list gets busy. Select any neighbour to walk to it, and a trail of crumbs lets you walk back. * **Original record** — the record itself, as it was written. Nothing rewritten, nothing summarised. * **What changed** — the corrections, replacements and promotions recorded against it, oldest first. This is the chain of how your project's thinking moved. If a correction exists, the record says so at the top before you read a word of it. An empty "what changed" tab does not mean a record is current — it means nothing has been recorded against it, which is a different claim, and the page says that too. ## The connection atlas Behind the atlas button: a grid of every kind against every other, showing how many recorded links run between them. Darker means more; blank means none recorded. It answers the question you cannot answer by reading records one at a time — do our decisions actually cite evidence, or do they float? Select any square to read the individual links behind the number. A blank square means no explicit link was recorded. It does not mean the two are unrelated. ## Editing your standing documents Standing documents are the ones you can edit here directly, because they are yours rather than the record's. Open one, press **Edit document**, and you get a review screen showing the saved version beside your new one before anything is written. The checkbox on the editor decides whether the document rides in *every* agent session or is fetched only when needed. The **overview** document is asserted to every agent, in every session, with full confidence, until someone changes it. Keep it to what is true and stable. Anything that can be counted or that moves on its own should not be in there — the system computes those, and a stale sentence here is worse than a missing one. The version from immediately before each save is kept, so one save is undoable. ## It updates while you read The view refreshes itself every few seconds, so an import or an agent session running in another window fills it in front of you. A draft you are part-way through editing is never clobbered by a refresh. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.