Aggiunto zoom immagini (click to enlarge) con mkdocs-glightbox

docs/will-executors/running-a-server.md

@@ -20,6 +20,14 @@ This page covers setting up your own Will-Executor node. If you are wondering *w
 
     Two things to keep in mind: for a user's redundancy, a consortium still counts as **one** Will-Executor; and the internal split is an agreement outside the protocol, which BAL neither arbitrates nor guarantees.
 
+See the [architecture diagram](../protocol/how-it-works.md#architecture-at-a-glance) for how
+`bal-server` and `bal-pusher` fit into the full flow from plugin to Bitcoin node.
+
+## Architecture at a glance
+
+![BAL architecture: plugin, Will-Executor, Bitcoin Core](../img/architecture.svg){ .diagram }
+*How a will travels from the Electrum plugin to the Bitcoin network. Click to enlarge.*
+
 ## The two components
 
 | Component | Role |

docs/will-executors/what-they-are.md

@@ -11,6 +11,10 @@ A Will-Executor is a server with one narrow job: **it stores pre-signed inherita
 
 What it *does* require is longevity: being still there, still working, years from now.
 
+!!! info "See the whole flow"
+    The [architecture diagram](../protocol/how-it-works.md#architecture-at-a-glance) shows how a
+    will travels from the Electrum plugin, through a Will-Executor, to the Bitcoin network.
+
 ## Why competition makes it work
 
 When you create your will, the plugin generates **a separate transaction for every Will-Executor you selected**. Each of those transactions carries an extra output paying that specific server its fee.