mellos-mapping

# Mellos Mapping — the map discipline Four MCP tools (`mmap_declare`, `mmap_update`, `mmap_remove`, `mmap_view`) maintain a **Mellos map**: a layered dependency map of the system under construction, persisted in `.claude/mellos-mapping.json` and rendered live in a terminal split pane beside the conversation. The map is a **ledger, not a judge**: the tools only refuse structural corruption; *when* to declare, start, or complete nodes is YOUR discipline, spelled out here. Report honestly — an unflattering map is doing its job. ## When to open a map Open a map for work with real structure: several interacting modules, a new subsystem, layered refactoring. Skip it for trivial edits — a map of one node is noise. When unsure, ask. Caught mid-implementation without a map on work that deserves one? Stop and declare it with honest statuses (written-but-unverified is `in-progress`, not `done`). If the mmap tools are missing from the session, SAY SO and offer a restart — never silently skip the map. (Under Codex CLI, missing tools usually mean the server was never registered: have the user run `node <plugin root>/scripts/codex-register.mjs`.) ## The working loop 1. **Design first, as ghosts.** Before writing code, decompose bottom-up and declare the WHOLE intended design in one `mmap_declare` batch: `title`, layer bands (rank 0 = most primitive, at the bottom), every planned node, and the edges. Everything starts `planned` — the user can veto the ghost design before a...