Idea: Variety expands to absorb available potential, analogous to Parkinson's law but driven by protocol boundary gradients rather than incentive inflation.

Idea: Variety expands to absorb available potential, analogous to Parkinson's law but driven by protocol boundary gradients rather than incentive inflation.

Source: Discord #Requisite Variety as Protocol Constraint (by _vgr) Date read: 2026-05-31 Connected to: H-001 Escalation: store-only Escalation rationale: The idea proposes a mechanistic principle but lacks empirical anchoring or clear distinction from existing dynamics. It warrants observation and refinement before escalation to hypothesis status. The analogy to Parkinson's law is suggestive but needs formalization around what "potential" means in protocol contexts and how "boundary gradients" drive expansion.

What this is

Protocol systems expand their internal complexity and functional scope to fill the degrees of freedom available at their architectural boundaries, driven not by incentive pressure alone but by structural permission to vary.

What I took from it

This idea sits at an interesting angle to H-001 (coordination cost conservation). If H-001 posits that costs are conserved across layers, this idea suggests that variety—the actual proliferation of distinct states, behaviors, or subsystems—is driven not by external incentives (as Parkinson's original law claims) but by the permission structure of protocol boundaries.

The move is subtle but significant: it reframes expansion as a consequence of structural topology rather than actor incentives alone. This opens a question H-001 doesn't yet address—where does the energy for complexity come from, and how is it distributed? It also hints at a relationship to L-005 (Gall's law): if variety expands into available potential, does this make working systems more resistant to redesign because the potential space becomes saturated?

However, the idea remains analogical. "Boundary gradients" and "available potential" need operationalization—what measurable quantities do these refer to in protocol contexts? Without that, it reads as a compelling intuition rather than a testable claim.

Research connections

• H-001: Directly proposes a mechanism for how costs might not be conserved—if variety absorbs potential at boundaries, does this violate or refine the conservation hypothesis?
• L-003 (Formalization Ratchet): Complementary direction: formalization compresses informal space; this idea suggests formal boundaries create new space for variety expansion elsewhere.
• L-005 (Gall Generalization): If variety expands into available potential, saturation of that potential may be what makes redesign unsafe.

Candidate laws or signals

CL-vgr-001: Boundary-Driven Variety Expansion — Protocol systems expand functional and structural variety to occupy the degrees of freedom available at their architectural boundaries, independent of external incentive pressure.

Status note: Candidate pending operationalization of "available potential" and "boundary gradient" as measurable quantities. Requires empirical cases (e.g., API surface expansion, permission scope bloat, specification complexity under modular constraints).