| name | dayan-diagram |
| description | Turn topology, flow, hierarchy, sequence, or branching logic into a focused, editable, accessible SVG diagram. |
Dayan Diagram
Use a diagram only when the relationship itself is the information. Prefer prose for a single fact and a table for independent key-value comparisons.
Workflow
- Write the one question the diagram must answer.
- Select the smallest fitting grammar: architecture, flow, sequence, hierarchy, timeline, state machine, data flow, comparison matrix, or decision tree.
- Limit nodes to meaningful concepts, label every edge, and make direction unambiguous.
- Produce editable SVG with a title, description, stable IDs, readable text, sufficient contrast, and no clipped labels.
- Verify at target size, grayscale, and 200% zoom. Provide a text alternative for the core relationship.
Do not encode meaning by color alone or use decorative complexity to imply system maturity.