Identifying physical laws versus local rules is a critical diagnostic step for any analyst, as it determines what must be accepted as a fixed parameter and what can be redesigned as a control variable[1][2]. The distinction rests on three primary criteria: universality, inexorability, and rate-dependence[3].
The Criteria for Identification
| Feature | Physical Laws (The Environment) | Local Rules (The System) |
|---|---|---|
| Scope | Universal: They apply everywhere in the material universe[3][5]. | Local: They are specific to a particular system, culture, or organization[4][5]. |
| Nature | Inexorable: They cannot be disobeyed or changed; they are “fixed facts”[4][6]. | Arbitrary: They are created by evolution or human design and can be modified[4][5]. |
| Temporal | Rate-Dependent: They rely on physical dynamics, force, and time (e.g., the speed of a falling ball)[7][8]. | Rate-Independent: The meaning of the rule remains the same regardless of how fast it is executed (e.g., a traffic light or a genetic code)[7][9]. |
How to Identify Laws
Physical laws exist in the Environment—the domain across the “Epistemic Cut”[1].
• The Constraint Test: Laws act as “context-independent constraints” or “walls” that reduce the number of ways a system can behave regardless of the parts’ intentions[12].
• The Thermodynamic Check: If a state of order appears where there should be chaos, an external agent has likely performed work using physical laws like thermodynamics[13][14].
• The “Given” Fact: When designing a system, laws are the conditions that must be accepted as “given,” such as gravity, physical infrastructure, or the laws of supply and demand[6][15].
How to Identify Rules
Local rules exist within the System—the domain where the observer or decision-maker has agency[1][2].
• The Arbitrariness Test: Rules are “frozen accidents” of history or deliberate design choices[2][16]. If a constraint could have been otherwise—like driving on the right versus the left side of the road—it is a rule, not a law[5][17].
• The Function of Selection: Rules (or “controls”) are used to harness physical laws to achieve a specific function or purpose[10].
• The Symbolic Nature: Rules require a “code” or “language” to be executed[5][17]. They act as “context-dependent constraints” that link parts together through mutual dependence, like the rules of grammar[20][21].
Why the Distinction Matters
For an analyst, mistaking a Rule for a Law leads to “Analysis Paralysis” or a failure to see leverage points for change[22][23]. Conversely, mistaking a Law for a Rule leads to the “Environmental Fallacy”—attempting to “think away” hard physical constraints like geography or finite resources, which inevitably results in system collapse[24].
Does your current project feel like you are being blocked by Universal Laws that cannot be moved, or are you perhaps dealing with Local Rules that have simply been misidentified as immovable?
References
[1] 💬Environment.md [2] 💬Gists.md [3] 💬Gists.md [4] 💬Gists.md [5] 💬Keywords + Jargon.md [6] 💬Environment.md [7] 💬Gists.md [8] 💬Keywords + Jargon.md [9] 💬Keywords + Jargon.md [10] 💬Gists.md [12] 💬Keywords + Jargon.md [13] 💬Questions.md [14] 💬Questions.md [15] 💬Questions.md [16] 💬Questions.md [17] 💬How To Guides.md [20] 💬Keywords + Jargon.md [21] 💬Nutshell (Process).md [22] 💬Environment.md [23] 💬Environment.md [24] 💬Environment.md