Diagramming processes REQUIRED BACKGROUND: the skill (hard rules, truth rules, style). Overview A diagram is a set of claims drawn instead of written; every box and arrow is bound by the same truth rules as a sentence. Core principle: diagram the behavior (processes, lifecycles, interactions), keep the source in version control, and treat every render as derived. The prose owns the reasoning; the diagram carries what prose serializes badly: branching, concurrency, and state. When to invoke, and not Invoke when a flow, lifecycle, or interaction needs showing: a business process spanning compon…