You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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
flowengine 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 themermaidescape 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)
addAnnotationpatch op). S–M. Highest ROI — the engine (feat(sgcr): layered annotation placement + P10 overlap proof #197) is already done.Next tier (not yet filed — capture here)
<<fork>>/<<join>>,[*],<<choice>>). Node-type + an SGCR fanout-alignment rule. M.rank=same/ alignment groups (align:[["a","b","c"]]) — tiny SGCR knob that removes a recurring "off by one slot" class of complaints. S.lifeline/pointnodes (uniform lifeline spacing, monotonic-Y messages, activation boxes, fragments). M.layout:"ring"which is cycle-only). M.architecture-beta). S.change. M.Lower priority / escape-hatch is fine
Sankey (use
vegalite), gitgraph, Gantt (usemermaid/vegalite), fishbone/Ishikawa, value-stream maps, BPMN choreography — distinctive symbol sets, niche; keep on themermaidescape hatch unless demand appears.Already addressed
sgcr-skipped-grouped,sgcr-overflow). Full grouped-graph SGCR support (two-level layout) is still deferred (design in fix(sgcr): warn on grouped silent-fallback + viewport-fit overflow (#195) #196).What's already strong (don't lose in marketing)
ER
entityfield 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.