Skip to content

[epic] Native flowchart parity — gaps vs Mermaid/BPMN/UML/ER (external survey) #204

Description

@ivanmkc

Native flowchart parity — gaps vs Mermaid / BPMN / UML / ER / Graphviz

Audit of external flowchart tools (Mermaid, PlantUML, BPMN 2.0, UML, Graphviz, draw.io/Lucidchart, plus VSM/fishbone/mindmap/C4) vs. what the termchart flow engine can render natively today. Goal: decide what should be native flow (so agents emit it and inherit our layout/tones/SGCR proofs) vs. left to the mermaid escape hatch (which bypasses all of that).

Framing: distinguish viewer can't render it (node shapes, markers, glyphs) from SGCR can't lay it out (dagre often still handles it). Most gaps below are viewer gaps.

Prioritized, actionable (filed)

Next tier (not yet filed — capture here)

  • Fork/join bars + composite/nested states — unlocks native UML activity + state-machine (<<fork>>/<<join>>, [*], <<choice>>). Node-type + an SGCR fanout-alignment rule. M.
  • C4 conventions + cloud-icon pack (AWS/GCP/Azure/K8s/iconify) — mostly a tone/icon/recipe pack; "architecture" is the most-requested family after "flowchart". M.
  • Off-page / on-page connector primitive + auto-suggest lint — paired circle/pentagon nodes; lint suggests a connector when SGCR routes a long crossing or dagre wraps wide. S.
  • rank=same / alignment groups (align:[["a","b","c"]]) — tiny SGCR knob that removes a recurring "off by one slot" class of complaints. S.
  • Sequence-diagram auto-layout for the existing lifeline/point nodes (uniform lifeline spacing, monotonic-Y messages, activation boxes, fragments). M.
  • Radial mindmap layout (center-out branching tree; distinct from SGCR layout:"ring" which is cycle-only). M.
  • Junction node (small dot, 4-way edge merge — Mermaid architecture-beta). S.
  • Graphviz HTML-like / record labels, icon-pack registry for change. M.

Lower priority / escape-hatch is fine

Sankey (use vegalite), gitgraph, Gantt (use mermaid/vegalite), fishbone/Ishikawa, value-stream maps, BPMN choreography — distinctive symbol sets, niche; keep on the mermaid escape hatch unless demand appears.

Already addressed

What's already strong (don't lose in marketing)

ER entity field tables, status tones + colorblind glyphs, sparklines, swimlanes (flat), all 4 directions, and provable overlap-free layout + crossing minimization (SGCR, P1–P10) — verified by a 40k-layout stress harness (#199).

Source: external survey across Mermaid/PlantUML/BPMN/UML/ER/Graphviz/draw.io/Lucidchart docs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions