Diagram and report
Node types, auto-layout, satellites and the editor beside them.
The diagram is a work surface, not a picture. Nodes can be moved, renamed, added and deleted; edges can be redrawn and labelled. Auto-layout arranges the process left to right so the reading order stays legible.
Node types
| Type | Meaning |
|---|---|
| Start / end | Trigger and completion of the process. |
| Step | An activity with actor, system, inputs and outputs. |
| Decision | A branch. Its exits carry the condition as an edge label. |
| Document / file | An artefact on the process. Files take real attachments. |
| Note | A remark on the side, outside the control flow. |
Documents, files and notes are satellites: they hang off a step instead of standing in the chain. That is the difference between “a document belongs to this step” and “opening the document is the next step” — and it is enforced automatically when the diagram is built.
The report beside it
Beside the diagram sits the report in a full editor. Headings, lists and tables behave the way you expect; it saves as Markdown. A fresh analysis never overwrites your edits — it appears as an offer, and you decide whether to rebuild the diagram.