1. Short Definition
Dominance is power-based control over a field, node, system, resource, narrative, interface, or decision surface; dominance is not coherence.
2. Canonical Definition
In UTS, Dominance occurs when a system’s ability to shape outcomes exceeds the corrective capacity, agency, auditability, or boundary integrity of other affected nodes.
Dominance may produce visible order, compliance, silence, efficiency, or apparent stability.
But dominance does not prove coherence.
Canonical distinction:
dominance ≠ coherenceDominance becomes incoherent when power replaces feedback, consent, compatibility, truth, or restoration.
It can suppress visible error while increasing hidden debt.
3. Functional Role in UTS
Dominance helps diagnose systems where power is mistaken for validity.
It appears in:
- institutions
- governance
- markets
- platforms
- AI systems
- security systems
- contracts
- discourse environments
- workplaces
- legal systems
- interface control
Dominance is especially dangerous when it controls the channels through which its own legitimacy would be evaluated.
4. Diagnostic Signatures
Dominance increasing
control over field↑
exit cost↑
alternative pathways↓
Au asymmetry↑
BΣ stress↑
Φ protected
H↑Coherence-valid authority
power scoped
Au↑
BΣ intact
feedback protected
R provisioned
MS symmetry preserved
O↑Dominance inversion
visible order↑
while agency↓ + H↑ + O↓This indicates power replacing coherence.
5. Canonical Distinctions
Dominance is not authority
Authority can be coherence-valid when scoped, auditable, accountable, and repair-capable.
Dominance is not governance
Governance coordinates constraint, selection, and restoration.
Dominance controls a field.
Dominance is not security
Security preserves coherence under forcing.
Dominance may suppress signals and create fragility.
Dominance is not legitimacy
Power can compel recognition without earning legitimacy.
6. U-Layer Mapping
| U-Layer | Dominance Expression |
|---|---|
| U0 | Material or physical capacity overwhelms alternatives. |
| U1 | Resource concentration creates dependency. |
| U2 | Boundaries, contracts, and permissions favor the dominant node. |
| U3 | Execution pathways are controlled by one actor or structure. |
| U4 | Narratives and metrics justify dominance. |
| U5 | Timing and delay are used to exhaust challengers. |
| U6 | Field coherence declines under asymmetric control. |
| U7 | Memory preserves dominance as precedent. |
| U8 | External forcing may expose fragility beneath dominance. |
7. Common Failure Patterns
| Failure Pattern | Description |
|---|---|
| Dominance Masquerading as Control | Force suppresses visible error while hidden debt rises. |
| Exit Denial | Dominant systems prevent coherent decoupling. |
| Selective Enforcement | Rules apply asymmetrically. |
| Interface Capture | Dominance controls what can be seen, verified, or appealed. |
| Legitimacy Debt | Compelled order erodes long-term trust. |
8. Restoration Implications
Restoring dominance requires converting power into accountable, scoped, repair-capable authority or reducing the dominance structure.
Typical sequence:
Μ map power surface
→ Au restore traceability
→ identify asymmetries
→ restore BΣ and exit
→ protect feedback
→ provision repair
→ enforce symmetry
→ Τ validate legitimacy over timeDominance is repaired when power no longer depends on suppression, capture, or hidden debt export.
9. Machine-Readable Summary
glossary_entry:
id: "GL-160"
term: "Dominance"
symbols:
- "Φ"
- "O"
- "ι"
short_definition: "Power-based control over a field, node, system, resource, narrative, interface, or decision surface; dominance is not coherence."
term_family: "Core System Patterns"
term_class:
- "Core System Pattern"
- "Power Pattern"
- "Control-Relevant Term"
core_formula:
- "dominance ≠ coherence"
diagnostic_negative:
- "control over field↑"
- "exit cost↑"
- "alternative pathways↓"
- "Au asymmetry↑"
- "BΣ stress↑"
- "H↑"
restoration_requirements:
- "power surface mapping"
- "auditability restoration"
- "boundary and exit repair"
- "feedback protection"
- "symmetry enforcement"
- "time validation"