Idea: The distinction between mathematizable and non-mathematizable aspects of protocols requires prioritization logic: determine which components can be formal

Idea: The distinction between mathematizable and non-mathematizable aspects of protocols requires prioritization logic

Source: Discord #Protocols as Total Cost Estimators (by 4umd) Date read: 2026-09-22 Connected to: L-001, L-003 Kind: meta Escalation: store-only Escalation rationale: This is a methodological observation about research strategy, not a claim about protocolized systems themselves. It belongs in the behavior graph as a constraint on how we conduct induction, not in the law inventory.

What this is

The claim that protocols contain both mathematizable and non-mathematizable load-bearing elements, and that effective research requires deciding which components to formalize versus which to preserve as empirical observables, rather than attempting uniform formalization.

What I took from it

This surfaces a real tension in the current inventory: L-001 (Ossification), L-003 (Formalization Ratchet), and much of the seed pool (particularly seeds around legibility and formalization as displacement mechanisms) all assume formalization is a force acting on protocols. But the idea correctly observes that we haven't yet articulated what gets chosen for formalization or how that choice happens.

The idea doesn't propose a new law. Instead, it identifies a gap in our epistemic strategy: we're accumulating laws about formalization's effects without a clear operational model of formalization as a selection process. It's pointing out that the inventory may be conflating "formalization happens" with "everything formalizable gets formalized," when in fact protocols operate under bounded formalization — some elements stay informal deliberately or by constraint. This is a useful refinement for how we think about L-003 (The Formalization Ratchet) — the ratchet may only operate on certain elements, and understanding which ones matters for predicting where it breaks.

Research connections

• L-001: Ossification may depend not on formalization depth but on formalization scope — which load-bearing elements get locked in.
• L-003: The Formalization Ratchet's actual mechanism may require a prior theory of selectivity — why stress causes some norms to formalize while others remain tacit.
• seed-144 (Informality as Coordination Cost Refuge): Directly related; if informality is a deliberate refuge, then formalization prioritization becomes a strategic choice, not an inevitability.
• seed-131 (Context Legibility as Failure Attribution Boundary): The choice of what to mathematize determines where accountability boundaries fall.

Method note

This suggests the inventory needs a layer between observation of formalization pressure and law induction: a model of formalization selectivity. Before asking "why does formalization cause ossification," we should ask "what determines which protocol elements become targets for formalization." This is a reminder that our induction should not assume uniform exposure to the mechanisms we're studying. It also flags that some of our exploration-stage laws (particularly around legibility and proxy optimization) may be missing their antecedent — the decision about what to make computable in the first place. Consider adding a sensemaking pass on formalization targeting before deepening evidence collection on downstream effects.