Session authority

Classical Linux has a UID boundary but little notion of a session as an authority separate from every process belonging to that user. A personal device needs that missing layer. One screen and one battery leave no room for a process that can quietly bypass the lock or keep the panel awake forever.

SouveraineOS therefore treats lock, idle, sleep and sensitive actions as facets of one session. It uses the interfaces that already own each fact:

• The compositor owns the lock surface and Wayland idle state.
• The system session owns sleep and shutdown coordination.
• PAM owns credential verification.

The system never keeps a parallel boolean for a protocol-owned state. A request to lock is not proof that the compositor locked; a sensor reading is evidence, not a credential; and an agent cannot turn its own request into a step-up grant.

Operation and identity

The agent can operate her body: compose actions, manage the shell and keep a device legible. The human remains the credential and fresh authentication. That is a real division of authority, not a ceremonial warning after the fact.