Insert drawings and diagrams

I need to include an architecture diagram in the product spec. Insert a new drawing into the document, recreate the network diagram we used in the July spec (three services, two databases, load balancer), label each component, and place the diagram just under the ‘Technical architecture’ heading. Make sure the diagram can be exported as PNG for the engineering board. Ladder L1

Before I embed the diagram, make it review-friendly: separate it into layers (frontend, backend, data), add numbered callouts for the three components that changed since the July spec, include a tiny legend explaining each symbol, and attach a short caption that explains the single risk a reviewer should care about. Ladder L2

I drew the system layout but the engineers disagree which database is authoritative and that argument could derail approval. I’m worried labeling one as primary will start a technical debate. What’s the likely consequence of labeling one as authoritative versus leaving it ambiguous, and what’s the best next move to get the spec past reviewers without sparking a huge rewrite? Ladder L5

In every spec the diagram gets reworked three times during review and each change forces another round of edits in the text. We lose clarity and approval slips. What habit change stops this churn — locking the diagram before text freeze, a single diagram owner, or embedding a change log — and which approach reduces rework fastest for a small engineering team? Ladder L6