# The Knowledgebase

> Browse your project's knowledge as a tree or graph, and see the Organizer that keeps its areas current.

Open **Knowledgebase** from a project to see its system map. It brings knowledge entries and plans together under **areas** — parts of your product such as checkout or deployment — rather than leaving you with one long document list.

## Three ways to see it

- **Tree** is the default. Search areas, knowledge, and plans; expand an area on the left and read its chapter or an entry on the right. Entries and open plans not yet assigned to an area appear under Unfiled.
- **Graph** draws areas and documents as connected nodes. Select one to open its reader; pan and zoom to explore the shape, including pinch-to-zoom on a touch screen.
- **Organizer** shows the runs that derive the map. You can start a pass with **Run now** and inspect its progress. It also runs daily when the corpus has changed.

An area's reader has separate **Knowledge** and **Plans** sections. Plans show open work and shipped history, so you can follow the work alongside the system it concerns. Knowledge entry keys follow their titles; area identities are preserved where the underlying topic still fits.

## An area is a chapter, not a folder

A folder holds things. An area explains them. Each one carries:

| Part | What it gives you |
| ---- | ----------------- |
| **Name** | The subsystem as your team would say it out loud. |
| **Description** | What the subsystem covers, and where its edges are. |
| **Covered paths** | The repo paths the area maps to, so a claim has an address. |
| **Members** | The knowledge entries and [plans](https://darting.dev/docs/plans-and-build/) filed under it. |

Opening an area gives you its chapter, its sub-areas, and the entries and plans filed there — not just a directory listing.

## The Organizer rebuilds the map

The **Organizer** is a [built-in automation](https://darting.dev/docs/built-in-automations/). A pass summarizes documents, embeds them, rebuilds the areas around their meaning, and curates changed topics. Related entries form leaf areas; related areas can group under parents. A matching area keeps its identity; an empty one can retire. New topics receive names and descriptions, and chapters are written over the resulting tree.

Within a topic, identical entries can fold into one. Related facets of a topic become merge proposals for your review; contradictions are flagged, not decided by the model. Plans remain separate work items unless they are truly identical. You can review proposals beside their area in the Knowledgebase and in the [Inbox](https://darting.dev/docs/inbox-and-proposals/).

## Agents navigate the same map

An agent begins with a small manifest of area names and what they cover, not every document body. It can search for the fact it needs, open an area's chapter and index of sub-areas, entries, and plans, then read the relevant document in full. Entries not yet filed under an area remain searchable. [Structured memory](https://darting.dev/docs/structured-memory/) explains why this keeps context lean.

The same area taxonomy files knowledge, rules, and plans and classifies work threads. That lets you connect the explanation of a system with the plans and threads working on it.