- 3 minutes to read

What is a C4 Diagram Set?

A C4 Diagram Set is the main architecture container in Nodinite Architecture Diagrams.

It groups related diagrams so teams can move through architecture levels using one governed unit instead of disconnected files.

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 diagram belongs to exactly one Architecture Scope.

Automatic navigation, layered synchronization, and C4 drill-down all depend on that scope identity.

Core concept

A C4 Diagram Set can hold these related views for one architectural subject:

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 How is this container implemented?
Dynamic Runtime behavior Developers, operations What happens in this specific scenario?
Deployment Infrastructure Operations, infrastructure Where does the software execute?

This structure keeps drill-through navigation predictable 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 can update inferred relationships for related views in the same scope, including when creating the next zoom level Related C4 views are maintained as layered projections of one architecture scope
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 automatic layered synchronization is applied

Layered Mode should be understood as: maintaining multiple architectural views of the same scope.

Free Draw should be understood as: manual control with no automatic layered synchronization.

Scope contract

A Scope establishes the architectural identity shared by multiple diagrams.

Within a Scope:

  • Automatic navigation is enabled.
  • Layered synchronization is possible.
  • Diagram relationships can be inferred.
  • Repository bindings become reusable.
  • Generated diagrams remain connected.

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

Changing Architecture Scope

When Architecture Scope changes, users should expect inferred relationships to be re-evaluated.

Changing Scope will:

• Recompute automatic navigation
• Re-evaluate layered relationships
• Change resolver identity
• Potentially remove inferred links

Manual links are preserved.

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
Operational relevance Sets remain linked to Repository entities
Reusability The same set can be consumed in Mapify or Mermaid

Use this together with

Next Step