describelisted

# Describe the work in the wiki Read [provenance.md](../wiki/references/provenance.md). Tools: `status`, `stage`, `capture`, `route`, `plan`, `apply` on the atlas MCP server. The work sits beside the project's folder: a repository, or documents. The wiki holds a map of it that 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. ## What is about to happen 1. Call `status`. It says whether a page describes the work (`described`, with `page`, `commit`, and `behind`). 2. A page that does not exist is written; one whose `behind` is above zero is updated. Say which, in one line, before you stage. ## Stage and capture 1. `stage` with `snapshot: true`. The core writes `inbox/<name>-<short commit>.md`, or `<name>-<date>.md` for a folder that is not a repository: the work's AGENTS.md, CLAUDE.md, and README verbatim in fenced blocks, the files (folders only past 2000), the first heading of every markdown file under `docs/`, and, when a page already describes the project, `git log --stat` from that page's commit to HEAD. The result says whether the snapshot is new or already waits. 2. `capture` the snapshot with its inbox path. Read the captured copy, not the inbox file. ## Read