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.

Phase×Zoom Ladder (PZL) — Canonical Navigation Ladder (Almost-Code)

CANONICAL LAYER: Almost-Code
SPEC FAMILY: Civilisation OS (CivOS)
GLOBAL VERSION: AC.v1.0
STATUS: Active
SCOPE: A single ladder for diagnosing, routing, and repairing systems across scale


0) Reader Contract

This page is specification, not commentary.

  • No persuasion.
  • No debate.
  • PZL is the canonical ladder used across all CivOS sub-OSes.
  • PZL exists to make drift and repair navigable.

1) Entity

ENTITY: PZL
EXPANSION: Phase×Zoom Ladder
TYPE: Navigation and routing standard
DEFINITION:
PZL = a canonical ladder mapping Phase reliability (P0–P3)
across Zoom scope (Z0–Z6) for diagnosis, routing, and repair.

2) Locked Axes

2.1 Phase Axis (Reliability Under Load)

P0 = non-functional / collapse
P1 = fragile / unstable (fails under variation/time pressure)
P2 = functional under normal load
P3 = robust under variation + stress + time pressure

2.2 Zoom Axis (Structural Scope)

Z0 = individual / role execution
Z1 = household / micro-team
Z2 = institution / organisation
Z3 = city / society / nation
Z4 = regional / multi-nation system
Z5 = country surface directory indexing layer
Z6 = supranational organisations / standards layer

3) Canonical PZL Grid (Interpretation Rules)

PZL is a grid of states, but interpretation is directional.

DIRECTIONAL RULES:
- Failures usually originate at Z0/Z2 and propagate upward if unrepaired.
- Repair is cheapest at lower Z and earlier time.
- P-state changes are not “labels”; they are control decisions.

4) PZL State Encoding (Standard)

ENCODING:
PZ = P{0..3} × Z{0..6}
Examples:
P3Z0 = role-level robustness under variation
P2Z2 = organisation-level functional under normal load
P1Z3 = nation-level fragile under shocks
P0Z1 = household-level collapse
RULE:
Every diagnosis must be reducible to one or more PZ codes.

5) Multi-Node Reality (Systems are not single PZ points)

SYSTEM PROFILE:
A real system is a distribution across PZ states, not a single point.
Representation:
Profile = { (PZ_i, weight_i) }
RULE:
Core pipelines must be at higher PZ than peripheral lanes.

6) Ladder Use Cases (Canonical)

6.1 Diagnosis

Goal: locate where reliability fails and at what zoom.
Output: set of PZ states + failure traces.

6.2 Routing

Goal: decide which repair lane and what control action is required.
Output: repair path (Z and P transitions) + stop-loss rules.

6.3 Upgrade Sequencing

Goal: raise robustness without triggering collapse.
Output: safe upgrade route: P1→P2→P3 with buffers maintained.

7) Upgrade Rules (Phase Movement Constraints)

PHASE UPGRADE RULES:
P1→P2 requires stability under normal load.
P2→P3 requires stability under variation + time pressure.
Forbidden:
Claiming P3 based on signal-only performance (false competence).
ZOOM UPGRADE RULE:
Do not scale upward (Z2→Z3) until lower-Z reliability is stable.
Scaling multiplies load and coupling.

8) Downgrade Rules (Safety Routing)

PHASE DOWNGRADE RULES:
If repeated failures occur under normal load → treat as P1
If failures occur under reduced load / basic conditions → treat as P0
ZOOM DOWNGRADE RULE:
If Z3 system fails, route repairs to Z2 and Z0 where causes live.
Avoid “top-only” fixes that ignore pipeline reality.

9) PZL Repair Routes (Standard Patterns)

9.1 The “Bottom Repair” Route (Most common)

P1Z3 symptom
→ diagnose causes at Z2/Z0
→ repair pipelines at Z0/Z2
→ restore P2Z2
→ restore P2Z3
→ build buffers and raise P3 where needed

9.2 The “Stop-Loss” Route (Emergency)

P1Z2 drift accelerating OR COEE risk rising
→ truncation (stop-loss)
→ protect core nodes/binds
→ stitch to restore P2 minimum

9.3 The “Upgrade Without Brittleness” Route

Maintain P2 while expanding capability
→ add redundancy lanes (reduce concentration)
→ raise P3 in core pipelines first
→ scale outward second

10) PZL + RePOC Integration (What gets protected)

PROTECTION RULE:
Core RePOC organs must maintain P2 minimum at Z2/Z3
and must achieve P3 in key binds and core roles where variation is unavoidable.
RePOC priority order under stress (typical):
Governance + Security + Supply continuity
→ Healthcare
→ Education pipeline continuity
→ Upgrade layers (later)

11) PZL + Civλ / CivY&Y Integration (Stability control)

If PZ drift is persistent:
- Civλ is rising (pipelines thinning / extinction risk)
- CivY&Y is insufficient (repair + replacement throughput too low)
CONTROL:
Use truncation to create a stitching window,
then rebuild pipelines to restore inequality:
CivY&Y(t) ≥ Civλ · C(t)

12) Mandatory Failure Mode Trace (Canonical)

FAILURE MODE TRACE (schematic):
System scales upward (Z2→Z3) without ensuring P3Z0/P2Z2 robustness
→ coupling and coordination load multiplies
→ hidden fragility accumulates (P2 appearance, P1 reality)
→ variation spike arrives (time pressure / shocks)
→ P2Z3 collapses to P1Z3
→ top-only fixes fail (causes live at Z0/Z2)
→ no stop-loss; COEE risk rises
→ P1Z3 → P0Z3 cascade possible

13) Canonical Claim Set (Frozen)

CLAIMS (frozen):
- PZL is the canonical navigation ladder for CivOS (P0–P3 × Z0–Z6).
- Systems are distributions across PZ states; core pipelines require higher reliability.
- Upgrade requires proven robustness under variation; downgrade is safety routing.
- Most repairs must route downward (Z3 symptoms → Z2/Z0 causes).
- Scaling without lower-Z robustness creates brittleness and sudden phase collapse.

END — PZL Canonical Spec (AC.v1.0)

Recommended Internal Links (Spine)

Start Here: