describelisted

# Describe a project in the knowledge base Read [provenance.md](../wiki/references/provenance.md). Tools: `status`, `stage`, `capture`, `route`, `plan`, `apply` on the atlas MCP server. A project's work lives in its own folder, a repository or documents. The knowledge base holds a map of it that other projects and later sessions can read: what it is for, how to build and test it, its layout at the level that changes slowly, what it has delivered, the concepts it introduces, and where to look for what. A snapshot the core writes is the source that map cites, so every claim points at a commit through the ledger when the work is a repository. The skill runs in a project session, for this project, or in a knowledge base session, for any project that uses it; pass `project` to `stage` there. ## Which project 1. Call `status`. In a project session it says whether a page describes the project (`described`, with `page`, `commit`, and `behind`). In a knowledge base session it lists every project and whether each is described. 2. Take the project the user names. With none named in a knowledge base session, take every one that is not described, and say which; when all are described, take those whose `behind` is above zero and offer the update. 3. Say what is about to happen in one line per project: new page or update. ## Stage and capture 1. `stage` with no paths (and `project` in a knowledge base session). The core writes `inbox/<name>-<short commit>.md`, or `<