Show an engineer a box-and-arrow diagram labelled “System Architecture” and they will nod and say it looks reasonable. Show them five specific diagrams — each asking a different question about the same system — and they will find at least two problems the first diagram hid.
The five architecture diagrams are not different ways to draw the same picture. They are five different questions, each of which is only visible from a specific angle. The request flow diagram shows latency. The data storage diagram shows consistency. The event-driven diagram shows asynchronous coupling. The data pipeline diagram shows freshness and correctness. The distributed coordination diagram shows failure modes in consensus.
You can have all five questions answered by a single static diagram only if you are willing to make it so complex that nobody can read it. Use five diagrams. Keep each simple and focused on its question.
Every architecture diagram you have ever drawn is probably one of these five — you may not have known it had a name, but the intent was always to answer one specific question. Naming the diagram type makes the question explicit.