d2-diagramslisted

# D2 diagrams Use D2 when fixed layout, repeatable exports or publication quality justify maintaining source plus a rendered asset. The project's diagram conventions, source/render owners and terminology are authoritative. Where the project is silent, prefer native Mermaid for GitHub READMEs and living operational docs. Simplify or split an overloaded Mermaid graph before converting it; a tool change cannot fix mixed conceptual levels. A review or validation request is read-only unless edits or exports are explicitly authorised. ## Publication figures (anything in a written document) For a paper, thesis, report or manuscript: 1. Match labels to the intended reader. Use implementation names only when exact reproducibility is the figure's purpose. 2. Match the target venue's output requirements. D2's native PDF path is PNG-derived; when vector shapes/text are required, render SVG and use a project-approved converter, then inspect the PDF. Read [publication-figures.md](references/publication-figures.md) before editing a publication figure. ## Where To Put Things - Use the project's diagram directory and naming convention when writes are authorised; otherwise use an assigned run-owned temporary path. - Export only when requested or required by the authorised workflow. - Never overwrite unrelated Mermaid or Structurizr artefacts. ## Default Workflow 1. Choose the reader question and diagram type. 2. Draft concise labels and stable identifiers. 3. For authorised