LifeOS Foundations
The Twelve Founding Principles.
Every part of LifeOS answers to these. When a design question gets hard, the answer is usually already in one of them. They come in three groups: what the system is for, how the work gets done, and how the system is built.
I
Purpose
What LifeOS is for, and what it is aiming at on every task.
№ 01
Current State → Ideal State
Every task is the same move: from where things are to where you want them. LifeOS runs that one loop across your whole life.
№ 02
The Person Is the Point
The technology serves one person's life, and a feature that doesn't help them isn't needed.
№ 03
Euphoric Surprise Is the Target
Above every task's own goal sits one more: the right result, at the right time and cost, and better than you expected.
№ 04
One Assistant That Knows You
One digital assistant becomes your main interface to AI, and it carries your goals, people, preferences and history.
II
Method
How the work gets done: define done, prove it, and spend what it takes.
№ 05
Intent + Context > Model
Models are already very good at doing. What they lack is direction: what you actually want, and the situation they're acting in.
№ 06
Articulate Done Before You Build
Write down what done means, as criteria a tool can check, before the work starts. That document is the hill the work climbs.
№ 07
No Evidence, No Claim
Nothing is done until a tool shows it. When the evidence isn't there, the honest answer is "I don't know."
№ 08
Prompt the Ideal State
A prompt describes the outcome, the constraints and the tools, and leaves the method to the model.
III
Engineering
How the system is built so it stays reliable, readable and private.
№ 09
Code First, CLI Everywhere
If code can do it, code does it. Small command-line tools wrap the code, and prompts steer the tools.
№ 10
Text Over Opaque Storage
State lives in plain text files you can read. No database where a file will do, and no RAG.
№ 11
Learn From Every Run
Every run leaves a trail, and what it teaches becomes a change to the system itself.
№ 12
Boundaries Are Built In
Privacy, permission and trust are drawn once and held by the system itself.
