[MERMAID_DIAGRAMMING]

Every committed diagram answers one written question, instantiates one catalog archetype or admitted type, carries only structural payload — declaration, nodes, edges, labels, subgraphs, accessibility directives, functional layout keys — and ships only after the validator and the soundness audit pass. Reasoning discipline and engine surface load on demand through the reference routes below.

[01]-[ROUTING]

• [01]-METHODOLOGY: admission, investigation, node/edge law, type selection, soundness audit, multi-diagram composition
• [02]-CONSTRUCTION: per-type — each type's question, what its marks assert, failure modes, truth tests
• [03]-GRAMMAR: link/arrow forms, link lengths, shape registry, containers, subgraphs, structural traps
• [04]-CONFIG: frontmatter schema, secure keys, layout engines, ELK tuning, accessibility, mmdc and CI, traps
• [05]-SYNTAX_CORE: flowchart, sequence, state, class, ER — node metadata, edge IDs, markdown strings, KaTeX, traps
• [06]-SYNTAX_EXTENDED: beyond the core five — admitted rows with working fences and traps, registered rows named
• [07]-CONCEPT_MAP: shape in code, prose, plans, arguments: signals, archetype routes, misfit shapes, composites
• [08]-EMBEDDING: fence law in markdown hosts, inline-SVG law in single-file HTML, export surfaces, source-beside-render
• [09]-THEMING: optional appearance system — palette, classDef canon, per-family routes; loads only for a styled render

[02]-[QUESTION]

A diagram earns its fence only when the reader traces a relation across more marks than a clause holds: three or more nodes with at least one branch, cycle, or crossing relation. Below that, prose owns the fact; one diagram owns one question, and a diagram needing two legends is two diagrams. Authoring discipline is references/methodology.md, per-type mark law references/construction.md; raw material with no written question resolves its shape through references/concept-mapping.md.