nvaf-architecture-diagrams

NVAF Architecture Diagrams

Apply the NVIDIA Cloud Architecture Diagrams Style Guide to NVAF figures while preserving the technical meaning requested by the user.

Sources of truth

Use this precedence:

1. The user's explicit content and deliverable requirements.
2. NVIDIA Cloud Architecture Diagrams Style Guide v1.1.
3. Repository conventions in docs/AGENTS.md.
4. Existing figures as implementation references.

Before editing, read the style-guide summary and the provenance file for the relevant assets. For the turn-orchestration figure, read its asset map. Treat nvaf-turn-orchestration.svg as a layout and validation example, not authority when it conflicts with the style guide.

Authoring contract

• Use this visual system only for architecture diagrams. Do not force workflow or software-stack content into it.
• Establish one clear primary path before adding secondary or optional paths.
• Use groups only when they contain multiple related components.
• Select icons by component semantics. Reuse the supplied generic icon when no specific icon exists; do not invent one.
• Keep source icons byte-identical. Do not recolor, crop, flip, rotate, or otherwise modify them.
• Pick one standard component-icon size for the diagram. Use the small size for technical diagrams and the large size only for simple executive diagrams.
• Keep labels short, normally six words or fewer. Break a long approved name onto two lines or shorten it after showing the full name once; never solve overflow by shrinking one label.
• Align components and orthogonal paths to a grid. Reserve open connector lanes between groups and rows instead of routing through cards.
• For a cross-group connector, use only a short, direct stub from the source component to its nearest group edge; put lateral routing in the open lane outside the group.
• Land each arrow on the midpoint of its target edge with a straight final segment at least 16 pt long. Avoid backtracking, U-turns, and a bend immediately before the arrowhead.
• Put a numbered callout on a straight, open part of its path—not on a bend, arrowhead, group boundary, or another connector. Keep parallel callouts at least one callout diameter apart.
• Use the guide's 1 pt stroke and 4 pt arrowhead proportions. Arrowheads must touch the target edge and point cleanly into it at normal reading size.
• Snap a group-level path to the group edge and a component-level path to the component itself.
• Use the guide's existing path styles and palette. Do not invent new path colors, icon treatments, or group styles.
• Keep the architecture canvas on a white canvas. For a dark presentation surface, place the unchanged white diagram on a white panel over the dark surround; do not invert or recolor the diagram.
• Embed local PNG icons as data-URI symbols in tracked SVGs so GitLab renders them without external file loading. Keep a data-source attribute pointing to the repository asset.