Methodology

How to read the map

Begin with the arrows and moving points. They show the direction in which the map asks the reader to follow a relationship: from the source concept toward a function, system, or service it enables or affects. Movement in both directions marks a reciprocal relationship. When animations are turned off, arrowheads preserve the same direction. These are conceptual flows, not measurements of traffic or literal routes taken by every packet.

Selecting any node opens more than a description. A node may include Foundational documents, curated primary materials that establish its technical or institutional basis, and Policymaking fora, standing working groups, governance bodies, or durable participation processes where relevant rules and practices continue to be developed or reviewed. These two sections connect the map’s explanation to both evidence and ongoing policymaking.

• Solid lines mark the main direct dependency or functional relationship in the map’s authored reading path.
• Dashed lines mark a mediated, conditional, or non-universal path. The relationship may depend on an intermediate function, a deployment choice, or an optional service; it should not be read as applying in every implementation.
• Blue lines are standard structural connections.
• Pink lines emphasize critical chains and coordination dependencies.
• Green lines appear after selecting a node. They connect the selected node to other nodes that share at least one institution listed in the institution rail, revealing where the same body participates across different parts of the map. The line’s outward reveal begins at the selected node only to make the connection easy to follow: it does not indicate technical flow, causation, control, or a direction of institutional authority. Green lines are temporary explanatory links, not additional structural dependencies.
• Light-blue nodes are the map’s standard concepts and functions. Pink nodes identify critical dependencies or coordination points given additional emphasis in this model. Purple nodes are cross-cutting overlays, such as VPNs, darknets, and the crypto space, that sit alongside the main structure rather than forming a single mandatory stage in it.
• Small satellite nodes are specialist terms attached to a broader parent concept. Their color comes from that parent; they add detail without becoming separate stops in the main reading path.

Color, size, and emphasis identify the role a concept plays in this authored model. They do not measure traffic, market share, institutional authority, or real-world importance.

What the map is for

The Internet Governance Map begins with a teaching problem. The Internet’s structure and its decision-making processes are difficult to see as a whole, especially for readers who do not work directly with its protocols, infrastructure, or institutions. Technical explanations often stop before reaching governance, while policy explanations may name organizations without showing the systems through which their decisions take effect. The map brings these sides together and presents them as parts of the same system for learning and teaching.

To make that system readable, the map translates a distributed and overlapping reality into a broadly linear visual design. It creates paths from physical infrastructure through interconnection, naming, numbering, and routing to hosting and user-facing services. Institutions are placed alongside the functions in which they participate. The Internet does not operate as one simple chain, but the linear arrangement provides a starting point and a sequence to follow.

This simplification carries a cost. Some distinctions, exceptions, and parallel relationships have to be condensed or left outside the frame. The model retains as much fidelity as the abstraction permits: enough technical and institutional detail to show meaningful dependencies, while keeping the whole model legible. Its paths let readers follow a function upstream toward the resources, rules, and organizations that shape it, and downstream toward the systems and services affected by a decision.

Governance is understood here to include the development of standards, the coordination of shared resources, contractual arrangements, public regulation, and the decisions operators make in running their services. The map is an authored interpretation of how these forms of decision-making meet the Internet’s technical structure, rather than a measurement or a claim that only one arrangement is possible.

Selecting and separating concepts

The abstraction depends on choosing a useful level of detail. Core nodes represent functions and categories that help explain how the Internet works and where decisions take effect. A concept warrants separate treatment when combining it with another would obscure a relevant dependency or difference in responsibility. Registries and registrars, for example, remain separate because operating a domain extension and managing a customer’s registration involve different functions and contractual roles.

The level of detail varies with the explanatory need. A protocol such as BGP, a broad service category such as hosting and cloud, and a coordinating function such as IANA are different kinds of concept. Their appearance as nodes makes their relationships visible; it does not make them equivalent units of analysis. Likewise, websites and platforms overlap in practice, but separating them helps distinguish publishing content from organizing participation and setting rules for users.

Other concepts are grouped when the finer distinction would interrupt the main reading path more than it would clarify it. Hosting and cloud are brought together around their role in running services, while the Spam node gathers related forms of abuse in one place. The accompanying descriptions establish the scope of these groupings. The expert layer adds selected specialist terms beside a parent concept, offering routes into greater detail without making the overview an inventory of every technology.

Interpreting connections and visual emphasis

The main connections turn the selected relationships into paths across the map. Following a path backward traces the dependencies that shape a function; following it forward traces related systems and services through which a technical change, policy choice, or operational failure may be implemented or felt. Institutional links and policymaking sources identify where relevant decisions are developed or carried out. “Upstream” and “downstream” are therefore relative to the path being examined, rather than fixed positions in a single hierarchy.

The meaning of each connection still depends on the concepts involved. The link from hardware manufacturers to physical infrastructure concerns material provision, while the registry–registrar connection concerns domain registration. A path across several nodes is an explanation of related functions; it is not necessarily the route taken by a request or a sequence in which every service must operate.

Direction indicates how a relationship is presented, and a two-way connection marks a relationship read in both directions. It does not establish a general rule of causation or authority. The node descriptions provide the context for interpreting each connection. An omitted connection does not indicate that no relationship exists.

Layout and visual emphasis are also editorial choices. They bring related functions together and draw attention to selected dependencies and coordination points. Position, size, color, and line treatment do not derive from measurements of traffic, market share, or institutional power. Animated packets make direction easier to follow; their speed and frequency do not represent observed traffic. When a selection changes the layout or highlighting, it changes the reading focus rather than the underlying model.

Institutions and shared involvement

Institutions form a separate layer that accommodates several organizations around one function and the same organization across several functions. Associations distinguish roles such as setting standards, coordinating resources, regulating activity, or operating a system. A connection identifies a relevant role within that body’s remit, without assigning it responsibility for the whole field.

Some entries identify individual organizations; others collect a class of actors, such as governments, or a regional system, such as the Regional Internet Registries. These groupings provide orientation while leaving differences in jurisdiction, policy, and practice to the linked material.

Selecting a node reveals green connections to other nodes associated with the same institutions. These connections show shared institutional involvement. They do not assert a further technical dependency, or imply that an institution exercises the same kind of authority over both functions.

Sources and terminology

The map provides two kinds of source material. Foundational documents provide primary material on the technical or policy basis of a concept, including specifications, architectural descriptions, and governing agreements. Policymaking fora direct readers to standing working groups, governance bodies, and recurring consultation or proposal processes where relevant rules or practices continue to be developed and reviewed. A time-bounded working group, single policy-development proceeding, review, event, report, or closed consultation is not treated as a forum. When no durable and directly relevant venue can be identified, the map leaves the section empty rather than substituting a weak match. Inclusion identifies a place to investigate or participate; it does not imply that all participants agree.

Primary documents are preferred for claims about technical operation or institutional remit. Their authority is specific to the subject: a standard describes a technical arrangement, and an agreement defines obligations within its scope. Neither alone establishes how widely a practice is adopted or how much influence an organization has. The sources support the concepts being explained; the selection, grouping, and arrangement of those concepts remain the map’s editorial interpretation.

English and Portuguese descriptions preserve the same meaning, with familiar technical terms retained where translation would obscure it. Short explanations omit detail where it is not needed to understand the relationship. Readers should turn to the linked sources when a distinction matters to their particular question.

Revision and use

Descriptions and connections are revised when technical practice or institutional roles change. Each revision considers neighboring concepts as well as the entry being edited. Automated checks maintain consistent identifiers, valid connections, and complete language fields; assessing the substance of a relationship remains a matter of editorial review.

The map supports teaching, self-guided learning, initial research, and discussion across technical and policy fields. A useful reading starts with one node, follows its dependencies and consequences, and then examines the institutions and source material attached to that part of the chain. Conclusions about a particular dispute, jurisdiction, or market require evidence beyond the map. For formal research, verify and cite the underlying documents directly, and treat the map itself as the interpretive model through which the question was approached.