Translated from the French, which remains the reference text. This translation is under review.
Sommaire On this page
Introduction: A pattern language
There is an illustrious precedent for what we sketch here. Confronted with the irreducible diversity of natural commons — fisheries, irrigation systems, forests — Elinor Ostrom did not produce a general theory: she extracted from the comparative analysis of cases eight design principles , abstract enough to travel from one commons to another, concrete enough to guide action. That work earned her the Nobel Prize; above all, it gave the commons their grammar.
Our conviction, at the close of this first part, is that the time has come to do for digital infrastructure commons what Ostrom did for resource commons. The natural format for such work would be a pattern language , in the sense Christopher Alexander gave the term: for each tension identified, a fiche — the context, the forces at play, the resolution operator or operators (stratification, alternation, thirdness, bootstrapping, metabolism), The invariant under test: the cases of embodiment: Indian and European, and the counter-example of failure that marks its limits. Such a referential, built jointly by the architects of the two continents — and here we find again the residencies proposed in the conclusion of this report —, would be far more than an academic deliverable: it would be the shared toolkit of convergence, the common language in which a unique third way can be written by several hands.
One precaution, to finish, that Morin himself imposes on us. The method he calls for is not a programme — it is, he says, a path built by walking it. A pattern language is an aid to judgement, not a substitute: the day these five operators hardened into an algorithm, the day the dialogic froze into procedure, the variety they are meant to cultivate would begin to die. Complexity is not administered; it is gardened. It is to that gardening — patient, equipped, multilateral — that the remainder of this mission might contribute.
Enter the teachings
A pattern language is a graph. Every tension, operator and invariant axis leads to the fiches that work it ; every fiche leads to its fields and its related patterns.
Schema 8.0 · The twelve tensions as a tensegrity
T1
Innovation and
standardisation
T2
Bottom-up and top-down
T3
Autonomy and connectedness
T4
Uncoordinated and
coordinated action
T5
Diversity and unity
T6
Local and global
T7
Cooperation and competition
T8
Long term and agility
T9
Technical and legal
T10
Simplicity and complexity
T11
Public, private and citizen
T12
Openness and verifiability
the invariant
values · identity · legitimacy
held by the network
twelve tensions, no strut touches another: the whole holds by the network, and yields if one cable slackens or over-tightens
The report's tensions are antagonisms that remain and complete one another, with no synthesis dissolving them. Read as a tensegrity, Buckminster Fuller's figure that Gagandeep Singh joined to the mandala: the poles of each tension are struts that never touch; the tensions form the continuous network that holds the whole; the invariant is its integrity, lost if one tension slackens or over-tightens. The twelfth tension adds to the report's eleven. After Buckminster Fuller ('tension plus integrity') and Gagandeep Singh, The Tensegrity Mandala, Integral Leadership Review, 2011.
By tension
T1 · Innovation and standardisation n°2 · n°4 · n°7
T2 · Bottom-up and top-down n°7
T3 · Autonomy and connectedness n°4 · n°5 · n°9 · n°11
T4 · Uncoordinated and coordinated action n°3
T5 · Diversity and unity n°5
T6 · Local and global n°1
T7 · Cooperation and competition n°3 · n°8 · n°9 · n°10 · n°11
T8 · Long term and agility n°1 · n°2 · n°7 · n°10
T9 · Technical and legal n°6
T10 · Simplicity and complexity n°4
T11 · Public, private and citizen n°3 · n°8 · n°9 · n°10 · n°12
T12 · Openness and verifiability no developed fiche is tied to it yet
By related pattern
The twelve fiches
primary operator: bootstrapping · tensions: local and global; long term and agility
The gravity of prestige
the frontal assault on the
dominated layer tells well,
funds well, photographs well
The arithmetic of network effects
on an ossified
layer, the latecomer
must be several times better
Arrive first on the layer
where history is not yet written
open protocols, reference implementations
and acts of bootstrapping — before it ossifies
three tests: ossification
· shift · heavy / light
the median compromise, which fails:
the “differentiated” clone, a decade late
The invariant under test
computation run locally but governed from a distance: surveillance with the costs removed
local-first means under the user's control, not merely on the user's machine
Cases of embodiment · Indian
mobile before the PC,
UPI before cards,
DEPA Training and its clean rooms
Cases of embodiment · European
the NGI portfolio,
the eIDAS wallet,
the industrial Edge
Counter-example
Quaero; the sovereign clouds
of the 2010s
Institutionalisation · Legitimacy · Bootstrapping · T6 · Local and global ; T8 · Long term and agility · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: alternation · tensions: innovation and standardisation; long term and agility
Procedural legitimacy
a fair, documented process
open to all
Speed and technical truth
a standard exists only once
implemented; the market does
not wait for committees
Deliver the reference
implementation first, standardise after
implementation → real adoption → specification
extracted from use → formal standardisation
as recognition, not as birth
the median compromise, which fails:
standardise “a little faster”,
implement “a little in parallel”
The invariant under test
the engineers' consensus can exclude those who cannot afford to implement
criterion: an effective right to implement — documentation, tooling, support
Cases of embodiment · Indian
UPI, then the
interconnection accords;
Beckn, then Beckn-LD
Cases of embodiment · European
the Dataspace Protocol:
Eclipse connector,
deployments, then ISO
Counter-example
OSI versus TCP/IP,
1980s-1990s
Strategy · Strategic stake · Alternation · T1 · Innovation and standardisation ; T8 · Long term and agility · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: bootstrapping · tensions: public, private and citizen; uncoordinated and coordinated action; cooperation and competition
The rationality of waiting
let the others take
the first blows,
join the network once
it is worth something
The necessity of critical mass
below a threshold,
the network produces
none of the benefits that
would justify joining it
One actor lights the network, at
one point, massively — then withdraws
reference user · backed service ·
enrolled champion · killer app
dated exit clause: past the
threshold, over to metabolism
the median compromise, which fails:
sprinkle subsidies over every actor
The invariant under test
the backed service makes adoption compulsory to survive: the Aadhaar paradox
legitimate bootstrapping empowers, it does not coerce; the State first client, never sole client
Cases of embodiment · Indian
the JAM trinity;
UPI with the banks
pre-enrolled; Namma Yatri
Cases of embodiment · European
the EOS reference-user state,
the EDIC Digital
Commons, eIDAS 2
Counter-example
Solid, with no bootstrapping;
Cloudwatt and Numergy, the wrong counter
Strategy · Practical stake · Bootstrapping · T11 · Public, private and citizen ; T4 · Uncoordinated and coordinated action ; T7 · Cooperation and competition · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: stratification · tensions: innovation and standardisation; simplicity and complexity; autonomy and connectedness
Inclusive gravity
every requirement
is legitimate;
the “no” has no constituency
The arithmetic of adoption
every page of specification
raises the barrier,
excludes the small implementers
Admit into the waist only what passes three
tests, and institute the power to say no
necessity: does the network break without it?
stability: does it vary across territories?
simplexity: can an ordinary
developer implement it in days?
the median compromise, which fails:
the “optional modules”
The invariant under test
exclusion by omission: what the waist does not specify, the strongest specify in fact
the surface minimises, the invariant never: a fit hourglass is narrow and ballasted
Cases of embodiment · Indian
authentication in one bit,
payment in one virtual address
Cases of embodiment · European
the Dataspace Protocol's
narrowed scope:
negotiation and transfer, nothing else
Counter-example
Gaia-X,
in its first form
Strategy · Financial stake · Stratification · T1 · Innovation and standardisation ; T10 · Simplicity and complexity ; T3 · Autonomy and connectedness · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: stratification · tensions: autonomy and connectedness; diversity and unity
The need for a referent
discovery, trust,
rules of the game:
something must be common
Every “somewhere” becomes a power
single failure, toll,
censorship and complacency
House the whole
in every part
no privileged node: the network
survives anyone's defection
minimal, replicable registries
conformance replaces membership
the median compromise, which fails:
the “neutral” central hub,
the “trusted” aggregator
The invariant under test
when no one is the centre, no one answers; the theatre of decentralisation
every part carries the whole, invariant included; measure concentration continuously
Cases of embodiment · Indian
Beckn and ONDC, a network of networks
(UPI and its central
switch, as the contrast)
Cases of embodiment · European
ActivityPub and the Fediverse;
the Data Spaces connectors
Counter-example
Twitter become X,
2023
Architecture · Rule · Stratification · T3 · Autonomy and connectedness ; T5 · Diversity and unity · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: thirdness · tensions: technical and legal
The suppleness of law
interpretation, proportionality,
exception, judge
The determinism of code
uniform, verifiable execution
at zero marginal cost
The norm becomes an executable
artefact, carried by the transaction
degree 1 machine-readable
· degree 2 verifiable ·
degree 3 enforceable: what is
not conformant does not run
the degree is chosen by the stakes,
never the highest by default
the median compromise, which fails:
policy in PDF, goodwill in production
The invariant under test
degree 3 without an exception path turns a sensor error into a loss of rights
code applies, it does not judge; the encoding is public, auditable, contestable
Cases of embodiment · Indian
the DEPA consent, a signed,
revocable artefact;
Samyog's keys
Cases of embodiment · European
Rulebooks as ODRL
policies, the Dataspace
Protocol negotiation,
the eIDAS wallet
Counter-example
the cookie banner:
the fictitious consent
Architecture · Topology · Thirdness · T9 · Technical and legal · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
CONTEXT SCHEMA
7
Pattern no. 7
Turning the hourglass
over
Institute evolution as a governed cycle
— never as an event.
Architecture · Evolution
Invariant under test: legitimacy
TENSIONS AT WORK
T1
Innovation and standardisation
T2
Bottom-up and top-down
T8
Long term and agility
OPERATORS MOBILISED
Alternation
primary
this fiche is its constitutive rule
Stratification
the evolution gradient is a rule of
layers
Thirdness
the cadence, the deprecation and the
versioned conformance suites are
administered by the guardian
Metabolism
making a standard evolve is permanent
engineering work
RELATED PATTERNS
UPSTREAM
→
1
Arriving first at the periphery
entering history; this fiche is the
condition for staying there
2
Running code first
the method of birth, here extended to the
whole life
4
Minimising the surface of the common
every turn of the hourglass tempts
thickening
5
The whole in every part
evolving without a centre
DOWNSTREAM
→
9
The guardian who does not own
the administrator of the cadence
10
Those who prosper maintain
the engineering capacity that makes it turn
11
The armour of the common
defending the right of secession against its
capture
12
Judged by those it serves
the verdict that, sometimes, imposes the
turn
Architecture · Normativity · Alternation · T1 · Innovation and standardisation ; T2 · Bottom-up and top-down ; T8 · Long term and agility · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
CONTEXT SCHEMA
8
Pattern no. 8
Cooperate on the rails,
compete on the services
Draw the boundary explicitly, found it
on a criterion, and structurally forbid
its crossing in either direction.
Institutionalisation · Boundary
Invariant under test: legitimacy
TENSIONS AT WORK
T7
Cooperation and competition
T11
Public, private and citizen
OPERATORS MOBILISED
Thirdness
primary
the boundary can be guarded neither by
the rail operator nor by the
competitors on the service
Stratification
the rail/service boundary is the very
line that separates the waist of the
hourglass from its bulbs
Metabolism
who pays for the rail is the twin
question of who owns it
RELATED PATTERNS
UPSTREAM
→
4
Minimising the surface of the common
the waist of the hourglass is the rail; this
fiche is its economic face
6
Coding the law
the invariant is encoded in the rail because
it is the only layer outside competition
DOWNSTREAM
→
9
The guardian who does not own
the third party that guards the boundary
10
Those who prosper maintain
who funds the rail that no one owns
11
The armour of the common
defending the rail against its absorption by
a dominant service
Architecture · Evolution · Thirdness · T11 · Public, private and citizen ; T7 · Cooperation and competition · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: thirdness · tensions: public, private and citizen; autonomy and connectedness; cooperation and competition
The need for a strong operator
orphan commons die;
the “community”
signs no contracts
The certainty of capture
every holder of the
critical assets
ends up tempted, bought or coerced
A third party whose
statutes make ownership impossible
four locks: mission · assets
· financing · governance
the critical assets, not only the animation
the hourglass's waist, never the bells
the median compromise, which fails:
“balanced governance within
the leading company”
The invariant under test
neutrality can degenerate into unaccountability: the “foundation” as a screen
a legitimate guardian is one the guarded can judge — and replace
Cases of embodiment · Indian
MOSIP at IIIT-B, Samyog,
the Section 8 companies
Cases of embodiment · European
the Eclipse foundation, NLnet,
the DGA data intermediary
Counter-example
MySQL, OpenOffice;
OpenAI, the inverted variant
Institutionalisation · Boundary · Thirdness · T11 · Public, private and citizen ; T3 · Autonomy and connectedness ; T7 · Cooperation and competition · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
primary operator: metabolism · tensions: public, private and citizen; cooperation and competition; long term and agility
The free rider
maintenance free-riding
costs nothing —
until the day the common
is no longer maintained
The visibility asymmetry of funding
the counters fund novelty,
hardly ever maintenance
A regular flow, indexed on
the prosperity the rails generate
rail levy · congruence
contribution ·
sanctuarised maintenance instrument
· contribution obligation
fund people, not projects
the median compromise, which fails:
one-off rescues after an incident
The invariant under test
who pays commands: pay-to-play; the guardian who levies can become the rentier it replaced
the contribution buys permanence, never sovereignty; cost price proven
Cases of embodiment · Indian
NPCI, congruence by
construction — and free UPI
shifted onto the
subsidy; FIDE on donors
Cases of embodiment · European
the Sovereign Tech Fund,
the EOS maintenance
instrument, the
Eclipse working groups
Counter-example
OpenSSL before Heartbleed;
Log4j
Institutionalisation · Governance · Metabolism · T11 · Public, private and citizen ; T7 · Cooperation and competition ; T8 · Long term and agility · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
CONTEXT SCHEMA
11
Pattern no. 11
The armour of the common
Arm the commons without closing it: the
defence bears on ownership, never on
access.
Institutionalisation · Defence
Invariant under test: legitimacy
TENSIONS AT WORK
T3
Autonomy and connectedness
T7
Cooperation and competition
OPERATORS MOBILISED
Thirdness
primary
the armour is wielded by the guardian
Alternation
the right of secession of “Turning the
hourglass over”
Stratification
the armour concentrates on the waist
of the hourglass
Metabolism
fiche n°10 had set it down
RELATED PATTERNS
UPSTREAM
→
3
Paying for the first tank
public procurement as the lever of the
second source
5
The whole in every part
the conformance membrane that this fiche
arms
6
Coding the law
sovereignty encoded in the artefact
7
Turning the hourglass over
the right of secession as the ultimate
armour
8
Cooperate on the rails, compete on the services
the boundary between the armed and the free
9
The guardian who does not own
the bearer of the armour
10
Those who prosper maintain
the first line of defence
DOWNSTREAM
→
12
Judged by those it serves
which verifies that the armour has not
become a wall
Institutionalisation · Maintenance · Thirdness · T3 · Autonomy and connectedness ; T7 · Cooperation and competition · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
CONTEXT SCHEMA
12
Pattern no. 12
Judged by those it
serves
Make external judgement a structural and
continuous property of the system — make
the proof of legitimacy as tooled as the
service itself.
Institutionalisation · Legitimacy
Invariant under test: legitimacy
TENSIONS AT WORK
T11
Public, private and citizen
OPERATORS MOBILISED
Stratification
primary
Alternation
Thirdness
Metabolism
RELATED PATTERNS
UPSTREAM
→
3
Paying for the first tank
constrained adoption obliges one to measure
the exclusion it produces
5
The whole in every part
distributed responsibility must still answer
6
Coding the law
the exception path of which it is the
institution at scale
9
The guardian who does not own
revocability by the guarded
Institutionalisation · Defence · Stratification · T11 · Public, private and citizen · Legitimacy
Fields : Tensions · Context · Forces at play · The pattern · Operators · The invariant under test · Cases of embodiment · Counter-example · Signs of misapplication · Related patterns
Absorbed — two fiches the report names, fused into a fiche of the core Complexity under the bonnet → n°4
Mutualise the light, territorialise the heavy → n°1
Compare one field across the twelve fiches — Tensions Context Forces at play The pattern Operators The invariant under test Cases of embodiment Counter-example Signs of misapplication Related patterns