LifeOS Personal Operating System

Problem Addressed

Turns “I want to plan but don’t know where to start” into an actionable workflow. It targets common blockers: vague goals, scattered todos, and shallow reviews. It does not make decisions for you; it uses questions to connect knowledge, goals, execution, and review into one loop.

How It Works

Routing follows “know, aim, act, reflect”:
- Knowledge system: uses Zettelkasten, Feynman learning, and PARA to turn input into internalized notes and output.
- Goal system: checks goals with SMART, then turns annual intent into no more than 3 Objectives and Key Results.
- Execution system: organizes tasks with GTD lists such as capture, next actions, projects, waiting, and someday, then sets a daily focus rhythm with Pomodoro.
- Review system: asks GRAI questions: goal, result, analysis, and insight, so reviews stay tied to goals instead of becoming event logs.

For cross-system requests, it starts from knowledge or goals when possible; for unclear starts, it runs a global diagnosis and suggests the weakest area. Outputs are Markdown documents such as OKR-YYYY-annual/monthly.md, GTD-list-YYYY-MM-DD.md, and LifeOS-diagnosis-YYYY-MM-DD.md.

Fit and Limits

It fits engineers doing personal planning, note-taking, goal decomposition, and periodic review. Because it depends on user context, the more concrete the goals and task list, the more usable the output. If the request is only a vague desire, start with diagnosis first. It does not complete real-world tasks, sync external systems, or auto-execute lists; it converts thinking into saved, structured documents.