They are not rules to enforce or patterns to blindly apply. They are diagnostic principles — ways to understand why a product feels trustworthy, coercive, calm, or exhausting.

When a system “feels off,” one of these laws is almost always being violated.

How to Use These Laws

They are observational, not prescriptive
They apply across UI, AI behavior, copy, pacing, and defaults
They help teams diagnose why trust is breaking — not just where

The laws are organized into three bands:

Core Laws – foundations every system must respect
Relational Laws – how systems behave in emotionally sensitive moments
Advanced Signals – indicators of alignment or overreach

Core Laws (1–9)

These apply to every interface, regardless of domain.

1. Law of Reflection

Principle: Systems should acknowledge user intent and state before acting.
Example: A chatbot confirms understanding before executing a request.
When it’s broken: Users say “That’s not what I meant” repeatedly.

2. Law of Resonance

Principle: Tone and pacing should match the user’s situation—not the system’s goals.
Example: Calm copy during stressful tasks instead of urgency-driven language.
When it’s broken": High completion rates paired with irritation or distrust.

3. Law of Clarity

Principle: If something matters, say it plainly.
Example: Clear summaries instead of buried legal language.
When it’s broken: Users agree to things they later regret or misunderstand.

4. Law of Coherence

Principle: Visuals, language, timing, and structure should align emotionally.
Example: Serious tone for serious decisions.
When it’s broken: Playful UI during high-stakes moments.

5. Law of Sovereignty

Principle: Users must have real choices — without manipulation.
Example: Easy opt-out, equal-weight options, no dark patterns.
When it’s broken: Pre-selected defaults or hidden exits.

6. Law of Completion

Principle: Every effort deserves closure.
Example: Acknowledging task completion or saved progress.
When it’s broken: Dead ends or forgotten user effort.

7. Law of Integrity

Principle: Protect consent, boundaries, and safety.
Example: Opting out is as easy as opting in.
When it’s broken: Users feel tricked or coerced.

8. Law of Presence

Principle: Design should make users feel acknowledged, not processed.
Example: Pauses before nudges or recommendations.
When it’s broken: Relentless prompts and notifications.

9. Law of Signal Fidelity

Principle: What the product claims should match how it behaves.
Example: A “privacy-first” product that actually limits data collection.
When it’s broken: Brand values collapse under real use.

Relational Laws (10–19)

These apply when users are stressed, uncertain, or emotionally loaded.

10. Attunement Before Action

Match emotional state before pushing progress.

11. Reflection as Relationship

Understanding precedes guidance.

12. Transparent Uncertainty

Admit limits instead of bluffing confidence.

13. Agency in Vulnerability

Stress does not remove choice.

14. Validation Before Correction

Acknowledge experience before fixing behavior.

15. Emotional Labor Acknowledgment

Recognize effort, especially in difficult tasks.

16. Silence as Signal

Pauses carry meaning — don’t rush to fill them.

17. Error Recovery as Trust-Building

Mistakes handled well increase credibility.

18. Consistency Across Escalation

Context should carry from AI to human support.

19. Right to Disengage

Users must be able to pause or exit without penalty.

Advanced Alignment Signals (Use With Caution)

These are indicators, not goals.

They signal when a system is either:

deeply aligned
or approaching ethical boundaries

If these appear, pause and document — do not optimize.

Stillness without anxiety
Effortless flow without pressure
Trust without persuasion

Professional Boundary Note

These laws govern UX and system behavior.

They do not justify:

psychological interpretation
identity shaping
therapeutic intervention

When emotional depth exceeds design scope, the correct response is pause, consent, or referral — not deeper automation.

Why These Laws Exist

They exist to answer one question: Is this system helping people act with clarity—or quietly acting on them? When the answer is clear, better design decisions follow.