A process as steps joined by arrows.
A flowchart whose steps are divided into lanes, one per actor.
The steps an AI agent takes to do a task.
The states something can be in, and the events between them.
A program's classes and how they are related.
What a database records, and how its entities are related.
A system's requirements and what meets or tests them.
The actors that use a system, and what they can do with it.
A C4 diagram of a software system, at a level it does not name.
A C4 diagram of a system among the people and systems around it.
A C4 diagram of the containers inside a system.
A C4 diagram of the components inside a container.
A C4 diagram of how its parts work together, step by step.
A C4 diagram of where a system's containers run.
A system's parts as blocks in rows and columns.
The services a system is made of, and their connections.
A repository's commits, on their branches.
How information moves through a system, as screens, commands and events.
Ideas branching out from one central topic.
Work as cards in columns, one per stage.
A hierarchy as an indented list, such as a project's files.
The causes of a problem, grouped into categories: a fishbone diagram.
Events along a line of time.
The rules of a grammar as tracks: a syntax diagram.
Situations sorted into domains by how clearly cause and effect show.
Items on two scales, in four quadrants.
The tasks a person goes through, and how satisfied they are at each.
The layout of a block of data as fields of bits.
A user need's components by visibility and evolution.
A diagram MAIDR names and explains in the reader's language, though no layer type of its own reads it: each is read as a layer type that navigates it, as a flowchart is read as a
directed_graphand a kanban board as atree. See MaidrLayer.diagramType.