About
One owner, deciding.
Computers change things and never say why. sutraOS is an attempt to build one that does.
Why it exists.
01
Something changed
An update, a setting or an app changed the system overnight. Nothing tells you what.
02
Nobody says why
The fan is loud, the battery drains, the backup did not run. The answer is buried in logs.
03
No way back
Undo stops at the edge of each app. Reversing a system change means a restore, if a backup exists.
How it is made.
Most of what a good system needs exists in Linux already. What is missing is one owner who decides, tests and says no.
- Proofs before code
- The riskiest ideas are tried small first. A proof that fails changes the design before anything is built on it.
- Drawn before built
- Every screen is drawn first and checked against written interface guidelines.
- Measured, or called a target
- A number is a target until it is measured, and a measurement names the machine it was taken on.
- Nothing half present
- A thing that waits is absent: no greyed-out menus and no promises with no date behind them.
- Upstream first
- Fixes go to the projects sutraOS stands on before they go anywhere else.
The names.
sutraOS
A sutra is a thread, and a short rule that holds a larger body of thought together. The name is written sutraOS, with a small s, also at the start of a sentence.
Rupa
The design language. Rupa is the Sanskrit word for form. Design
Who is behind it.
sutraOS is designed and built by one person for now, working with coding agents, on the laptops it targets first. A team follows when there is funding.
The company's name, the founder's name and a contact address: the owner's choice