What a Life OS is
A Life OS is the idea of one home for your whole life: goals, projects, health, finances, relationships, and routines, organised so they connect rather than scatter across a dozen apps.
The term is borrowed from operating systems for a reason. The promise is a single layer that everything else runs on top of, so you are not rebuilding context every time you switch from work to health to money.
The Notion-template approach
The most common way people build a Life OS is a Notion template: a set of linked databases for tasks, goals, habits, and notes. The appeal is real. It is flexible, endlessly customisable, and there is a large ecosystem of templates to start from.
The cost is maintenance. A Notion Life OS is a system you operate. You design it, you keep it current, and you do the planning yourself. The template stores your life but it does not plan your week. It also lives in the cloud, on someone else's servers.
The purpose-built-app approach
A purpose-built app takes the opposite trade-off. You give up some flexibility and get structure and planning that already work. Instead of designing databases, you name what matters and the app drafts the week.
asambl is built this way. It is opinionated about how whole-life planning works, it keeps your data on your machine, and it drafts plans across your life areas that you approve, amend, or discard. You are not maintaining the system; the system is doing the planning.
Which should you choose?
If you enjoy building systems and want total control over structure, a Notion template can be a great fit. If you want the outcome (a coordinated weekly plan) without the upkeep, and you care about keeping your data private and local, a purpose-built app is the lower-friction path.
A useful test: do you want to spend your time tending the system, or running your week? That answer usually points clearly one way.