VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Load Taxonomy — Maintenance / Replacement / Coordination / Complexity (Almost-Code Canonical)

Three students study around open books and worksheets in a shared classroom.

CANONICAL LAYER: Almost-Code
SPEC FAMILY: CivOS Core Physics
GLOBAL VERSION: AC.v1.0
STATUS: Active
SCOPE: A unified taxonomy of load types that drive drift, collapse, and recovery cost


0) Reader Contract

This page is specification, not commentary.

  • No persuasion.
  • No debate.
  • “Load” is a physical concept in CivOS.
  • Misclassified load leads to wrong repairs.

1) Entity

ENTITY: Load Taxonomy
TYPE: System load classification
ROLE: Identify what kind of burden is acting on HRL, RePOC, and pipelines
DEFINITION:
Load = any recurring or stochastic demand that consumes regenerative capacity
(time, attention, energy, coordination, replacement throughput).

2) Canonical Load Types (Locked)

LOAD TYPES (L):
L1 = Maintenance Load
L2 = Replacement Load
L3 = Coordination Load
L4 = Complexity Load
RULE:
Every failure must be traceable to one or more load types.

3) L1 — Maintenance Load

DEFINITION:
Maintenance Load = ongoing effort required to keep existing systems functional.
EXAMPLES:
- infrastructure upkeep
- routine operations
- basic healthcare delivery
- lesson preparation and marking
- equipment servicing
FAILURE MODE:
If maintenance load exceeds capacity:
- quality degrades
- errors accumulate
- system drifts into P1
MISDIAGNOSIS RISK:
Mistaking maintenance overload for “lack of motivation” or “poor culture”.

4) L2 — Replacement Load

DEFINITION:
Replacement Load = effort required to replace people, roles, skills, and parts
lost to attrition, failure, or obsolescence.
EXAMPLES:
- training new teachers/nurses/operators
- onboarding staff
- succession planning
- retraining after technology shifts
FAILURE MODE:
If replacement load is underfunded:
- Φ_out > Φ_in
- vacancy rises
- Civλ increases (pipeline thinning)
MISDIAGNOSIS RISK:
Covering vacancies with overtime (shifts load to L1, burns HRL).

5) L3 — Coordination Load

DEFINITION:
Coordination Load = effort required to align multiple agents, roles,
institutions, and decisions.
EXAMPLES:
- meetings and approvals
- compliance reporting
- cross-agency alignment
- handoffs and interfaces
FAILURE MODE:
If coordination load grows faster than execution capacity:
- decision latency rises
- binds drift
- people route around governance
MISDIAGNOSIS RISK:
Adding more rules to fix coordination problems (increases L3 further).

6) L4 — Complexity Load

DEFINITION:
Complexity Load = cognitive and operational burden created by system intricacy,
coupling, exception-handling, and non-linearity.
EXAMPLES:
- highly coupled systems
- many special cases
- fragile dependencies
- opaque processes
FAILURE MODE:
If complexity exceeds comprehension:
- errors become systematic
- recovery time explodes
- brittleness rises sharply
MISDIAGNOSIS RISK:
Blaming individuals for failures caused by system complexity.

7) Load Interaction Rules (Canonical)

INTERACTIONS:
- L4 increases L3 (complex systems need more coordination)
- L3 steals capacity from L1 and L2
- Underfunded L2 increases L1 via overtime
- Excess L1/L3 reduces buffer thickness
RULE:
Load types compound non-linearly.

8) Load vs Capacity Inequality (Local Form)

LOCAL STABILITY CONDITION:
Σ(L1..L4) ≤ Available Regenerative Capacity + Buffers
If violated persistently:
- Phase drops (P2→P1)
- Recovery windows vanish
- Collapse risk increases

9) Load Misallocation Anti-Patterns (δAd⁻)

ANTI-PATTERNS:
- pushing maintenance into heroics (burnout)
- hiding replacement gaps with overtime
- adding reporting to fix trust (coordination spiral)
- adding features without simplification (complexity explosion)

10) Load Reduction Strategies (Canonical)

10.1 Reduce L1 (Maintenance)

- simplify systems
- improve tooling
- remove non-essential tasks

10.2 Reduce L2 (Replacement)

- invest in pipelines (Education OS)
- shorten TTC
- improve retention

10.3 Reduce L3 (Coordination)

- simplify binds
- clarify authority
- reduce approval layers

10.4 Reduce L4 (Complexity)

- modularise systems
- remove exceptions
- standardise interfaces

11) Integration with Truncation & Stitching

TRUNCATION:
Often targets L3 and L4 first (freeze scope; simplify).
STITCHING:
Restores L2 capacity (replacement pipelines) and buffers,
then stabilises L1.

12) Mandatory Failure Mode Trace (Canonical)

FAILURE MODE TRACE (schematic):
System grows (capability ↑)
→ L4 rises (complexity)
→ L3 rises (coordination)
→ capacity diverted from L2 (replacement neglected)
→ vacancies grow; L1 shifts to overtime
→ buffers thin; recovery slows
→ small shock exceeds recovery window
→ PhaseDrop cascade (P2→P1→P0)

13) Canonical Claim Set (Frozen)

CLAIMS (frozen):
- Load has four canonical types: maintenance, replacement, coordination, complexity.
- Collapse often comes from load misclassification, not “lack of effort”.
- Replacement load (L2) neglect is a primary driver of Civλ.
- Complexity and coordination loads compound non-linearly.
- Correct repair requires reducing the right load type, not pushing harder.

END — Load Taxonomy Canonical Spec (AC.v1.0)

Recommended Internal Links (Spine)

Start Here: