The XRUIOS

Least privilege is the architecture.

Through a carefully created system, functions are split between multiple workers. No app talks to these workers directly; a singular allowed manager is asked, which then checks the permissions and routes the call.

The three walls

A wall between every worker.

Barebones was one project with about 400 functions. In The XRUIOS each system class runs as its own worker with its own password and its own key.

WALL 1

Process isolation

One class per worker. Compromise the Songs worker and you still can't reach Calendar's code, because it isn't loaded there.

WALL 2

Password isolation

Each worker gets its own 256-bit PSK, held only by the Manager. A leaked PSK unlocks exactly one worker.

WALL 3

Key isolation

Each worker's store is encrypted under its own key, derived from the master. A breach reads its own data and nothing else.

WalkerDev"Security is at the core of every good, worthwhile system."

How a request flows

Apps never touch a worker. They ask, and the Manager decides.

AUDIT ✎

    The app never learns which worker answered, never holds a worker key, and never touches the OS directly.

    Breaching one wall doesn't cascade.

    Pick an attack and see what it gets.