EditorialDiagramSoftware Engineering
Editorial Architecture Delta Diagram Designer — No Shadows, No Mermaid Slop
Explain a system change using synchronized Before, Changes and After panels. The ten-node example replaces a direct dispatcher with a durable queue while retaining storefront, worker and storage identities.
Take it with you
Free PNG includes an EditorialDiagram watermark.
Layout Grammar & Anti-Patterns
Four rules for this diagram
- 01
Use exactly two topology snapshots with a change ledger between them. Both snapshots have the same dimensions, grid pitch and vertical origin.
- 02
Copy retained components into the same local coordinates. Move them only when a MOVED ledger entry is part of the actual story.
- 03
Keep stable component and relationship IDs. CHANGED describes a semantic signature edit; REWIRED describes a change to ordered edge endpoints.
- 04
Make ADDED, REMOVED and CHANGED readable with text and shape or dash treatments. Draw identified relationship paths before components.
Three mistakes to avoid
- Independent auto-layouts imply movement even when the system did not move.
- A ledger that only says “updated” conceals which object changed and how.
- Treating two snapshots as a deployment sequence invents timing, causality or rollback guarantees.
Engineer vs. Executive
The two renders use the same illustrative source. Executive mode groups detail deliberately; read the captions before using an overview for a technical review.
Ten snapshot nodes represent six stable component identities; six ledger entries cover semantic and endpoint changes.
Six snapshot nodes summarize intake and fulfillment capabilities while preserving the before/after comparison.
When to use another diagram instead
System Architecture Diagram
Use a single architecture when there is only one state to explain.
Sequence Diagram
Use a sequence when the change concerns request timing or protocol order, rather than topology identity.
Gantt Chart
Use a Gantt chart for dated implementation phases, overlap and the migration schedule.
Questions about this diagram
Why do retained components stay in the same place?
A delta uses spatial stability to distinguish real changes from drawing changes. The example keeps storefront, API, worker and store coordinates synchronized. A position change needs an explicit MOVED claim, otherwise the reader could mistake re-layout for a system migration.
What is the difference between CHANGED and REWIRED?
CHANGED means the same object has different semantics, such as the orders API switching from direct dispatch to enqueue. REWIRED means the same relationship now has a different source or target, such as submission moving from the legacy dispatcher to the queue. A relationship can have both changes when both facts are true.
Does the delta prove that the queue migration is safe to deploy?
No. It explains two topology states and their declared differences. Deployment order, rollback, availability and data consistency require a separate plan. Use Engineer mode to inspect the six-entry component and edge ledger, and a dated schedule for implementation sequencing.
Worked examples use illustrative data. Edited sources require an AI provider; cached previews are ready immediately.
Cached examples are free. Starter Pack is $9.9 once; Pro Pass is $8.9 per month. Every generation costs 10 credits, including one automatic geometry repair. Pricing