- 5 minutes to read

What is a C4 Diagram Set?

A C4 Diagram Set is the main architecture container in Nodinite Architecture Diagrams (C4 Diagrams). It groups related diagrams so teams can move through architecture levels using one governed unit instead of disconnected files.

  • ✅ One home for every C4 view of a software system, from System Landscape to Deployment
  • ✅ New 7.12 Inferred navigation between levels from scope, subject and Repository bindings: nothing to sync
  • ✅ Set-level Roles decide who can view or manage the architecture
  • ✅ Draft, Active, and Archived lifecycle for governed publishing

The Order-to-Cash Demo set page: its diagrams with Architectural Scope, Level, Mode and State, one Component diagram per Service, the Assistance and Coverage matrix with one row per System, then the Export menu open, animated walkthrough (7.12)
Animated walkthrough: a set page lists the set's diagrams with Architectural Scope, Level, Mode, and State. Assistance and Coverage shows a matrix with a Landscape row and one row per System against Landscape, Context, Container, Component, Dynamic, and Deployment; a cell with more than one diagram shows the count. Export downloads every diagram of the set as one ZIP of SVG or PNG images, or Mermaid, Structurizr DSL, PlantUML, or Draw.io markup.

Diagram Sets list in the Repository with Mode and Active and Draft diagram counts per set (7.12)
Example of the Diagram Sets list: each set shows its tags, its Mode (Free Draw or Layered), and how many Active and Draft diagrams it holds.

Architecture Scope is the anchor

In a Diagram Set, Architecture Scope defines which architecture a diagram describes.

Every diagram within the same Architecture Scope is a different viewpoint of the same architecture.

Important

Golden Rule

A diagram never exists in isolation.

Every Context (L1), Container (L2) and Component (L3) diagram has one System as its Architecture Scope before it can be promoted to Active.

Its navigation pills come from that scope, the subject, and the bindings of its elements.

New 7.12 The scope is always one System. A System Landscape (L0) has none. A Dynamic or Deployment diagram has none or one System and can be promoted without one: the Designer shows Architectural Scope guidance instead of Architectural Scope required before promotion. An L3 also has a Subject: the Service or Contract whose inside it shows. Set the scope early to keep the diagram grounded in the Repository Model.

Core concept

A C4 Diagram Set can hold these related views of one software system:

Level Purpose Typical audience Main question answered
System Landscape (L0) Enterprise overview Architects, managers How do our systems fit together?
Context (L1) One system in its environment Architects, business Who interacts with this system?
Container (L2) Major runtime building blocks Architects, developers What major applications or services make up the system?
Component (L3) Internal implementation Developers, integration specialists What is inside this Service or Contract (the L3's Subject)?
Dynamic Runtime behavior Developers, operations What happens in this specific scenario?
Deployment Infrastructure Operations, infrastructure Where does the software execute?

This structure keeps navigation predictable, one level at a time, and supports versioned governance workflows.

Layered Mode and Free Draw

Mode Scope behavior Node and boundary behavior Cross-diagram effect
Layered Mode Uses Architecture Scope as a contract for related C4 views Adding or removing nodes and boundaries propagates to the set's related Layered Drafts, found through the inferred relations, including when creating the next zoom level The bindings stay consistent across the related views; Active and Archived diagrams are left alone
Free Draw Scope still exists for organization and navigation context You can change nodes and boundaries locally without affecting other Draft diagrams, regardless of scope No propagation

Layered Mode should be understood as: keeping the bindings consistent across related views.

Free Draw should be understood as: manual control with no propagation. Navigation pills are inferred in both modes.

Scope contract

A Scope establishes the architectural identity shared by multiple diagrams.

Within a Scope:

  • The System's Context, Container and Component diagrams reach each other through Inside, Context and Zoom out pills.
  • Layered propagation is possible.
  • Repository bindings become reusable.

Navigation itself needs no shared scope: it comes from the diagram type, the scope, the subject and the bindings, inside the set. See Navigation Between C4 Diagrams.

Changing Scope is therefore not a cosmetic action. It changes the architectural identity of the diagram.

Changing Architecture Scope

When Architecture Scope changes, the diagram's navigation pills are recomputed the next time it opens; there are no stored inferred links to remove.

Changing Scope will:

• Recompute the navigation pills on the next open
• Re-evaluate layered relationships
• Change resolver identity

Manual links are kept, and may turn Stale:
"Scope or entity relationship has changed since link was created"

Why it matters in the Repository Model

Repository concern Diagram Set value
Architecture consistency Related diagrams stay grouped under one set
Access control Set-level roles define who can view or manage (Role-Based Access for C4 Diagram Sets)
Operational relevance Sets remain linked to Repository entities
Reusability The same set can be consumed in Mapify or Mermaid

Use this together with

Next Steps