What Is the TELOS Framework in LifeOS and How to Capture Current State to Ideal State

The TELOS framework is LifeOS's core context-gathering system that maps personal beliefs, goals, and projects from current reality to an ideal future state through structured markdown files and automated workflows.

LifeOS, developed by Daniel Miessler, is an open-source life operating system designed to bridge the gap between where you are and where you want to be. The TELOS (Telic Evolution and Life Operating System) framework serves as its central intelligence layer—collecting, organizing, and analyzing the data that drives personal and project evolution. As implemented in danielmiessler/LifeOS, TELOS operates across two distinct modes: Personal TELOS for individual life context and Project TELOS for organizational or initiative-based analysis.

Understanding the TELOS Framework Architecture

What TELOS Actually Does

At its core, TELOS is a dual-purpose context engine defined in LifeOS/install/skills/Telos/SKILL.md (lines 38-42). The framework's descriptor explicitly states its purpose: "TELOS (Telic Evolution and Life Operating System) is a context-gathering system with two applications"—personal life management and project analysis.

Personal TELOS stores your complete life context under ~/.claude/LIFEOS/USER/TELOS/. This directory contains purpose-built markdown files including:

• TELOS.md — Core identity and mission
• GOALS.md — Target outcomes with metrics
• BELIEFS.md — Foundational principles
• PROBLEMS.md — Current obstacles and challenges
• PROJECTS.md — Active initiatives
• STRATEGIES.md — Approaches to bridge gaps
• PREDICTIONS.md — Future-state envisioning

These files collectively describe your current reality and your ideal future—the two poles that LifeOS is designed to reconcile (SKILL.md, lines 37-65).

Project TELOS, by contrast, is an analysis layer that scans any user-specified directory for .md or .csv files. It constructs a relationship graph mapping PROBLEMS → GOALS → STRATEGIES → PROJECTS and can render reports or interactive dashboards (SKILL.md, lines 98-108).

The Current-to-Ideal State Design Principle

LifeOS's central algorithm is built around the Euphoric Surprise metric—a measurable gap between current and ideal states that drives all planning loops (README.md, lines 39-41). TELOS supplies the raw data for this transition:

1. Current State — Captured during the Interview workflow (step 3) where you describe your mission, active projects, challenges, and everything true right now (Interview.md, lines 20-22)
2. Ideal State — Captured in Interview step 4 where you articulate goals, strategies, metrics, and desired future outcomes (same source)

Both states persist as markdown files in the TELOS directory. After completion, the SeedPulse tool reads these files and writes LIFEOS_STATE.json, which powers the Pulse dashboard with live rings visualizing current versus ideal values (Interview.md, lines 23-24).

How to Capture Current State to Ideal State

The Complete Workflow

Step	Action	Command/Method
1. Initialize	Run the Interview workflow to collect personal TELOS data	lifeos interview
2. Record Current	Answer prompts about mission, people, active projects, and present challenges	Interactive workflow writes to ~/.claude/LIFEOS/USER/TELOS/
3. Record Ideal	Provide goals (with metrics and dates), strategies, and envisioned future	Same workflow populates GOALS.md, STRATEGIES.md, PREDICTIONS.md
4. Persist State	Use the Update workflow for later edits with automatic backups	update-telos command
5. Visualize	Generate JSON state and launch Pulse dashboard	bun Tools/SeedPulse.ts --apply

Step 1: Run the Interview Workflow

The Interview workflow is the primary entry point for capturing both current and ideal states. Executing lifeos interview invokes a structured dialogue where the DA (Digital Assistant) probes your complete life context.

# Start the onboarding interview; captures both Current and Ideal TELOS

lifeos interview

During execution, the workflow internally uses write helpers to persist answers directly to the TELOS directory. No manual file creation is required.

Step 2: Record Your Current State

The Interview workflow's third step specifically targets present reality. You'll be prompted about:

• Your core mission and purpose
• Key relationships and people
• Active projects and their statuses
• Immediate challenges and blockers

Responses automatically populate MISSION.md, PROBLEMS.md, and PROJECTS.md in your TELOS directory.

Step 3: Define Your Ideal State

Step 4 of the Interview shifts to未来 (future) orientation. Here you'll specify:

• Quantified goals with target dates
• High-level strategies for achievement
• Success metrics and milestones
• Long-range predictions and vision

These entries flow into GOALS.md, STRATEGIES.md, and PREDICTIONS.md.

Step 4: Update and Maintain with Versioning

Post-interview changes use the Update workflow, which provides safe modification with full audit trails. The UpdateTelos.ts tool (lines 3-15) implements this functionality:

# Add a new goal with automatic backup and changelog entry

update-telos GOALS.md "### Run a marathon by 2027\n\nTarget: 26.2 miles" "Added marathon goal" --section "Ideal State"

This command:

• Creates a timestamped backup of GOALS.md
• Appends your new goal to the specified section
• Logs the change in updates.md with metadata

The Update workflow documentation (Update.md, lines 81-93) details the full backup and logging protocol.

Step 5: Seed Pulse for Visualization

With TELOS files populated, generate the dashboard state:

# Preview changes without writing

bun Tools/SeedPulse.ts --dry-run

# Apply and generate LIFEOS_STATE.json

bun Tools/SeedPulse.ts --apply

After applying, accessing http://localhost:31337 displays the Pulse interface with progressive rings comparing current versus ideal values across all captured dimensions.

Advanced: Project TELOS Analysis

Beyond personal life management, TELOS extends to organizational contexts. The writeReport command generates McKinsey-style analyses:

# Create professional Current→Ideal narrative for any project

lifeos telos writeReport --project AcmeCorp

Internally, this runs the CreateNarrativePoints workflow, then maps output to styled web reports (SKILL.md, lines 96-104). Project TELOS scans directories, builds dependency graphs, identifies bottlenecks, and tracks progress across the same PROBLEMS→GOALS→STRATEGIES→PROJECTS chain used in personal contexts.

Key Implementation Files

Understanding the TELOS framework requires familiarity with these source files:

File	Purpose
LifeOS/install/skills/Telos/SKILL.md	Core framework definition, personal/project context specifications, file layout schema
LifeOS/Workflows/Interview.md	Onboarding interview capturing Current and Ideal states
LifeOS/install/skills/Telos/Workflows/Update.md	Safe modification protocol with backups and changelogs
LifeOS/install/skills/Telos/Tools/UpdateTelos.ts	CLI implementation for TELOS file updates
LifeOS/Tools/SeedPulse.ts	State generation for Pulse dashboard visualization
LifeOS/install/skills/Telos/Workflows/WriteReport.md	Professional report generation from TELOS data

Summary

• TELOS is LifeOS's dual-mode context engine: Personal TELOS tracks individual life data; Project TELOS analyzes organizational initiatives
• Current-to-Ideal state capture occurs through the Interview workflow, which populates structured markdown files in ~/.claude/LIFEOS/USER/TELOS/
• State persistence uses automated write helpers during interviews and the update-telos CLI for subsequent modifications
• Visualization requires SeedPulse execution to generate LIFEOS_STATE.json and render Pulse dashboard rings
• All changes are versioned through timestamped backups and updates.md logging per the Update workflow specification

Frequently Asked Questions

What does TELOS stand for in LifeOS?

TELOS stands for Telic Evolution and Life Operating System. The term "telic" derives from Greek telos, meaning purpose or end goal—reflecting the framework's orientation toward purposeful state transition from current to ideal conditions.

How is Current State different from Ideal State in TELOS?

Current State encompasses everything true about your present reality: active projects, existing problems, current beliefs, and immediate constraints. Ideal State articulates target conditions: quantified goals with deadlines, preferred strategies, and envisioned future outcomes. Both states are stored as parallel file sets in the TELOS directory and compared by the Pulse dashboard's ring visualization.

Can I update my TELOS files without running the full Interview again?

Yes. The Update workflow and update-telos command allow iterative modifications. As implemented in UpdateTelos.ts, this tool automatically creates timestamped backups and appends entries to updates.md—providing full change history without requiring complete re-interviews.

What file format does TELOS use for state storage?

TELOS exclusively uses markdown files for personal context storage, with optional CSV support for Project TELOS data ingestion. The framework avoids proprietary formats, ensuring human-readable, version-control-friendly persistence that remains accessible outside LifeOS.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}