0. Plain Statement

Coherence precedes optimization.

Plain-language version:

A system should not optimize for speed, power, profit, efficiency, growth, compliance, visibility, or performance if doing so degrades the coherence of the system. Optimization is valid only when it preserves or increases coherence.

1. Formal Definition

The Coherence Priority Law states that optimization must remain subordinate to coherence.

A system may improve a visible success proxy while damaging identity, meaning, boundary integrity, auditability, compatibility, slack, restoration capacity, or long-term functional integrity. When this occurs, the system is not becoming more coherent. It is entering pseudo-coherence.

This law establishes the ordering rule for all UTS design, diagnosis, governance, security, AI, restoration, and scaling work:

Coherence first.
Optimization second.

Optimization is admissible only when it does not degrade the structural conditions that allow the system to remain coherent across time, stress, transformation, and scale.

2. Canonical Form

O is prior to Φ

Expanded canonical form:

Φ may increase only when O is preserved or increased

Failure expression:

Φ↑ while O↓ ⇒ ι↑

Related variables:

O, Φ, H, ι, Au, R, µᵢ, BΣ, K

Where:

3. Core Mechanism

The Coherence Priority Law usually unfolds through one of two pathways.

Coherent pathway

O preserved
→ Φ optimized within coherence constraints
→ H bounded
→ ι remains low
→ R remains available
→ system scales or improves without hollowing

In this pathway, optimization improves the system without damaging its deeper integrity.

Inverted pathway

Φ prioritized
→ O treated as secondary
→ Au narrows
→ BΣ / µᵢ / K / R degrade
→ H accumulates
→ ι rises
→ pseudo-coherence forms

In this pathway, optimization produces visible improvement while weakening the system’s ability to remain coherent.

The most common mechanism is proxy substitution:

visible success proxy replaces coherence as the steering target

Once the proxy becomes the target, the system may begin sacrificing the conditions that originally made the proxy meaningful.

4. When This Law Applies

This law applies whenever a system is optimizing for any visible or measurable success signal.

Common optimization targets include:

• efficiency
• speed
• profit
• growth
• scale
• compliance
• security metrics
• benchmark performance
• institutional stability
• public reputation
• user engagement
• throughput
• productivity
• biological symptom reduction
• social approval
• symbolic certainty
• policy simplicity
• control density

The law is especially important when:

Φ is rising faster than O can be validated

or when:

optimization pressure increases while Au, R, BΣ, µᵢ, or K decrease

Typical domains:

5. When This Law Does Not Apply

This law should not be used to reject optimization itself.

Optimization is valid when it:

• preserves coherence;
• increases coherence;
• improves capacity without hidden debt accumulation;
• increases auditability;
• strengthens boundary integrity;
• improves restoration capacity;
• preserves meaning and agent integrity;
• increases slack or compatibility;
• reduces recurrence.

This law is not anti-efficiency, anti-growth, anti-performance, or anti-scaling.

It only rejects optimization that subordinates coherence to proxy success.

False-positive cases:

Important distinction:

A proxy is useful when it serves coherence. It becomes dangerous when it replaces coherence.

6. Diagnostic Signature

The basic diagnostic signature is:

Φ↑ while O↓ or unverifiable ⇒ proxy-coherence divergence

A stronger warning signature:

Φ↑
Au↓
R↓
BΣ↓
µᵢ↓
K↓
H↑
ι↑

Common indicators:

Additional diagnostics:

7. Failure Pattern

If ignored, this law tends to produce pseudo-coherence.

General failure pathway:

Optimization target selected
→ proxy becomes steering priority
→ coherence constraints treated as friction
→ boundary / meaning / audit / restoration conditions degrade
→ visible success persists or improves
→ hidden debt accumulates
→ inversion stabilizes
→ collapse or legitimacy shock appears late

Common failure modes:

• Pseudo-Coherence — the system appears ordered while coherence declines.
• Success Proxy Capture — the proxy becomes the target.
• Goodhart Collapse — optimization around a metric destroys the metric’s meaning.
• Hidden Debt Accumulation — unresolved incoherence is displaced or deferred.
• Silent Extraction — coherence is drained while visible error remains low.
• Metric Substitution — measurable success replaces real system health.
• Pseudo-Restoration — optics improve while repair does not occur.
• Optimization Capture — all system decisions are routed through performance pressure.

Compact failure signature:

Φ↑ + Au↓ + H↑ + ι↑ + R↓ ⇒ pseudo-coherence risk

8. Restoration Implications

Restoration requires returning the system to coherence-first ordering.

The first question is not:

How do we improve Φ?

The first question is:

What must be preserved for O to remain real?

Restoration priorities:

1. Re-establish coherence as the steering target.
2. Audit the proxy.
3. Identify what the optimization process has degraded.
4. Surface hidden debt created by proxy prioritization.
5. Restore damaged boundaries, meaning, slack, auditability, or repair capacity.
6. Prevent re-optimization until coherence conditions are revalidated.
7. Time-validate the repair.

Relevant restoration arcs:

Minimal restoration sequence:

Pause optimization pressure
→ restore auditability
→ compare Φ movement against O movement
→ identify hidden debt
→ repair damaged coherence conditions
→ reduce recurrence
→ resume only coherence-preserving optimization

Temporal validation requirement:

H(t+Δt) ≤ H(t)
ι(t+Δt) ≤ ι(t)
Au stable or rising
R stable or rising
BΣ intact
µᵢ preserved
O preserved or improved

9. Design Rule

Never optimize a proxy beyond the system’s ability to preserve coherence.

Operational design requirements:

• Define what coherence means before selecting success metrics.
• Treat metrics as diagnostic aids, not final truth.
• Require auditability for all optimization processes.
• Track hidden debt as a first-class design concern.
• Preserve boundary integrity under performance pressure.
• Preserve meaning and agent integrity under scale.
• Maintain restoration capacity proportional to optimization intensity.
• Stop or slow optimization when coherence indicators degrade.
• Validate success across time, not only at the moment of measurement.

Avoid:

• optimizing what is easiest to measure;
• treating efficiency as automatically coherent;
• scaling before restoration;
• increasing throughput while reducing auditability;
• improving optics while suppressing debt;
• using compliance as a substitute for legitimacy;
• using symptom reduction as a substitute for recovery;
• using benchmark gains as a substitute for AI safety;
• treating local success as global alignment.

10. Cross-Scale Expressions

11. Examples

Example A — AI Benchmark Optimization

Scenario:

An AI system improves benchmark scores while becoming harder to audit, more difficult to appeal, less transparent to affected users, and more dependent on hidden classification rules.

Law expression:

Φ_benchmark↑ while Au↓ and BΣ↓ ⇒ ι↑

Interpretation:

The system is not necessarily becoming safer or more coherent. It may be optimizing a visible proxy while degrading the conditions required for trustworthy operation.

Example B — Institutional Compliance

Scenario:

An institution reports improved compliance metrics, but affected people cannot understand decisions, appeal outcomes, or trace responsibility.

Law expression:

Φ_compliance↑ while Au↓ and R↓ ⇒ H↑

Interpretation:

Compliance improvement is not enough. If auditability and repair capacity degrade, the institution is generating hidden debt.

Example C — Economic Growth

Scenario:

Profit increases while circulation weakens, workers lose slack, infrastructure maintenance is deferred, and repair costs are pushed into the future.

Law expression:

Φ_profit↑ while O↓ and H↑ ⇒ pseudo-coherence

Interpretation:

The economy may appear successful while becoming less coherent. The visible profit signal is not sufficient to validate the system.

Example D — Biological Symptom Suppression

Scenario:

A symptom improves temporarily, but the underlying system loses resilience, recovery capacity, or tolerance.

Law expression:

ε↓ or Φ_health↑ while R↓ and τ_m↑ ⇒ false recovery risk

Interpretation:

Observable improvement does not prove restoration. Recovery requires coherence, not only symptom reduction.

Example E — Project Delivery Velocity

Scenario:

A development team ships faster while documentation, review, testing, architecture quality, and maintainability degrade.

Law expression:

Φ_velocity↑ while Au↓ and R↓ ⇒ H↑

Interpretation:

The team is converting technical coherence into short-term throughput. Hidden debt will return as brittleness, defects, or slowdown.

12. Relationship to Nearby Laws

Aliases folded into this law:

• Coherence Priority Law
• Objective Mixing Law
• Coherence-Preserving Optimization Rule

Deduplication note:

This law should remain the root priority law. Domain-specific versions should be created only when they add distinct diagnostic or design utility. Otherwise, they should be treated as expressions of LAW-001 or LAW-003.

13. Operator Mapping

Coherent operator sequence:

Θ → Γ(coherence-aware classification) → Π(coherence-preserving constraint) → optimization within Σ → ℛ if debt appears

Inverted operator sequence:

Γ(proxy selection) → Φ optimization → Π retrofits justification → Au↓ → H↑ → ι↑

14. Machine-Readable Summary

id: "LAW-001"
name: "Coherence Priority Law"
type: "law"
status: "draft"
family:
  - "Core Coherence Laws"
summary: "Coherence precedes optimization."
canonical_statement: "Coherence precedes optimization."
canonical_form: "O is prior to Φ"
failure_form: "Φ↑ while O↓ ⇒ ι↑"
variables:
  primary:
    - "O"
    - "Φ"
    - "ι"
  secondary:
    - "H"
    - "Au"
    - "R"
    - "µᵢ"
    - "BΣ"
    - "K"
diagnostics:
  - "Coherence"
  - "Hidden Debt"
  - "Inversion Index"
  - "Effective Auditability"
  - "Proxy-Coherence Divergence"
  - "Restoration Capacity"
  - "Boundary Integrity"
  - "Goodhart Risk"
failure_modes:
  - "Pseudo-Coherence"
  - "Success Proxy Capture"
  - "Goodhart Collapse"
  - "Hidden Debt Accumulation"
  - "Silent Extraction"
  - "Optimization Capture"
  - "Metric Substitution"
restoration_arcs:
  - "Auditability Restoration"
  - "Boundary Reconstitution"
  - "Slack Regeneration"
  - "Origin-Layer Repair"
  - "Restoration Capacity Rebuild"
  - "Temporal Validation"
related_laws:
  - "LAW-003"
  - "LAW-004"
  - "LAW-016"
  - "LAW-021"
  - "LAW-050"
  - "LAW-064"
  - "LAW-065"
  - "LAW-077"
related_invariants:
  - "INV-001"
  - "INV-004"
operator_sequence:
  coherent:
    - "Θ"
    - "Γ"
    - "Π"
    - "Σ"
    - "ℛ"
  inverted:
    - "Γ"
    - "Φ"
    - "Π"
    - "Au↓"
    - "H↑"
    - "ι↑"
aliases:
  - "Coherence Priority Law"
  - "Objective Mixing Law"
  - "Coherence-Preserving Optimization Rule"
deduplication_note: "Root priority law. Domain expressions should be folded here unless they add unique diagnostic or design value."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-001 — Coherence Priority Law

Coherence precedes optimization.

Plain meaning:

Optimization is valid only when it preserves or increases coherence. If visible success improves while coherence conditions degrade, the system is entering pseudo-coherence.

Canonical form:

O is prior to Φ

Failure form:

Φ↑ while O↓ ⇒ ι↑

Primary variables:

O, Φ, H, ι, Au, R, µᵢ, BΣ, K

Diagnostic signature:

Visible success rises while auditability, restoration capacity, boundary integrity, meaning integrity, slack, or coherence decline.

Failure risk:

Pseudo-coherence, success proxy capture, hidden debt accumulation, Goodhart collapse, silent extraction.

Restoration priority:

Restore coherence as the steering target, audit the proxy, surface hidden debt, repair degraded coherence conditions, and time-validate before resuming optimization.

16. Source Status

This entry was expanded from the current Laws Technical Registry source excerpt. It preserves the core canonical statement, canonical form, related variables, and aliases while adding diagnostic, restoration, design, operator, and cross-scale structure for registry use.

17. Source Excerpt

Coherence precedes optimization.

Optimization is valid only when it preserves or increases coherence.

If visible success improves while identity, meaning, boundary integrity, auditability, compatibility, or restoration capacity degrade, the system is entering pseudo-coherence.

Canonical form:

O is prior to Φ

Related variables:

O, Φ, H, ι, Au, R, µᵢ, BΣ

Aliases folded into this law:

• Coherence Priority Law
• Objective Mixing Law
• Coherence-Preserving Optimization Rule