Diagram Standards

Different organizations draw architecture differently, and consistency across packages matters more than any single default. Diagram standards are organization-level rendering rules: set once in Settings, applied to every package's views.

What You Can Standardize

• Element classification: override how a capability renders (for example, always drawing your ESB as a queue, or a particular platform as external), when the default reading does not match your house convention.
• Trust-zone assignment: pin specific capabilities to the zone your security model places them in.
• House style: naming and presentation conventions, applied uniformly.

Rendering Only, Never Meaning

Standards change how designs are drawn, not what they are. Compliance results, gap decisions, approval, drift: none of them read the diagram standard; they read the design. A rendering override can therefore never hide a gap, move a component out of scope, or change a control outcome.

Standardize When You See the Same Correction Twice

The defaults are good for most designs. The moment you find yourself making the same visual correction on a second package, promote it to a standard so every future package (and every future reviewer) gets it for free.