---
schema_version: "1.0"
id: "GL-218"
title: "GL-218 — Legibility Restoration"
slug: "gl-218-legibility-restoration"
type: "glossary_term"
status: "draft"
version: "0.1.0"
last_updated: "2026-06-24"
summary: "Legibility Restoration is a restoration arc that makes hidden structure, causality, boundaries, basin geometry, responsibility, or repair pathways visible enough for coherent correction."
canonical_url: "/archive/glossary/registry/gl-218-legibility-restoration"
citation_id: "gl-218-legibility-restoration-v0-1-0"
canon:
tier: "registry"
state: "draft"
source: "UTS Glossary Simplified Registry"
source_id: "GL-218"
classification:
family: "Glossary"
module: "Restoration Terms"
module_group: "Reference Systems"
density: "Reference"
audience:
- "UTS readers"
- "researchers"
- "builders"
- "AI readers"
- "machine readers"
tags:
- "glossary"
- "registry"
- "gl-218"
- "legibility-restoration"
- "legibility"
- "restoration"
aliases:
- "Legibility Restoration"
- "Restoring legibility"
- "Structure legibility repair"
- "Causal legibility restoration"
related:
laws:
- "Temporal Audit Asymmetry"
- "Hidden Debt Return Law"
invariants:
- "O ≠ Φ"
operators:
- "Μ"
- "Ξ"
- "Au"
- "Π"
- "ℛ"
- "Τ"
gates:
- "Au-Actuation"
- "FI-Gate"
- "HR-Gate"
- "R Sufficiency"
- "Τ Validation"
diagnostics:
- "Au"
- "Au_eff"
- "X_c(t)"
- "H"
- "O"
- "µᵢ"
- "FI"
failure_modes:
- "Obfuscation"
- "Auditability Collapse"
- "Paper Coherence"
- "Interface Capture"
- "Rule Stacking Wall"
restoration_arcs:
- "Legibility Restoration"
- "Truth Reconstruction"
- "Temporal Proof Arc"
- "Basin Aware Restoration"
modules:
- "glossary"
terms:
- "Legibility"
- "Auditability"
- "Causal Traceability"
- "Truth"
- "Observability"
navigation:
order: 218
parent: "glossary"
visible: true
provenance:
created_from: "glossary-simplified-continuation"
source_thread: "GLOSSARY-REFACTOR.md"
source_file: "glossary-raw.docx"
notes: "Continued Restoration Terms sequence."
entry:
term_id: "GL-218"
term: "Legibility Restoration"
term_class:
- "Restoration Term"
- "Auditability Repair"
- "Sensemaking Restoration"
symbols:
- "Au"
- "Μ"
---1. Short Definition
Legibility Restoration is a restoration arc that makes hidden structure, causality, boundaries, basin geometry, responsibility, or repair pathways visible enough for coherent correction.
2. Canonical Definition
In UTS, Legibility Restoration repairs the system’s ability to understand itself.
It is used when the system cannot repair because it cannot see enough of the relevant structure.
Legibility Restoration does not require making everything visible.
It requires making the coherence-relevant structure visible.
Canonical sequence:
Μ map unreadable region
→ restore Au
→ reduce X_c where needed
→ clarify scope and boundary
→ distinguish signal from narrative
→ expose repair path
→ Τ validate through recurrenceLegibility Restoration often precedes deeper repair because a system cannot repair what remains structurally unreadable.
3. Functional Role in UTS
Legibility Restoration supports:
- truth reconstruction
- auditability restoration
- governance repair
- AI decision review
- contract repair
- interface legitimacy
- basin-aware restoration
- justice repair
- security repair
- recurrence prevention
It converts opacity into repairable structure.
4. Diagnostic Signatures
Legibility Restoration active
Au↑
Au_eff↑
X_c manageable
cause-path visible
scope clarified
repair path visible
H mappedLegibility still insufficient
data visible
but cause, responsibility, or repair path remains hiddenLegibility validated
affected nodes can understand pathway
repair becomes executable
recurrence decreases
O↑ over time5. Canonical Distinctions
Legibility Restoration is not disclosure dump
More information can increase opacity if structure remains unreadable.
Legibility Restoration is not surveillance
It restores coherence-relevant traceability, not total control visibility.
Legibility Restoration is not simplification alone
Simplification must preserve meaning and causality.
Legibility Restoration is not blame assignment
It reconstructs structure before consequence allocation.
6. U-Layer Mapping
| U-Layer | Legibility Restoration Expression |
|---|---|
| U0 | Material or substrate state becomes inspectable. |
| U1 | Resource flows and burdens become visible. |
| U2 | Boundaries, permissions, contracts, and consent become readable. |
| U3 | Execution paths become traceable. |
| U4 | Labels, metrics, and narratives are checked against reality. |
| U5 | Timing and sequence are reconstructed. |
| U6 | Field effects become attributable. |
| U7 | Memory and recurrence are restored as evidence. |
| U8 | External forcing is distinguished from internal cause. |
7. Failure Patterns Addressed
| Failure Pattern | Description |
|---|---|
| Obfuscation | Relevant structure is hidden. |
| Auditability Collapse | Cause and consequence cannot be traced. |
| Paper Coherence | Documents hide operational incoherence. |
| Interface Capture | Mediator controls what can be verified. |
| Rule Stacking Wall | Constraint complexity exceeds auditability. |
8. Restoration Implications
Legibility Restoration is often the first repair needed when truth is unclear.
Typical sequence:
Ψ receive confusion or contradiction
→ Μ map illegible domain
→ recover records and signals
→ restore Au_eff
→ reduce unnecessary complexity
→ clarify responsibility and repair path
→ ℛ repair once structure is visible
→ Τ validate recurrence reductionLegibility is restored when the system can see enough to correct itself.
9. Machine-Readable Summary
glossary_entry:
id: "GL-218"
term: "Legibility Restoration"
symbols:
- "Au"
- "Μ"
short_definition: "A restoration arc that makes hidden structure, causality, boundaries, basin geometry, responsibility, or repair pathways visible enough for coherent correction."
term_family: "Restoration Terms"
term_class:
- "Restoration Term"
- "Auditability Repair"
- "Sensemaking Restoration"
canonical_sequence:
- "Μ map unreadable region"
- "restore Au"
- "reduce X_c where needed"
- "clarify scope and boundary"
- "distinguish signal from narrative"
- "expose repair path"
- "Τ validate through recurrence"
diagnostic_positive:
- "Au↑"
- "Au_eff↑"
- "X_c manageable"
- "cause-path visible"
- "scope clarified"
- "repair path visible"
- "H mapped"
validation:
- "affected nodes can understand pathway"
- "repair becomes executable"
- "recurrence decreases"
- "O↑ over time"