FondationFAM Numérique 5ème cycleNumérique 5ème cycle
DonateDons
Chapitre 8Chapter 8 Part 3 · Towards a multilateral third way Partie 3 · Vers une troisième voie multilatérale

Pattern no. 5 — “The whole in every part”: Architecture · Topology

Translated from the French, which remains the reference text. This translation is under review.

Pattern n°5 · Stratification (primary), Alternation, Thirdness · tensions T3, T5 · Legitimacy · volets I.2, II.2 · ↑ navigation

Schema F5.1 · Context of pattern no. 5

CONTEXT SCHEMA 5 Pattern no. 5 The whole in every part House the whole in every part: the protocol as a complete genetic heritage, carried in full by every implementation. Architecture · Topology Invariant under test: legitimacy TENSIONS AT WORK T3 Autonomy and connectedness T5 Diversity and unity OPERATORS MOBILISED Stratification primary this fiche describes what the waist of the hourglass becomes once propagated Alternation evolving a protocol that no one controls is the hard problem of the pattern Thirdness someone must hold the specification and certify conformance without owning the network RELATED PATTERNS UPSTREAM → 2 Running code first the hologram is proven by its implementations 4 Minimising the surface of the common what spreads everywhere must be small HINGE ↔ 6 Coding the law what the waist contains of the normative, this fiche propagates: read the two together DOWNSTREAM → 7 Turning the hourglass over evolution without a centre 11 The armour of the common defending a network that no one owns CONTEXT SCHEMA 5 Pattern no. 5 The whole in every part House the whole in every part: the protocol as a complete genetic heritage, carried in full by every implementation. Architecture · Topology Invariant under test: legitimacy TENSIONS AT WORK T3 Autonomy and connectedness T5 Diversity and unity OPERATORS MOBILISED Stratification primary this fiche describes what the waist of the hourglass becomes once propagated Alternation evolving a protocol that no one controls is the hard problem of the pattern Thirdness someone must hold the specification and certify conformance without owning the network RELATED PATTERNS UPSTREAM → 2 Running code first the hologram is proven by its implementations 4 Minimising the surface of the common what spreads everywhere must be small HINGE ↔ 6 Coding the law what the waist contains of the normative, this fiche propagates: read the two together DOWNSTREAM → 7 Turning the hourglass over evolution without a centre 11 The armour of the common defending a network that no one owns
The pattern within the grammar of chapter 7: the tensions it works, the operators it mobilises and what they do there, the invariant it puts to the test, its related patterns upstream and downstream and what ties them. The rule in italics and the glosses are the fiche's own.After fiche no. 5 of the report and the investigation's Knowledge Space (pattern language 0.3.0).

Tension(s) at work: Diversity and unity — of which this fiche is the literal embodiment: Morin's hologrammatic principle made technical; autonomy and connectedness. Implicitly, the founding topological question of the third way: how can network effects be obtained without the centre — since every centre becomes a bottleneck, and every bottleneck a rent?

Context: An ecosystem wants to make thousands of independent actors interoperate — without any one of them coordinating the others. The problem is real: coordination requires a common point of reference, and the platform solves it brutally well — one centre, one API, one truth. It is even its selling point: coherence through ownership. The decentralised ecosystem must produce the same coherence without the owner — failing which it is not a network but an archipelago of incompatible solitudes.

Forces at play: On one side, the need for a referent: discovery of participants, trust between strangers, rules of the game — something must be common, and the reflex is to house it somewhere. On the other, the lesson of two decades of platforms: every “somewhere” becomes a power — technical (single point of failure), economic (toll), political (censorship and complacency). The median compromise — the “neutral” central hub, the “trusted” aggregator — fails with regularity: the neutral hub is a platform in the making.

The pattern: House the whole in every part: the protocol as a complete genetic heritage, carried in full by every implementation. The network ceases to be a place and becomes a property: it is the sum of conforming implementations, and exists nowhere else. Three design corollaries follow. No privileged node: any participant can disappear, secede or fork without the network dying — survivability to the defection of anyone, the founder included, is the pattern's acceptance test. Minimal, replicable directories: even decentralised, a network must allow discovery; the discipline consists in reducing registries to the strict minimum and making them federable and copyable (Beckn's registries are its pure form; DeDi, the decentralised directory presented in chapter 6, makes a specification of it), for the directory is the last place where the centre likes to hide. Conformance replaces membership: one does not “join” the network, one conforms to it — test suites and certification form the membrane of the commons, in place of the membership contract a centre would have one sign.

Operator(s) mobilised: Primary: stratification — this fiche describes what the waist of the hourglass becomes once propagated: present everywhere, owned nowhere. Support: thirdness — someone must hold the specification and certify conformance without owning the network (fiche n°9); the hologram needs a reference negative. Support: alternation — evolving a protocol that no one controls is the hard problem of the pattern; it requires equipped version cycles (“Turning the hourglass over”, n°7).

The invariant under test: The pattern distributes power — so it also distributes responsibility, sometimes to the point of dissolving it: when no one is the centre, no one answers — for abuses, for moderation, for victims. Criterion of legitimacy: decentralised architecture does not exempt anyone from accountability — and the answer lies in the pattern itself: each part carries the whole, including the invariant. The values encoded in the protocol travel with it to every node (this is the hinge with fiche n°6: what “Coding the law” inscribes in the waist, “The whole in every part” propagates to the entire universe of implementations — the central discovery of this report, in two fiches). A second risk: the theatre of decentralisation — the formally open protocol, one of whose implementations concentrates most of the network, becomes a de facto centre again, as “decentralised” email learned by concentrating in the hands of a handful of operators. Associated criterion: measure concentration continuously, and treat it as a debt.

Schema F5.2 · The whole in every part

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
The protocol is carried entire by every implementation: no privileged node, minimal replicable registries, conformance in place of membership; the network becomes a property, not a place. The risk proper: distributed power dissolves responsibility, and an open protocol whose one implementation concentrates the network becomes a centre in fact.After pattern no. 5 of the report, “The whole in every part”.See also : Schema F4.2, Minimising the surface of the common · Schema F6.2, Coding the law.

Cases of embodiment: Indian: Beckn is the most deliberate application of the pattern — a transaction protocol whose every participant carries the whole grammar, deliberately skeletal registries, and a network (ONDC) designed as a network of networks rather than as a marketplace. The comparison within the corpus is instructive: UPI, with its central switch operated by NPCI, is not hologrammatic — it is a centralised utility under neutralised governance; Beckn is, in a sense, the lesson drawn: the next generation moves neutrality from the guardian into the architecture itself. European: ActivityPub and the Fediverse are its full-scale demonstration — no one can switch the network off, not even its creators; and the Data Spaces apply the pattern to the data economy: each connector embeds the whole of the Dataspace Protocol and the policies of the Rulebook — the whole, law included, in every part.

Counter-example: Twitter become X, 2023: overnight, the closure and prohibitive pricing of the central API killed, within a few weeks, an ecosystem ten years in the making — third-party clients, research tools, civic services — without recourse, without negotiable notice, and without the quality of what was dying weighing anything at all. The lesson goes beyond the anecdote: an ecosystem backed onto a central API is a colony — it lives by permission. Every actor that had built on that API had signed a precarious lease whose main clause it had never read: the centre can do anything, always, unilaterally. The experimental contrast is supplied by the same historical sequence: X's convulsions sent millions of users flooding to the Fediverse — which, precisely, no one could either buy or shut down. The theorem: what has a centre has a price; what has none is not for sale.

Signs of misapplication: Participant discovery goes through a private database. One actor's “official” SDK is the de facto obligatory passage. One node concentrates a dominant share of the network and no one is alarmed. The majority implementation adds unspecified extensions that the others must imitate (embrace-extend from within — “The armour of the common”, n°11). The network has a bank account, a board and a logo before it has two independent implementations. The failure of one particular server brings down something other than that server. Two symptoms warrant an alert; three, a diagnosis.

Related patterns: Upstream: “Minimising the surface of the common” (n°4 — what spreads everywhere must be small) and “Running code first” (n°2 — the hologram is proven by its implementations). Hinge: “Coding the law” (n°6 — what the waist contains of the normative, this fiche propagates: read the two together). Downstream: “Turning the hourglass over” (n°7 — evolution without a centre) and “The armour of the common” (n°11 — defending a network that no one owns).

Mission carried by the Fondation FAM. Mission portée par la Fondation FAM. ← Back to mission homeRetour à l'accueil de la mission www.fondation-fam.org — Pattern no. 5 — “The whole in every part”: Architecture · Topology — PART 3 www.fondation-fam.org — Pattern n°5 — « Le tout dans chaque partie » : Architecture · Topologie — PARTIE 3