GL-118 — Legibility

Open archive search
Archive registry entry

GL-118 — Legibility

Legibility is the condition of being understandable, traceable, and meaningfully inspectable without collapsing complexity into false simplicity.

draftid: GL-118version: 0.1.0updated: 2026-06-24
Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation
Online

The section has a stable overview route and basic reader context.

Technical Layer
Online

A deeper technical overview is available.

Registry
Current

194 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

1. Short Definition

Legibility is the condition of being understandable, traceable, and meaningfully inspectable without collapsing complexity into false simplicity.


2. Canonical Definition

In UTS, Legibility means a system can be read well enough for valid sensemaking, audit, correction, consent, governance, restoration, or time validation.

Legibility is not the same as simplicity.

A system can be simple-looking and illegible if the real causes, effects, boundaries, incentives, or repair paths are hidden.

Legibility asks:

textScroll
Can the relevant structure be understood without distortion?

Legibility supports auditability, but it also includes meaning clarity: the system must be understandable in a way that preserves the real relationships between state, cause, consequence, and repair.


3. Functional Role in UTS

Legibility supports:

  • truth reconstruction
  • governance
  • AI systems
  • public communication
  • contract validity
  • interface legitimacy
  • failure mode mapping
  • restoration design
  • consent
  • feedback integrity
  • basin transition

Legibility makes coherent participation possible.

Where legibility collapses, systems can become dependent on authority, guesswork, metrics, or narrative control.


4. Diagnostic Signatures

Legibility increasing

textScroll
Au↑
Au_eff↑
X_c manageable
cause visible
scope clear
meaning preserved
repair path visible

Legibility declining

textScroll
Au↓
Au_eff↓
X_c > Au_eff
scope blur↑
narrative substitution↑
H↑
O↓

False legibility

textScroll
clear dashboard
but hidden causality, hidden burden, or hidden repair path

This creates readable appearance without meaningful inspectability.


5. Canonical Distinctions

Legibility is not simplification

Simplification can improve or damage legibility depending on whether meaning is preserved.

Legibility is not transparency alone

Data may be visible while structure remains unreadable.

Legibility is not control

Making a system legible should not automatically authorize domination.

Legibility is not narrative clarity

A coherent story may hide incoherent structure.


6. U-Layer Mapping

TableScroll
U-LayerLegibility Expression
U0Substrate state and physical constraints can be understood.
U1Resource flows and burdens are visible.
U2Boundaries, permissions, contracts, consent, and exit are readable.
U3Execution behavior can be traced.
U4Labels, metrics, models, and narratives preserve meaning.
U5Timing and sequence are visible.
U6Field-level coherence can be assessed.
U7Memory and recurrence remain inspectable.
U8External forcing is distinguishable from internal causality.

7. Common Failure Patterns

TableScroll
Failure PatternDescription
ObfuscationStructure is hidden or made unreadable.
Paper CoherenceDocuments look coherent while reality is not.
Metric SubstitutionNumbers appear legible while real coherence is hidden.
Interface CaptureMediator controls what can be seen or verified.
Rule Stacking WallComplexity exceeds effective auditability.

8. Restoration Implications

Legibility restoration makes hidden structure readable enough for repair.

Typical sequence:

textScroll
Μ map unreadable region
→ restore Au
→ reduce X_c where possible
→ clarify scope and boundary
→ distinguish signal from narrative
→ expose repair path
→ Τ validate through recurrence

A system becomes more restorable as its real structure becomes more legible.


9. Machine-Readable Summary

yamlScroll
glossary_entry:
  id: "GL-126"
  term: "Legibility"
  symbols:
    - "Au"
    - "Μ"
  short_definition: "The condition of being understandable, traceable, and meaningfully inspectable without collapsing complexity into false simplicity."
  term_family: "Foundational System Terms"
  term_class:
    - "Core Concept"
    - "Sensemaking Condition"
    - "Auditability Support"
  diagnostic_positive:
    - "Au↑"
    - "Au_eff↑"
    - "X_c manageable"
    - "cause visible"
    - "scope clear"
    - "repair path visible"
  diagnostic_negative:
    - "Au↓"
    - "Au_eff↓"
    - "X_c > Au_eff"
    - "scope blur↑"
    - "narrative substitution↑"
    - "H↑"
  core_distinctions:
    - "Legibility is not simplification."
    - "Legibility is not transparency alone."
    - "Legibility is not control."
    - "Legibility is not narrative clarity."