1. Short Definition
U1 Budget Scaling Rule means that a system cannot increase demand coherently unless its usable budgets increase with that demand.
Budgets include not only money, but every resource required to act, inspect, repair, and adapt.
2. Canonical Pattern
U1 budget < scaling demand ⇒ compression cascadeExpanded:
demand↑
+
energy / time / attention / labor / material budget insufficient
⇒ slack↓
⇒ compression↑
⇒ repair capacity↓
⇒ coherence risk↑Plain form:
Demand without budget becomes compression.
3. Mechanic Description
SCALE-064 defines the U1 scaling constraint.
U1 is the power and budget layer. It includes the resources the system can spend to operate, respond, inspect, repair, and adapt.
U1 budgets may include:
- time
- attention
- energy
- labor
- money
- compute
- staffing
- materials
- bandwidth
- logistics
- review capacity
- repair time
- cognitive load
- biological recovery
- institutional capacity
- operational reserves
Scaling increases demand on these budgets.
If demand rises without corresponding budget growth, the system compresses.
This produces:
- rushed decisions
- degraded auditability
- lower classification resolution
- reduced maintenance
- weaker restoration
- boundary strain
- hidden labor
- forced choices
- backlog growth
- stress propagation
- delayed response
- recurrence
This rule is central because many systems attempt to scale obligations without scaling actual support capacity.
They add scope, rules, users, cases, responsibilities, or performance targets while leaving budgets flat.
That creates hidden debt.
4. UTS Variable Mapping
| Variable | Role in SCALE-064 |
|---|---|
| O | Declines when budgets cannot support coherent demand |
| H | Rises through deferred work, hidden labor, and repair backlog |
| ε | Appears as delay, errors, overload, or failure |
| ι | Rises when obligations expand while capacity does not |
| Au | Auditability requires time, attention, and resource budget |
| µᵢ | Meaning / legitimacy degrades when impossible demands persist |
| BΣ | Boundaries fail when budgets cannot regulate flow |
| K | Slack collapses when budgets are fully consumed |
| R | Restoration capacity depends on protected repair budgets |
| Φ | Performance pressure often raises demand without raising budget |
5. Diagnostic Questions
- What demand is increasing?
- Which U1 budgets are required to support it?
- Are budgets increasing with demand?
- Is hidden labor filling the gap?
- Is auditability being sacrificed due to resource shortage?
- Is restoration time protected?
- Are backlogs growing?
- Are boundaries failing because intake exceeds budget?
- Is the system relying on unpaid, invisible, or future capacity?
- Should scope be reduced until budgets scale?
6. Failure Signatures
1. Demand-Budget Gap
Scaling demand↑ while U1 budget flat/↓The system is asked to do more without more capacity.
2. Hidden Labor Compensation
budget_gap↑ ⇒ invisible_labor↑Unseen nodes absorb the missing budget.
3. Audit Budget Collapse
time / attention budget↓ ⇒ Au_eff↓The system lacks resources to inspect itself.
4. Restoration Budget Collapse
repair_time↓ ⇒ R_eff↓ ⇒ H↑Repair capacity is consumed by ongoing demand.
5. Backlog Growth
demand > throughput_budget ⇒ backlog↑Unprocessed burden accumulates.
7. Related Failure Modes
- budget compression
- hidden labor burden
- restoration starvation
- auditability collapse
- backlog accumulation
- boundary overload
- silent extraction
- zero-slack collapse
- capacity collapse
- pseudo-scaling
- forced choice
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| U1_budget | Available usable budget |
| scaling_demand | Added demand from scale |
| budget_gap | Difference between demand and budget |
| hidden_labor_index | Invisible labor absorbing the gap |
| repair_time | Budget reserved for restoration |
| audit_time | Budget reserved for auditability |
| backlog_size | Accumulated unprocessed load |
| σ(t) | Slack remaining |
| R_eff | Restoration capacity |
| Au_eff | Auditability capacity |
9. Restoration Implications
If SCALE-064 is active, restoration requires budget alignment.
Required actions:
- Identify which budgets are constrained.
- Compare scaling demand to usable budget.
- Reduce scope or load if budget cannot increase.
- Surface hidden labor.
- Protect audit budget.
- Protect repair budget.
- Increase staffing, time, compute, money, or logistical capacity where needed.
- Reduce nonessential demand.
- Rebuild slack.
- Resume scaling only when budgets exceed demand with margin.
Core restoration rule:
Do not scale demand without scaling the budget that carries it.10. Compact Registry Entry
id: SCALE-064
name: "U1 Budget Scaling Rule"
family: "SCALE-L — U-Layer Scaling Mechanics"
type: "budget-power-scaling-constraint"
status: "draft-ready"
short_definition: "A system cannot increase demand coherently unless its usable budgets increase with that demand."
canonical_pattern: "U1 budget < scaling demand ⇒ compression cascade"
failure_signature: "demand↑ + energy/time/attention/labor/material budget insufficient ⇒ slack↓ + compression↑ + repair capacity↓ + coherence risk↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- U1_budget
- scaling_demand
- budget_gap
- hidden_labor_index
- repair_time
- audit_time
- backlog_size
- σ(t)
- R_eff
- Au_eff
related_failure_modes:
- budget_compression
- hidden_labor_burden
- restoration_starvation
- auditability_collapse
- backlog_accumulation
- boundary_overload
- silent_extraction
- zero_slack_collapse
- capacity_collapse
restoration_implication: "Align demand with usable budget, surface hidden labor, protect audit and repair budgets, reduce nonessential load, rebuild slack, and scale only with margin."11. One-Line Canon
Demand without budget becomes compression, and compression becomes hidden debt.