dayan-diagramlisted

# 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 1. Write the one question the diagram must answer. 2. Select the smallest fitting grammar: architecture, flow, sequence, hierarchy, timeline, state machine, data flow, comparison matrix, or decision tree. 3. Limit nodes to meaningful concepts, label every edge, and make direction unambiguous. 4. Produce editable SVG with a title, description, stable IDs, readable text, sufficient contrast, and no clipped labels. 5. 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.