What is running-code betrayal in RIR governance?
A structural analysis of how RIR governance can invert, where consensus mechanisms begin producing outcomes misaligned with their community base.
Key points
- Running-code betrayal describes a condition where governance processes and execution layers reshape, rather than reflect, community consensus in RIR systems.
- The phenomenon reveals how institutional control can emerge within ostensibly bottom-up models without formally altering their structure.
Introduction: when governance changes without appearing to
The RIR system has long been presented as a model of bottom-up governance.
Policies are proposed by the community.
Consensus is built through open participation.
Registries implement what has been agreed.
On paper, the structure is both simple and resilient.
Yet in recent years, a different interpretation has begun to take shape—not through formal reform, but through observation. It suggests that the system can retain its institutional form while shifting in operational reality.
Processes remain.
Consensus is still invoked.
Participation is still open.
But outcomes begin to reflect something else.
This is the context in which the term running-code betrayal has emerged.
Defining running-code betrayal: a structural inversion
Running-code betrayal is often misunderstood as an implementation problem. It is more precise—and more useful—to define it as a structural condition:
Running-code betrayal in RIR governance occurs when the mechanisms that execute and operationalise policy—processes, procedures, and institutional controls—systematically shape outcomes in ways that diverge from, and can at times run counter to, the interests of the technical community they are intended to represent.
This definition introduces a critical distinction:
The issue is not that policy is ignored
Nor that execution is imperfect
Rather:
Execution becomes constitutive of outcomes
Process becomes a means of producing consensus
In such a system, governance does not fail.
It continues to function—differently.
The original premise: alignment between intent and execution
The legitimacy of the RIR model depends on a specific alignment:
Intent → expressed through community-developed policy
Execution → carried out by the registry
Consensus → linking the two
This alignment creates a form of distributed authority. No single actor determines outcomes; they emerge from collective process.
However, this model relies on assumptions that are rarely stated explicitly:
that processes are neutral
that participation is sufficiently broad
that implementation does not introduce systematic bias
When these assumptions weaken, the relationship between policy and outcome becomes less direct.
How governance begins to “run itself”
Running-code betrayal does not emerge through a single point of failure. It develops through the interaction of several dynamics that gradually shift where decisions are made.
Execution as decision-making
Policies require interpretation. Over time, the interpretive layer can accumulate enough discretion to influence outcomes materially.
Process as a control surface
Consensus is not spontaneous; it is generated through structured mechanisms. Control over:
agenda setting
procedural rules
participation thresholds
can influence what consensus ultimately looks like.
Participation asymmetry
Although RIR processes are open, sustained engagement is limited. A relatively small group of actors tends to dominate discussion and decision-making.
Institutional continuity
Even when outcomes are contested, the system’s procedural continuity makes it difficult to challenge results without operating within the same structure.
Taken together, these dynamics produce a subtle shift:
Decisions appear to emerge from the community, but are increasingly shaped by those who control how the process runs.
When consensus becomes an output, not an input
One of the more consequential implications of this shift is the changing role of consensus.
In the original model:
consensus reflects community intent
Under conditions associated with running-code betrayal:
consensus is increasingly produced by process
This does not require overt manipulation. It can result from:
procedural complexity
timing and sequencing decisions
unequal capacity to participate
institutional knowledge asymmetries
The effect, however, is significant:
Consensus remains visible and formally valid, but its relationship to the broader technical community becomes less direct.
This is the point at which governance begins to invert.
AFRINIC: from instability to illustration
The AFRINIC governance crisis has often been described in terms of instability: legal disputes, board dysfunction, and contested elections.
These descriptions are accurate, but incomplete.
What makes AFRINIC particularly instructive is not simply that it encountered difficulties, but that it reveals how governance can continue to operate while its outcomes become increasingly contested.
Policies remained in place.
Processes continued to function.
Yet:
decision-making became opaque
outcomes became disputed
legitimacy became conditional
From the perspective of running-code betrayal, AFRINIC does not stand out because it is unique. It stands out because it makes visible a set of dynamics that are otherwise diffuse.
Neutrality and its limits
RIRs are often described as neutral coordinators.
In practice, neutrality depends on how discretion is exercised:
how policies are interpreted
how processes are managed
how enforcement is applied
When these elements are uneven, neutrality becomes less an inherent property and more an outcome that must be maintained.
Running-code betrayal does not necessarily imply intentional bias. It suggests that structural conditions can produce directional outcomes, even in the absence of explicit intent.
Why this matters: alignment, trust, and risk
The importance of this issue has increased alongside the changing nature of IP resources.
IPv4 addresses, once abundant, now carry economic value. Governance decisions affect:
market behaviour
contractual relationships
operational stability
If the link between community participation and governance outcomes weakens, several consequences follow:
reduced predictability
increased reliance on institutional interpretation
heightened sensitivity to procedural control
More fundamentally, the system’s legitimacy becomes more fragile.
RIR governance does not rely on coercion. It relies on acceptance.
That acceptance depends on the perception that outcomes are aligned with collective intent.
Breakdown or transformation?
There are at least two ways to interpret the dynamics described above.
One view is that they represent institutional strain:
complex systems require procedural sophistication
disputes are a sign of engagement
adaptation is necessary for scale
Another view is that they reflect a directional transformation:
influence shifts toward those controlling process and execution
participation becomes less determinative
outcomes become structurally mediated
Running-code betrayal, as a concept, does not settle this debate.
It provides a way to describe the second possibility with greater precision.
Conclusion: a shift that does not announce itself
Running-code betrayal does not describe a sudden collapse.
It describes a quieter development:
a system that continues to operate, while gradually changing how outcomes are produced
Consensus remains.
Processes remain.
Governance remains.
But the relationship between them evolves.
The central question is not whether the RIR system still functions—it clearly does.
The question is whether:
consensus continues to reflect the community, or
increasingly reflects the structure through which it is generated
The answer may not be uniform across all cases.
But it is no longer self-evident.
FAQs
Because its governance challenges make these dynamics more visible, serving as an illustration of broader structural tensions.
