1. Short Definition
Rule-Stacking Wall occurs when a system attempts to solve complexity by adding more rules after the rule system has already exceeded effective auditability.
At that point, additional rules increase hidden debt rather than coherence.
2. Canonical Pattern
Rules↑ while Au_eff↓ ⇒ H↑ + arbitrary enforcement↑Expanded:
X_c > Au_eff
+
Rules↑
⇒ interpretability↓
⇒ enforcement inconsistency↑
⇒ hidden debt↑Plain form:
More rules do not create coherence when the system can no longer understand or apply them coherently.
3. Mechanic Description
SCALE-013 is a specific failure mode of SCALE-012.
When a system experiences disorder, risk, ambiguity, conflict, or misuse, it often responds by adding rules.
This can work while the rule system remains interpretable.
But beyond a threshold, new rules make the system harder to understand, harder to apply, harder to challenge, harder to audit, and harder to repair.
The rule stack becomes a wall.
Symptoms include:
- exceptions multiply
- policy becomes self-conflicting
- enforcement becomes inconsistent
- affected nodes cannot understand outcomes
- operators rely on habit rather than clarity
- appeal pathways fail
- compliance becomes performative
- dashboards show order while actual coherence declines
- responsibility diffuses into procedure
- nobody can explain the whole system
This is especially important for AI governance, legal systems, institutional compliance, security policy, and large bureaucracies.
The rule-stacking wall is not anti-rule.
It is a warning that rules must remain auditable, interpretable, and repairable.
4. UTS Variable Mapping
| Variable | Role in SCALE-013 |
|---|---|
| O | Declines when rules no longer preserve coherent function |
| H | Rises through unresolved ambiguity and arbitrary outcomes |
| ε | Appears as appeals, disputes, contradictions, and enforcement failures |
| ι | Rises when more governance creates less coherence |
| Au | Falls when rules exceed interpretability |
| µᵢ | Meaning / legitimacy degrades when rules lose intelligibility |
| BΣ | Boundaries become inconsistent or selectively applied |
| K | Slack is consumed by navigating procedure |
| R | Repair fails when procedure blocks correction |
| Φ | Compliance metrics may improve while coherence falls |
5. Diagnostic Questions
- Are more rules being added to solve incoherence?
- Can operators explain the rule system clearly?
- Can affected nodes understand decisions?
- Are exceptions multiplying?
- Are rules contradicting each other?
- Is enforcement becoming inconsistent?
- Is compliance improving while legitimacy declines?
- Are appeals usable or blocked by complexity?
- Is responsibility hiding inside procedure?
- Would removing, clarifying, or consolidating rules increase coherence?
6. Failure Signatures
1. Rule Addition After Audit Failure
Au_eff already low + Rules↑ ⇒ H↑The system adds rules after it can no longer audit rules.
2. Exception Proliferation
Rules↑ ⇒ Exceptions↑ ⇒ X_c↑↑Each rule creates new edge cases.
3. Arbitrary Enforcement
X_c > Au_eff ⇒ enforcement variance↑Outcomes depend on interpretation rather than coherent rule logic.
4. Compliance-Coherence Split
Compliance↑ while O↓The system looks more governed while becoming less coherent.
5. Procedure Capture
procedure↑ + responsibility↓ ⇒ repair failure↑The process protects itself from correction.
7. Related Failure Modes
- rule-stacking wall
- compliance theater
- policy opacity
- arbitrary enforcement
- appeal collapse
- responsibility diffusion
- auditability collapse
- procedural capture
- hidden debt accumulation
- legitimacy decay
- AI policy incoherence
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| X_c | Rule / constraint complexity |
| Au_eff | Effective auditability |
| appeal_access_ratio | Whether decisions can be challenged |
| enforcement_variance | Consistency of application |
| exception_count | Rule stack fragmentation |
| R_eff | Capacity to repair bad outcomes |
| µᵢ | Meaning / legitimacy integrity |
| K / σ(t) | Slack required to navigate rules |
| H | Hidden debt from rule complexity |
| Φ_compliance | Compliance surface metric |
9. Restoration Implications
If SCALE-013 is active, restoration requires rule simplification and interpretability restoration.
Required actions:
- Stop adding rules as the default response.
- Map the existing rule stack.
- Identify contradictions and redundant constraints.
- Consolidate rules around higher-order principles.
- Reduce exception burden.
- Restore plain-language interpretability.
- Rebuild appeal and correction pathways.
- Clarify responsibility.
- Test whether rules reduce recurrence.
- Add new rules only if they increase auditability and coherence.
Core restoration rule:
Do not add rules to a system that has lost rule auditability.10. Compact Registry Entry
id: SCALE-013
name: "Rule-Stacking Wall"
family: "SCALE-C — Auditability and Observability Mechanics"
type: "complexity-failure-mechanic"
status: "draft-ready"
short_definition: "Rule-Stacking Wall occurs when adding more rules after interpretability has fallen below complexity reduces coherence and increases hidden debt."
canonical_pattern: "Rules↑ while Au_eff↓ ⇒ H↑ + arbitrary enforcement↑"
failure_signature: "X_c > Au_eff + Rules↑ ⇒ interpretability↓ + enforcement inconsistency↑ + hidden debt↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- X_c
- Au_eff
- appeal_access_ratio
- enforcement_variance
- exception_count
- R_eff
- µᵢ
- K
- σ(t)
- H
- Φ_compliance
related_failure_modes:
- compliance_theater
- policy_opacity
- arbitrary_enforcement
- appeal_collapse
- responsibility_diffusion
- auditability_collapse
- procedural_capture
- legitimacy_decay
restoration_implication: "Stop default rule addition, simplify and consolidate the rule stack, restore interpretability, rebuild appeals, and add rules only when they increase auditability."11. One-Line Canon
Rules stop repairing coherence once the system can no longer audit, interpret, or correct the rule stack.