Diagram Standard¶

Why This Exists¶

Diagrams make Blueprint relationships easier to understand, especially when describing how Algosure's organizational architecture is reflected in software.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

Consistent diagrams reduce interpretation errors, improve stakeholder alignment, and make enterprise design easier to review.

Diagram Rules¶

Use Mermaid for diagrams where useful.
Keep diagrams focused on one concept or relationship.
Label nodes with business-readable names.
Do not use diagrams to introduce unapproved architecture.
Place source diagrams near the document that explains them unless a shared diagram asset is approved.

Recommended Diagram Types¶

Diagram Type	Use
`flowchart`	Concept relationships, process flows, and operating flows.
`sequenceDiagram`	Interactions over time.
`stateDiagram-v2`	Lifecycle states.
`classDiagram`	Conceptual structure only when approved.

Architecture Mirror Example¶

flowchart LR
    Organization[Organizational Architecture]
    Software[Software Architecture]
    Practices[Practices]
    Capabilities[Business Capabilities]
    Workflows[Executable Workflows]

    Organization --> Practices
    Organization --> Capabilities
    Practices --> Software
    Capabilities --> Software
    Software --> Workflows

Diagram Review Checklist¶

The diagram has one clear purpose.
It uses approved Blueprint terminology.
It supports the text instead of replacing it.
It does not define implementation details that have not been approved.