`api_abstraction_map`

Draw the program's abstraction ladder: every definition placed at its abstraction height (layer 0 = built only from builtins; each layer composes the ones below), with reuse (fan-in), width (direct dependencies), mass (size: node count of the compiled definition), duplication (shape-isomorphic blocks repeated inside a definition, and copy-paste clone pairs across definitions), and layer-skipping edges measured. Every visual quantity is a defined function of the source's dependency graph and the layout is deterministic, so you can inspect reuse and layer crossings. The layout does not score organization or establish that one graph shape is best. On the browser MCP page this tool also renders the map for the user, so sending sources here changes what they see.

Kind: AbstractionMap. Origin: Yichus/Mcp::catalog.

CLI: yichus organize map — the same abstraction map, the CLI's map lens.

Parameters

sources (required, array) — JSON array of {fileName, source} Bosatsu files for the module.

Read the result according to this tool’s scope: static checks, bounded execution checks, and descriptive diagrams answer different questions. A successful call is not a general approval of the program. The safety and permissions guide compares the checks and provides editable ownership, guard, and role examples.