What Is the TELOS System? A Complete Guide to Personal AI Goal Management
The TELOS system is a Telic Evolution and Life Operating System that captures personal objectives through structured markdown files stored in ~/.claude/skills/PAI/USER/TELOS/, using automated backup workflows and conversational editing to maintain a secure, version-controlled single source of truth for AI-assisted personal development.
The TELOS system serves as the deep-goal-understanding layer within the danielmiessler/Personal_AI_Infrastructure repository. Unlike simple task managers, this primitive transforms ephemeral intentions into structured, queryable data that downstream AI workflows can reliably reference when generating reports, analyzing projects, or providing strategic recommendations.
Understanding the TELOS System Architecture
Core Components and File Structure
The TELOS system resides in the user's personal directory at ~/.claude/skills/PAI/USER/TELOS/. According to the source code in SKILL.md, this location houses a collection of markdown and optional CSV files that collectively model an individual's complete strategic context.
The system operates through two primary contexts: personal life management and project analysis. As implemented in the danielmiessler/Personal_AI_Infrastructure codebase, TELOS functions as "one skill, two powerful contexts," enabling both holistic life operating system functionality and targeted project evaluation frameworks.
The Ten Dimensions of Personal Context
The TELOS system captures personal objectives across ten distinct dimensions, each stored as dedicated markdown files:
- Mission: Core purpose and overarching life direction
- Goals: Specific, measurable objectives derived from the mission
- Beliefs: Foundational principles that guide decision-making
- Strategies: High-level approaches for achieving goals
- Projects: Concrete initiatives with defined deliverables
- Narratives: Personal stories and contextual background
- Lessons Learned: Insights from past experiences
- Challenges: Current obstacles and constraints
- Ideas: Potential opportunities and concepts
- Mental Models: Cognitive frameworks for processing information
This structure ensures that when a user asks "what are my goals?" or requests to "add a new objective," the TELOS system routes these queries to the appropriate files while maintaining relationships between different dimensions of personal context.
How the TELOS System Captures Personal Objectives
The Update Workflow: Safe, Conversational Editing
When users interact with the TELOS system to modify personal objectives, the Update workflow handles the interaction through a conversational interface. Located in Workflows/Update.md, this workflow guides users through structured edits while enforcing critical safety constraints.
The workflow implements a four-stage capture process:
- Guidance: The system initiates a conversational edit, asking clarifying questions to ensure the objective is properly categorized and specified.
- Validation: Before writing changes, the system verifies the target file exists and identifies the appropriate markdown section.
- Execution: The new objective is appended or inserted into the relevant TELOS file (e.g.,
GOALS.mdorPROJECTS.md). - Confirmation: The system summarizes the change and confirms the update has been persisted to the local TELOS directory.
Automated Backup and Logging Mechanisms
The TELOS system implements rigorous data protection through automated backup and logging mechanisms defined in the Update workflow. Before any modification occurs, the system creates a timestamped backup in the Backups/ subdirectory within the TELOS folder.
Every change is logged in updates.md, creating a complete audit trail of personal objective evolution. This log includes timestamps, change descriptions, and references to backup file locations, enabling users to review their strategic development over time or revert to previous states if needed.
Critically, the TELOS system enforces a security rule that prevents personal TELOS files from being committed to public repositories. As implemented in the workflow logic, this ensures that sensitive personal objectives, beliefs, and strategic plans remain local and private, never exposed through accidental version control operations.
Practical Implementation: Working with TELOS Files
The following examples demonstrate how to interact with the TELOS system using the command-line tools and workflows provided in the danielmiessler/Personal_AI_Infrastructure repository.
Adding a New Personal Goal
Use the update-telos script to append objectives to specific TELOS files:
# Add a goal to GOALS.md
bun ~/.claude/commands/update-telos.ts GOALS.md "- *Learn TypeScript* – become proficient enough to build a personal CLI tool" "Add new learning goal"
This command creates a timestamped backup, appends the new goal to ~/.claude/skills/PAI/USER/TELOS/GOALS.md, and logs the change to updates.md.
Reading Current Objectives
Query your stored goals directly from the TELOS directory:
cat ~/.claude/skills/PAI/USER/TELOS/GOALS.md
Typical output includes structured markdown with italicized goal titles and descriptive text:
# Goals
- *Learn TypeScript* – become proficient enough to build a personal CLI tool
- *Publish a monthly newsletter* – share AI‑enabled productivity tips
- *Run a 5 km race* – improve physical health by Q3 2026
Generating Strategic Reports
Trigger the WriteReport workflow to synthesize TELOS data into professional documentation:
pai ask "write a TELOS report for my personal objectives"
This workflow, defined in Workflows/WriteReport.md, pulls data from all ten TELOS dimensions, formats a dark‑theme web report, and returns a printable PDF suitable for strategic review sessions.
Accessing the Dashboard Interface
For visual management of TELOS files, launch the local dashboard:
http://localhost:3000/teleos/dashboard
The dashboard, provided by the DashboardTemplate, renders every TELOS file with inline editing capabilities and displays recent backup history, offering a GUI alternative to command-line interactions.
Security and Privacy Architecture
The TELOS system implements a privacy‑first architecture that keeps sensitive personal data local. Unlike cloud‑based goal‑tracking applications, TELOS stores all objectives in the user's personal directory (~/.claude/skills/PAI/USER/TELOS/) on local storage.
The Update workflow enforces a critical security constraint: personal TELOS files are never committed to public repositories. This rule prevents accidental exposure of mission statements, strategic beliefs, and personal challenges through version control operations. Users maintain complete sovereignty over their objective data, with backups stored locally in the Backups/ subdirectory rather than remote servers.
Summary
The TELOS system transforms abstract personal intentions into structured, actionable data within the danielmiessler/Personal_AI_Infrastructure ecosystem. Key capabilities include:
- Structured goal modeling across ten dimensions (Mission, Goals, Beliefs, Strategies, Projects, Narratives, Lessons, Challenges, Ideas, Mental Models) stored as markdown files in
~/.claude/skills/PAI/USER/TELOS/ - Conversational capture workflows that guide users through adding or modifying objectives while maintaining data integrity through the Update workflow
- Automated backup and logging that creates timestamped backups in
Backups/and maintains complete audit trails inupdates.md - Privacy‑first architecture that keeps all personal objectives local and prevents accidental commits to public repositories
- Downstream integration enabling skills like WriteReport to generate professional strategic analyses from the single source of truth
Frequently Asked Questions
What does TELOS stand for in the Personal AI Infrastructure?
TELOS stands for Telic Evolution and Life Operating System. The name reflects the system's dual purpose as both a life‑management framework and a project analysis tool, serving two powerful contexts within a single skill according to the SKILL.md documentation in the danielmiessler/Personal_AI_Infrastructure repository.
How does the TELOS system differ from traditional todo applications?
Unlike traditional todo applications that store tasks in proprietary cloud databases, the TELOS system captures personal objectives as structured markdown files stored locally in ~/.claude/skills/PAI/USER/TELOS/. It models goals across ten dimensions—including beliefs, mental models, and narratives—rather than simple checklists, and integrates with AI workflows for automated reporting and strategic analysis while maintaining strict privacy controls.
Where are TELOS files backed up before modifications?
Before any modification, the TELOS system creates timestamped backups in the Backups/ subdirectory within ~/.claude/skills/PAI/USER/TELOS/. The Update workflow automatically generates these backups while logging all changes to updates.md, ensuring complete version history without manual intervention or exposure to remote servers.
Can TELOS data be committed to public Git repositories?
No. The TELOS system enforces a strict security rule that prevents personal TELOS files from being committed to public repositories. This privacy protection is hardcoded in the Update workflow to ensure that sensitive personal objectives, mission statements, and strategic beliefs remain local and are never exposed through accidental version control operations.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →