Two layers, in order

Layer one: establish the baseline

The first release implements 32 familiar forms across seven families. It includes five rendering primitives, shared controls, individual recipe references, editable JSON, SVG export, and local review history.

The next work in this layer is calibration: inspect the examples in real documentation pages, record timed editing tasks, and revise scores from those observations. The initial totals are provisional editorial estimates.

Coverage to extend

The catalog is finite. Familiar forms not yet implemented include Sankey diagrams, treemaps, scatterplots, network chord diagrams, C4-specific notation, UML class diagrams, BPMN, packet layouts, and circuit diagrams. Some require data-aware layout or notation rules that the current coordinate-based renderer does not provide.

Treat these as candidate coverage, not working examples. Add each only with a rendered recipe, clear usage limits, and a documented review.

Editing improvements

• Parameterized layout recipes so adding a node can recompute related positions.
• Data inputs for charts, separate from their SVG geometry.
• Importable review bundles and human-calibrated scoring worksheets.
• Browser regression screenshots committed with recipe revisions.
• A distributable library package once the schema has survived real use.

Layer two: original diagram exploration

This phase begins after reviewing the familiar baseline. Start from an explanation that the existing forms handle poorly. Use the user’s brief and original construction, without browsing galleries or external visual references for ideas.

For each experiment, record the question it answers, why a familiar form falls short, which primitives it reuses, the reading rule, and the expected editing operation. Keep it in an experimental collection until people can read and modify it without additional coaching.

No original diagram forms have been added to this release. The distinction keeps the baseline useful as a reference for what we already know how to generate.

Platform boundaries

The current site is static. It has no account system, backend storage, live AI generation, executable terminal, or collaborative editor. You can use the hosted site, fork the public MIT-licensed repository, or deploy your own copy. Review storage remains local to each browser.