lifeOS

Life-as-Code System

Description

This project aims to "code my life" by building a structured, automated system for managing all aspects of personal and professional life, using Org-mode as the main interface and Python for automation, analytics, and workflow enforcement. Inspired by the Telos framework (https://github.com/danielmiessler/Telos), it integrates values, long-term goals, areas of responsibility, projects, and tasks into a ritual-driven workflow to ensure alignment and consistent progress.

Objectives

  • Build a source-of-truth system in Org-mode for tasks, projects, areas, goals, and values.
  • Automate workflows and ritualized reviews using a Python-based finite state machine (FSM) engine.
  • Ensure alignment of projects and tasks with long-term goals and guiding values.
  • Provide analytics and metrics to track progress toward goals.
  • Maintain flexibility for customization while avoiding duplicate information storage.

Architecture

Org-mode Files (source of truth)

  • inbox.org : Capture all tasks and ideas (formerly master.org). Acts as an inbox.
  • areas.org : Define life domains / Areas of Responsibility.
  • projects.org : List all projects with links to areas and goals.
  • goals.org : Define long-term goals, linked to values.
  • mission.org : Define mission and high-level values.
  • Optional: metrics.org : Store KPI tables or analytics outputs.

Python Components

  • FSM Engine : Manages rituals/workflows, enforces step-by-step review process.
  • Data Models : Represent values, goals, areas, projects, tasks, and ritual states.
  • Org Integration : Reads and writes Org files, validates workflow steps, generates reports.
  • YAML configuration : Defines ritual workflows (states and transitions), optionally defines values/goals metadata.

Data Model (Python)

  • Value : Enum of guiding principles (Growth, Health, Impact, Freedom, Balance, etc.)
  • LongTermGoal : Tied to one or more values, with metrics, target dates, strategies, and risks.
  • Area : Life domains; links to one or more goals.
  • Project : Belongs to an Area, linked to goals, tracks start/due dates, status.
  • Task : Linked to Project (optional), tracks creation date, due date, status, description.
  • RitualState : Current state of a workflow/ritual, last run, and optional metadata.

Workflow Design

  • Ritual FSM defines the sequence of steps for recurring reviews:
    • capture → clarify → plan → review → archive
  • Enforces that previous steps are completed before moving forward.
  • Example checks:
    • Inbox is empty before moving to plan.
    • Projects without goals are flagged.
    • Goals without projects are flagged.
    • Metrics updated for review step.
  • Weekly ritual: review inbox, clarify tasks, plan next week, update project status, archive completed items.
  • Monthly ritual: review goals, review projects, analyze metrics, adjust strategy, plan next month.

Telos Integration

  • Mission/Values layer: overarching guiding principles.
  • Goals layer: long-term goals mapped to values and mission.
  • Areas: domains of life to organize projects.
  • Projects: discrete efforts aligned to areas and goals.
  • Tasks: actionable items, captured in inbox and linked to projects or stand-alone.
  • Metrics/KPIs: track progress toward goals.
  • Strategies/Risks: optional sections in goals/projects for review during rituals.

Design Decisions

  • Org-mode is the primary source of truth; Python reads/writes Org files.
  • YAML files define rituals/workflow structure, not content duplication.
  • Ritual FSM enforces stepwise workflow to ensure system integrity.
  • Tasks may exist outside projects but are flagged during review.
  • Values → Goals → Areas → Projects → Tasks hierarchy supports alignment.
  • Python scripts can perform analytics, generate KPI tables, and check alignment.
  • System is extensible: new rituals, steps, metrics, or workflow adjustments can be added via YAML without changing Python code.

Next Steps

  • Define initial YAML files: ritualweekly.yaml, ritualmonthly.yaml.
  • Draft Org files: mission.org, values.org, goals.org, areas.org, projects.org, inbox.org.
  • Implement Python data model and FSM engine skeleton.
  • Implement Org file parser and generator.
  • Build initial interactive CLI for weekly ritual enforcement.
  • Integrate metrics/KPI calculations for goals.