1. Short Definition
Interface Legitimacy is the condition under which an interface remains auditable, revocably consented, compatibility-verified, scope-bound, and restoration-capable.
2. Canonical Definition
In UTS, Interface Legitimacy determines whether an interface can validly mediate signal, permission, representation, action, access, obligation, or meaning.
An interface is legitimate only when it preserves coherence for the systems it connects.
Minimum validity conditions:
Au sufficient
BΣ intact
scope clear
consent revocable
Λ > 0
FI protected
R available
Τ validation activeIf these conditions fail, the interface may still function technically while becoming coherence-invalid.
3. Functional Role in UTS
Interface Legitimacy is essential for:
- AI systems
- platform governance
- contracts
- civic systems
- institutional intake
- medical interfaces
- data access
- public communication
- justice pathways
- restoration systems
- human-machine interaction
It prevents an interface from becoming a hidden authority layer that shapes outcomes without audit, consent, or repair.
4. Diagnostic Signatures
Interface legitimacy preserved
Au↑
BΣ intact
scope clear
consent revocable
Λ > 0
FI intact
R available
O↑ or stableInterface legitimacy failing
Au↓
BΣ↓
scope drift↑
consent invalid
Λ untested
FI failure
repair path absent
H↑Illegitimate interface capture
interface controls reality access
while avoiding audit, revocation, or repair5. Canonical Distinctions
Interface Legitimacy is not usability
An interface can be easy to use while coherence-invalid.
Interface Legitimacy is not popularity
Adoption does not prove validity.
Interface Legitimacy is not technical functionality
A working interface may still distort meaning, consent, or feedback.
Interface Legitimacy is not institutional authority
Authority does not replace auditability, consent, compatibility, or repair.
6. U-Layer Mapping
| U-Layer | Interface Legitimacy Expression |
|---|---|
| U0 | Contact surface does not damage substrate integrity. |
| U1 | Resource burdens are visible and sustainable. |
| U2 | Consent, permission, scope, boundaries, and exit are valid. |
| U3 | Runtime behavior matches legitimate interface claims. |
| U4 | Labels, metrics, and representations remain truthful. |
| U5 | Timing, notification, review, and revocation are valid. |
| U6 | Field coherence improves or is protected. |
| U7 | Logs, history, and recurrence support accountability. |
| U8 | External pressure does not justify hidden capture. |
7. Common Failure Patterns
| Failure Pattern | Description |
|---|---|
| Interface Capture | The interface controls access, verification, timing, or representation. |
| Consent Theater | Interface records consent without valid boundary conditions. |
| Auditability Collapse | Interface effects cannot be traced. |
| Metric Substitution | Interface metrics replace coherence. |
| Repair Path Absence | Harm or error has no valid pathway for correction. |
8. Restoration Implications
Restoring Interface Legitimacy requires rebuilding the interface as a valid coherence surface.
Typical sequence:
Μ map interface power
→ restore Au
→ restore BΣ
→ clarify scope
→ make consent revocable
→ test Λ
→ protect FI
→ provision R
→ Τ validate effects over timeAn interface is legitimate when it can mediate relation without hiding power, suppressing signal, invalidating consent, or blocking repair.
9. Machine-Readable Summary
glossary_entry:
id: "GL-124"
term: "Interface Legitimacy"
symbols:
- "Au"
- "BΣ"
- "Λ"
- "R"
short_definition: "The condition under which an interface remains auditable, revocably consented, compatibility-verified, scope-bound, and restoration-capable."
term_family: "Foundational System Terms"
term_class:
- "Core Concept"
- "Validity Condition"
- "Governance Primitive"
validity_conditions:
- "Au sufficient"
- "BΣ intact"
- "scope clear"
- "consent revocable"
- "Λ > 0"
- "FI protected"
- "R available"
- "Τ validation active"
diagnostic_negative:
- "Au↓"
- "BΣ↓"
- "scope drift↑"
- "consent invalid"
- "FI failure"
- "repair path absent"
core_distinctions:
- "Interface Legitimacy is not usability."
- "Interface Legitimacy is not popularity."
- "Interface Legitimacy is not technical functionality."
- "Interface Legitimacy is not institutional authority."Continuing from the uploaded glossary source material, here is the next batch: GL-125 → GL-129.