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. 7 — “Turning the hourglass over”: Architecture · Evolution

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

Pattern n°7 · Alternation (primary), Metabolism, Stratification, Thirdness · tensions T1, T2, T8 · Legitimacy · volets I.2, II.1 · ↑ navigation

Schema F7.1 · Context of pattern no. 7

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 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
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. 7 of the report and the investigation's Knowledge Space (pattern language 0.3.0).

Tension(s) at work: Long term and agility — of which this fiche is the constitutive rule; innovation and standardisation, taken up again in their temporal dimension; bottom-up and top-down, whose cycle it organises. Implicitly, the second half of the momentum challenge: “Arriving first at the periphery” says how to enter history — this fiche says how to stay there. The question: how does one make an invariant evolve? — for an adopted protocol has become the waist of the hourglass, and the waist, by definition, is what does not move.

Context: A protocol has won. It is implemented everywhere, it carries millions of transactions, it has become the common invariant of a network that no one owns. And that is precisely where its danger begins: the world keeps changing around it — new threats, new uses, new substrates (the move to the periphery is one of them) — while every modification of the standard now costs all its implementers. The winner's paradox: the more a standard is adopted, the harder it is to change; success is the first cause of ossification. The hologrammatic network makes the problem worse: there is no centre where the change could be decided, and every part carries the whole — so every part has to change.

Forces at play: On one side, the implementers' demand for stability: installed base, amortised investments, compatibility of millions of existing integrations — every break is a tax, and the installed base always votes for immobility. On the other, the demand for change coming from reality: a flaw to fix, a use the standard had not foreseen, a technology that shifts what is possible — and a standard that no longer answers reality gets bypassed by wild extensions, then replaced. The median compromise takes two equally fatal forms: the “optional extensions” that fragment the network into incompatible dialects, and the great breaking release — the big bang that everyone approves and no one adopts.

The pattern: Institute evolution as a governed cycle — never as an event. The hourglass is not turned over once; it is turned over at a cadence, and the cadence is an institution. Four moves. The instituted rhythm: a revision periodicity known in advance — the standard carries the date of its next revision as a contract carries its term; the predictability of change is what makes it acceptable to the installed base. Compatibility as a contract: never break what exists, never freeze it — deprecation announced, dated, tooled, with an overlap period during which the old and the new coexist; a version that excludes conforming implementations is not an evolution, it is a secession. The evolution gradient: the layers do not change at the same speed — the bulbs fast, the waist slowly, the normative invariant almost never; the discipline consists in housing experimentation in the fast layers (framed extensions, sandboxes, domain profiles) and in promoting into the waist only what several implementations have put to the test — “Running code first” applied to evolution: nothing enters the standard without having first run beside it. The right of secession: the fork is the safety valve of the commons — a standard that no one can fork is a standard that no one can correct, and the possibility of dissent is what keeps the guardian honest. The rule, already set out in chapter 7 of this report: never freeze the hourglass — turn it over. Its operational corollary: a standard is alive as long as it has a date.

Operator(s) mobilised: Primary: alternation — this fiche is its constitutive rule; it organises the breathing of divergence-convergence-divergence over the long run, where “Running code first” (n°2) described it only at birth. Support: stratification — the evolution gradient is a rule of layers: an hourglass is kept alive through its bulbs, not through its waist. Support: thirdness — the cadence, the deprecation and the versioned conformance suites are administered by the guardian (n°9), the only actor whose interest is the rhythm and not one of the versions. Support: metabolism — making a standard evolve is permanent engineering work; a commons without funded capacity does not turn, it cracks (n°10).

The invariant under test: The risk proper to the pattern is that the turning over serves as a pretext. The next version can recentralise quietly — an increased complexity that only the dominant player knows how to implement, and every turn of the hourglass eliminates one more implementer (this is “Minimising the surface of the common” (n°4) violated by the ratchet method). It can also be captured by those who fund it (n°10), or blow away a protection without anyone noticing — a version that silently removes what “Coding the law” (n°6) had inscribed. And there is the opposite risk: churn — a standard that turns too fast exhausts the small, for instability is a regressive tax: the big absorb the migrations, the small drop out. Criterion of legitimacy, threefold: every version preserves the normative invariant (what is encoded is not silently de-encoded); every version passes the small-team test (n°4); no one served loses the service because of a version — deprecation respects users before implementers. A legitimate hourglass turns at the speed of the slowest of its necessary nodes.

Cases of embodiment: Indian: UPI is an hourglass in continuous rotation for a decade — version after version, it has absorbed recurring payments, offline transactions, credit, international use, without ever breaking the compatibility of existing applications. Beckn institutionalises the evolution gradient in its very structure: a slowly evolving core protocol and domain schemas (mobility, commerce, health) that evolve fast, separately — the bulbs as the laboratory of the waist. And Aadhaar had to turn its hourglass over under the constraint of an external verdict: under the pressure of the litigation that led to the 2018 judgment came the virtual identifier, offline verification, masking — proof that the cycle “feedback corrects” (“Judged by those it serves”, n°12) passes through a capacity to evolve. European: the GSM → 3G → 4G → 5G lineage is the largest rotating hourglass in industrial history — an instituted rhythm of releases at a regular cadence, backward compatibility maintained over thirty years, and a consortium governance that holds the cadence: the coopetition of “Cooperate on the rails, compete on the services” (n°8) lasted only because it knew how to turn. Closer to us, eIDAS carried out its turning over through the law — from 2014 to the recast that institutes the wallet — while the Dataspace Protocol is learning to version itself under a neutral foundation.

Counter-example: Two deaths of the hourglass, symmetrical. The fossil: Minitel. Arrived first at the periphery — the networked home terminal, a decade before the Web, millions of households — and the winner on its own ground, it refused to turn: centralised architecture, captive pricing, no opening towards the emerging networks. It held on by inertia until the Web bypassed it, then survived twenty years as a museum piece left switched on. The lesson completes fiche n°1: arriving first is worth something only if one knows how to stay — and staying means moving. The perpetual building site: IPv6. The right version, technically necessary, specified as early as the late 1990s — and a turning over that, a quarter of a century later, is still not complete: no cadence, no coexistence designed as a contract, no incentive for the individual implementer to migrate before the others. The sand does not flow; the hourglass has stayed stuck in the middle of its turn. The theorem: a standard dies in two ways — by refusing to turn, or by never finishing its turn. Cadence is what separates evolution from agony.

Signs of misapplication: The latest version is several years old and no roadmap exists — or, conversely, every version breaks the previous one. There is no written, dated, tooled deprecation policy. The conformance suites are no longer up to date with the current version. Unspecified extensions proliferate and become dialects. The fork is made impossible by the trademark or the licence. Evolution is decided in a closed committee, without prior implementation. The number of independent implementers falls with every version. A version has removed a protection without announcing it. Two symptoms are a warning; three, a diagnosis.

Related patterns: Upstream: “Arriving first at the periphery” (n°1 — entering history; this fiche is the condition for staying there), “Running code first” (n°2 — the method of birth, here extended to the whole life), “Minimising the surface of the common” (n°4 — every turn of the hourglass tempts thickening), “The whole in every part” (n°5 — evolving without a centre). Downstream: “The guardian who does not own” (n°9 — the administrator of the cadence), “Those who prosper maintain” (n°10 — the engineering capacity that makes it turn), “Judged by those it serves” (n°12 — the verdict that, sometimes, imposes the turn). Further on: “The armour of the common” (n°11 — defending the right of secession against its capture).

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. 7 — “Turning the hourglass over”: Architecture · Evolution — PART 3 www.fondation-fam.org — Pattern n°7 — « Retourner le sablier » : Architecture · Évolution — PARTIE 3