Know
Know what the system is doing and why it is doing it.
ETHICS
Define the boundary before expanding capability.
The closer technology comes to the body, the more restraint it needs.
01 / CURRENT SCOPE
State support means helping someone regain stability, clarity, and agency when they are overwhelmed or unable to rest, with their knowledge and consent.
At this stage, our work is focused on pre-sleep regulation and restorative use. The aim is to help a person move toward rest, not to override awareness, erase every difficult feeling, or make decisions for them.
02 / PRINCIPLES
They govern how we design state support.
The user remains the owner of their own state. The system may support recovery, but it must not replace judgment or self-direction.
People should know when support is active, why it is being offered, and what form it takes.
People decide whether support is on and what they accept. Pause, reduction, and shutoff must remain available.
Use the least intervention needed. Meaningful discomfort should not be automatically flattened.
Safety and dignity come before experience optimization. User interests come before business incentives.
03 / LIMITS
These five practices have no place in our product design.
We do not shape compliance for conversion, engagement, dependency, or institutional convenience.
A third party cannot define someone's target state without that person's informed agreement.
Grief, moral conflict, and reality-based distress should not be erased automatically, or reduced to one emotional template.
When reflection, alertness, or real-world decisions are required, the system must not push a person toward sedation or impaired judgment.
State support is not a substitute for care, judgment, or medical responsibility, and claims must stay within the evidence.
Beyond general state support, the system should reduce intervention and leave judgment with the person.
04 / RIGHTS
Know what the system is doing and why it is doing it.
Decide whether support is enabled and what forms are accepted.
Choose manual or automated control, and reduce support at any time.
Pause or turn off support at any time, without giving a reason.
As capability grows, explanations, controls, and automation boundaries must become clearer.
05 / COMMITMENT
This charter will change as our capabilities, evidence, and responsibilities change. The direction remains the same: define limits before expanding capability, and protect human agency before optimizing experience.
When evidence is limited, our claims will be narrower. When there is no clear reason to intervene, the system should remain quiet.
Questions about these boundaries are welcome