Expand–contract — the boundary is a muscle

How it holds over time. The boundary is not a setting fixed once; it is a muscle that contracts under threat and relaxes under safety:

Open → shock (spam / malicious influx) → contract (retreat to whitelist / WoT floor) → adapt "in the between" (the stack retunes, devs ship) → re-expand.

Neither pole is the answer: the open pool is exposed; the hard whitelist is safe but defeats the purpose of joining a commons. Governance is the retuning between them — and the option space grows with each shock (every new spec, hackathon output, WoT function is one more method the space did not have before). The always-working floor is what licenses the experimentation above it.

This is Ostrom's own "Being Prepared for Change" (UKAC ch. 3, p. 68: fixed rules over-trust current knowledge; adaptive systems suboptimal short-run, wiser long-run) instantiated and observable — not an ecological metaphor imported onto her framework. Locator and verbatim text in {{ref:src-analyzing-knowledge-commons|Ostrom & Hess 2007}}.

Standing discipline #3: keep the observable oscillation distinct from the longer-horizon maturation conjecture ({{ref:q-maturation-hypothesis|Q: The maturation hypothesis (flagged conjecture)}}) — say which is which first.

Related: - {{ref:emergentgov|Index}} - {{ref:concept-adaptive-governance|Adaptive governance as feedback architecture}} - {{ref:concept-boundary-rules|Boundary (entry and exit) rules}} - {{ref:concept-requisite-variety|Requisite variety (Ashby's law, institutionalized)}} - {{ref:claim-relay-spectrum|The relay spectrum}} - {{ref:q-maturation-hypothesis|Q: The maturation hypothesis (flagged conjecture)}} - {{ref:q-generativity-robustness|Q: Is robustness generativity rather than redundancy?}}