Genesis from Chronic, Self-Refreshing Threat
Dutch water boards, some tracing to the thirteenth century, never needed a founding scandal because flooding was continuous, not occasional — the hazard refreshed faster than institutional memory could decay.
What decision changes?
Prefer continuous, well-monitored capability growth over discontinuous jumps where possible: every increment then acts as a small, survivable demonstration that keeps correction attention warm, the way ordinary winter weather kept Dutch dike inspection vigilant without a flood.
The Dutch water boards — the waterschappen, some tracing to the thirteenth century — are among the oldest continuously operating democratic institutions in Europe, and they never needed a founding scandal. Coastal and low-lying communities faced flooding not as an occasional event but as a permanent condition: the sea never stopped rising, the rivers never stopped silting, and a neglected dike section threatened everyone behind it. The institutions that managed this — with taxing authority to fund maintenance, inspection duties, and enforcement against negligent landholders — never had the chance to idle between disasters. Ordinary winter weather did the work of keeping them vigilant that scandals and catastrophes do elsewhere.
The underlying principle is about timescales. Institutional memory decays: the people who remember why a rule exists retire, and the rule starts to look like overhead. But the Dutch hazard refreshed faster than the memory could decay. Nobody had to remember why dikes matter; the water reminded them annually. This is why the water boards persisted for seven centuries while catastrophe-founded institutions elsewhere eroded within two or three generations (see the reform-decay card for the mirror image).
Quieter versions of the same route exist. Common-law precedent builds correction doctrine one small dispute at a time. The internet’s standards body, the IETF, built its authority through “rough consensus and running code” — an accretion of small, unglamorous fixes rather than any founding mandate. In each case, a steady stream of minor, survivable failures substitutes for the big one.
For AI, this route carries a directional policy implication that is easy to miss. If AI capability grows relatively continuously, every increment is itself a small, survivable demonstration of slightly larger reach — a permanent, low-grade dike inspection that keeps oversight attention warm without requiring a discrete catastrophe. If capability instead arrives in large, discontinuous jumps, this genesis route closes along with the catastrophe route, leaving only the money-at-risk path. That is a reason to prefer continuous, well-monitored capability growth over sudden leaps — independent of the direct safety argument for either — and a reason to build things like standing AI-harms dispute bodies that convert diffuse harms into a steady, visible stream of small cases.
One of eleven historical case studies in Institutional Genesis, Memory, and Decay — see the overview for the full life-cycle map, or read the complete appendix.
What would count as evidence?
The waterschappen's levy authority, inspection duties, and enforcement against negligent maintenance persisted for centuries without needing a catastrophe to justify renewal; the IETF's 'rough consensus and running code' and common-law precedent show the same accretive, no-founding-disaster pattern.