Guide/Annexes
Annex C: Diagram style
Every diagram in the docs follows one style, the "EterShield Diagram": Apfel Grotezk, white nodes with a thin border, a single teal highlight. This page shows the four types and the rules.
Rules
- About 12 nodes at most per diagram. Beyond that, split it in two.
- Short labels, no trailing punctuation. Technical terms (Evidence, Gap, finding) stay as in the application.
- Decisions with two exits are always labelled "Yes" and "No".
- A single highlighted node, the one the reader must remember. Main arrows in teal.
- Never emojis, not even inside diagrams. Never orange or shadows.
- Every diagram has a short caption underneath.
- Hierarchy trees are drawn with a shared trunk and no arrowheads.
Flowchart
For processes with decisions and deadlines. Start and end as pills, decisions as diamonds with "Yes" and "No" on the arrows, steps as rounded rectangles.
Sequence diagram
For exchanges between people and systems over time. Solid arrows for requests, dashed arrows for replies.
Hierarchy tree
For structure and dependency: modules, roles, frameworks. Groups in light grey, the root highlighted.
- EterShield
- Governance and risk
- Risks
- Policies
- Operations
- Incidents
- Assets
- Compliance
- Frameworks
- Reports
- Governance and risk
State diagram
For the lifecycle of an object: policy, incident, finding. One state per box, the transition says what causes it.