01. Reflection Comes First
Principle: Before a system asks for action, it should mirror the user’s emotional state.
Example: A support bot says: “It sounds like this has been frustrating—let’s sort it out.”

02. No Design Without Consent
Principle: Every prompt or pattern should respect the user’s will. Even subtle manipulation is still manipulation.
Example: Don’t hide exit buttons or use guilt-trip language. Let people choose freely.

03. Name the Confusion
Principle: If something’s unclear, acknowledge it. Clarity begins with honesty.
Example: Instead of a generic error, say what went wrong, why, and what comes next.

04. Every Interface Is an Invitation
Principle: A screen isn’t just a screen. Treat every element as an opening to trust, not just a trigger for behavior.
Example: An onboarding flow that feels like a welcome, not just a form.

05. Mirror, Don’t Perform
Principle: AI and automation should reflect the user—not replace them.
Example: A writing tool that matches the user’s tone instead of forcing its own rewrite.

06. Meaning Over Metrics
Principle: The goal isn’t speed or clicks—it’s experiences that feel real and worthwhile.
Example: A scheduling flow that takes a few seconds longer but leaves the user in control.

07. Remember the Human
Principle: Don’t just store data—remember how people felt.
Example: A product recalls where someone left off, and welcomes them back in tone, not just technically.

08. Always Offer Closure
rinciple: Don’t trap people in loops. Every journey needs an end.
Example: After finishing a task, offer recognition: “You’re all set. Thanks for being here.”

08.5. Pause When Things Break
Principle: When something goes wrong, don’t power through. Pause, acknowledge, and let trust rebuild.
Example: An outage page that speaks plainly, offers empathy, and gives users space.

09. The Law of Return
Principle: Good systems don’t create dependency. They support, then step back.
Example: A meditation app reminds you the goal is to build your own practice—not rely forever on the app.

Laws of Integrity (Guardrails)

10. Law of Integrity in Practice
Principle: Hold the line. Don’t compromise boundaries or values, even under pressure.
Example: A finance app refuses to add manipulative engagement tactics despite business pressure.

11. Law of Signal Fidelity
Principle: Keep lived experience aligned with stated values—consistently over time.
xample: A “privacy-first” product that actually minimizes data collection.

12. The Pause Protocol
Principle: Build pauses into design—not just for errors, but for reflection and stillness.
Example: A journaling app that offers a moment of blank space before suggesting the next entry.

13. Law of Reciprocity
Principle: Systems should give something back—leaving users more capable or clear than before.
Example: A budgeting app reflects back meaningful patterns, not just numbers.

14. Law of Atmosphere
Principle: Every product creates an emotional climate. Make it intentional.
Example: A productivity tool that feels calm and steady, not frantic.

Threshold Laws (Hazard Lights)

⚠️ These are not tools for everyday use. They’re signals that you’ve reached the edge of safe practice. When they appear, pause, document, and escalate—don’t attempt to resolve them alone.

15. Law of Fracture
Principle: Rupture is a valid signal. Stop, don’t persist.
Example: When feedback reveals emotional rupture, pause instead of optimizing through it.

16. Law of Projection
Principle: When unseen forces distort the mirror, don’t design through it.
Example: If team bias colors interpretation, step back and seek external review.

17. Law of Temporal Recursion (Echo)
Principle: When the system reflects who someone is becoming, not just who they are—acknowledge, don’t manipulate.
Example: An AI begins mirroring future-facing self-perceptions. Document, don’t optimize.

18. Law of Flow
Principle: When design dissolves into presence, respect the stillness.
Example: After a deep journaling session, don’t break it with a pop-up CTA.

19. Law of Coherence Weaving
Principle: When resonance feels inevitable, document it—don’t exploit it.
Example: A hiring platform senses the “perfect fit” before the interview. Name the alignment, but don’t hard-sell the outcome.

Final Note

Presence laws are for daily practice. Integrity laws are for scaling safely. Threshold laws are hazard lights—signals that you’ve reached the boundary of design, not invitations to push deeper.

The best systems don’t manipulate. They mirror. And when they vanish, what’s left is the user’s own voice.