Concepts & methods

TELOS: the purpose layer your planning system is missing

Daniel Miessler's open-source file asks you to write down your problems, missions, goals, and metrics in one place any system (or AI) can read. A reference entry on what a purpose layer is for, and why it needs a week underneath it.

Aleem O'BalogunBy Aleem O'Balogun|Updated |4 min read

The short answer

TELOS is Daniel Miessler's open-source framework for writing down your purpose as structured plain text: the problems you care about, the missions they imply, the goals that serve those missions, and the metrics that say whether it is working. Named for the Greek word for purpose, it is the layer above any planning system: the criteria the planning is for.

What it is, and who made it

TELOS is the framework Daniel Miessler publishes openly at danielmiessler.com/telos, named for the Greek telos, the end or purpose a thing exists for (the word is Aristotle's). The practice is disarmingly concrete: one plain-text file that works from the outside in. Which problems in the world do you actually care about? What missions follow from caring? Which goals, with dates, serve those missions, and which metrics would show movement? The file extends to history, flaws, and ideas in Miessler's full template, but the problems-to-metrics spine is the framework. It sits beside his open-source LifeOS work, and the two are designed to meet: a structured purpose file is something a planning system, or an AI assistant, can actually read and serve.

What it actually solves

Most planning systems inherit their criteria silently. Something feels important, gets planned, and the feeling is never audited; busy weeks accumulate into years without anyone checking what the busyness was for. TELOS makes the criteria explicit and inspectable. Written down, “why does this goal exist?” has an answer you can follow up the chain to a mission and a problem, and the goals that serve nothing become embarrassingly visible. The plain-text choice matters more than it looks: the file is versionable, portable, private by default, and readable by any tool you might ever point at it, which is precisely the property that lets purpose inform planning rather than living in a journal nobody reopens.

Where it breaks

A purpose file has one failure mode: staying an essay. Written once in an inspired evening and never consulted, TELOS becomes the most articulate unused document you own, and nothing in the framework itself forces the connection downward into what you do on Tuesday. It also asks for honesty that takes iterations to reach; first drafts reliably contain the missions their author wishes they had, and the file only starts working once it describes the real ones. Miessler's own practice treats it as a living document under revision, which is the correct defence, and the part easiest to skip.

How it maps to the notice loop

TELOS does not run the loop; it sits above it and supplies what the loop cannot generate for itself: criteria. Noticing needs a definition of “matters”, shaping needs priorities that come from somewhere, and reviewing needs a standard to review against; a purpose file is where those live. The connection has to be built as a habit, and the natural joint is the planning cadence: the weekly shape consults the goals, and the quarterly review is where the file itself gets re-read and revised against reality. Purpose above, loop below, each meaningless without the other.

Sources

Primary sources; the framework is published openly and the entry describes it as published.

  • Daniel Miessler, TELOS (danielmiessler.com/telos, with the template on GitHub), and the adjacent open-source LifeOS project. The problems, missions, goals, and metrics spine, and the plain-text, AI-readable design intent.
← All guides