Declare map structure
mmap_declareDeclare or grow a layered map by setting its title, diagram kind, layers, lanes, groups, nodes, and downward edges in a single all-or-nothing batch.
Instructions
Grow the Mellos map: set the title and diagram kind, add layer bands, lanes and groups (labeled subsystems within a band — the zoomed-out view renders groups, so declare them for any map beyond a handful of nodes), add nodes, add dependency edges. Declare the whole ghost design up front, then grow it as understanding deepens. Edges must point strictly downward (a node may only use nodes on lower layers); the batch is all-or-nothing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | diagram kind. dev (default) = the live progress ledger with status skins. The rest are documentation diagrams rendered neutrally: architecture (layered components; also fits call graphs and module dependencies), dataflow (source→transform→sink, stages as layers), behavior-tree (root on top, leaves at the bottom; also fits mind maps and WBS), sequence (classic call/return: rank = time step with rank 0 = EARLIEST, drawn top-down; declare lanes as participants and make every call AND every return its own event node in the acting participant's lane, edges labeled with the message). State machines are unsupported: cycles cannot enter a Mellos map. | |
| page | No | page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other and the pane can switch between pages. | |
| edges | No | ||
| lanes | No | vertical columns crossing all bands; declaration order = left-to-right | |
| nodes | No | ||
| title | No | map title, e.g. the feature being built | |
| groups | No | ||
| layers | No |