Learn ClarityOS.
Every feature. Every pipeline.

Every piece of content you'll ever produce begins as raw input — a fleeting idea, a quote, a question. The Knowledge Pipeline transforms that raw input into structured insight. The Project Pipeline turns insight into executed, finished work. The Content Pipeline turns finished work into published thinking that earns leverage and feeds back into new captures.

Everything in Clarity OS is stored as plain markdown files in your vault — a folder you choose on your computer. No cloud lock-in. No database. You own your data completely.

Most people never ship because their ideas go nowhere. The Capture Feed is where every raw thought lands — ideas you have mid-shower, quotes you read, questions that surface while working. The rule is simple: capture now, process later. Nothing gets evaluated at capture time. Speed is the point.

Every capture item has a type prefix that signals what kind of raw material it is. This prefix determines how it travels through the system.

An Insight Note is not a summary. It is your synthesis — a claim you can defend, with a mechanism you understand, connected to things you already know. The conversion from Capture to Insight Note is the most important transformation in the system. This is where raw input earns permanence.

When you click → Convert to Insight Note from the Capture Feed, the Three-Gate Filter runs first. Three questions determine if this capture is insight-grade material:

Insight Notes have a fixed structure — every field has a purpose:

The status tag is the most important field — it tells you what stage of the pipeline this note is at:

A Connection Note links exactly two Insight Notes and surfaces the insight that lives between them — the thing that neither note contained on its own. This is where your knowledge starts to compound. Connections are where synthesis actually happens.

Idea Notes are where synthesized thinking becomes applicable. They have two stages — Idea Seed and Big Idea Thesis — representing the progression from promising spark to fully-developed argument ready for long-form content or a new project.

A Map of Content (MOC) is a navigation note — not a knowledge note. It doesn't contain thinking. It organizes access to thinking that already exists. MOCs emerge when multiple notes converge on a theme: you notice the same concept appearing across several Insight Notes and Connection Notes. The MOC names that theme and links inward.

The Graph View renders your entire vault as a visual web of nodes and connections. Each note is a node; each link between notes is an edge. The graph reveals your actual thinking patterns — which ideas are well-connected, which are isolated, and where themes are emerging.

Most projects fail before they start — not from lack of effort but from lack of definition. An idea that passes through Start Smart either becomes a real project with a clear finish line, or it stays in the knowledge pipeline where it belongs. No idea skips this step.

Every project gets a dedicated dashboard with four tabs. Each tab has a clear function — none overlap. The dashboard is where execution lives, not where thinking happens. Thinking lives in the knowledge pipeline and feeds into the project via the Direction tab.

A sprint is one week of execution against one project. Maximum 3 tasks per sprint — not because more isn't possible, but because 3 well-chosen tasks is what actually finishes projects. Sprints have a Weekly Focus — the outcome the sprint should produce — which flows directly into the Command Center as Today's Focus context.

The Content Dashboard is the home for everything content-related — your North Star (publishing identity), your Content Calendar (what ships when), your Idea Pipeline (sparks to theses), and your Banks (reusable content assets). Content flows from the knowledge pipeline into here — never the other direction. Thinking first, writing second.

The Content Calendar tracks every scheduled piece through its production lifecycle. Each entry has a status, a channel, a format, and a content stream. The calendar is not a planning board — it's a commitment surface. What's on the calendar ships.

Content Banks are collections of proven, reusable elements that speed up production without reducing quality. They store patterns that work — opening hooks that pull readers in, structural frames that organize arguments, and personal stories that make ideas concrete and memorable.

The Pipeline Pulse is a five-stage count that shows you exactly where your system stands at a glance. It doesn't require you to open each pipeline individually — it surfaces the signal instantly. If Capture shows 12 and Output shows 0 for three weeks running, the system is telling you something important.

The Command Center holds goals, not tasks. Tasks live in the Sprint. The Primary Outcome is the single thing that makes today a win — even if nothing else happens. Today's Focus tasks are pulled directly from the active sprint's task list, not created fresh each morning. The morning ritual is recognition, not reconstruction.

Daily KPIs are not performance pressure — they are system diagnostics. Four numbers tell you whether your pipelines are actually flowing today. Set targets once per week; track actuals each day. The data accumulates and gets harvested each week in the Weekly Review.

Most people end the day the same way they started it — reactively. The End-of-Day Check-In is the closing ritual: four prompts that surface what happened, extract what's worth keeping, and set tomorrow up to start strong. The data accumulates in the Command Center and gets harvested in the Weekly Review.

The daily routine is not a checklist to complete — it is an anchor to open and a ritual to close. The system runs in the space between. Consistency matters far more than duration. A 5-minute morning and 5-minute evening run every day produces more than a 2-hour session once a week.

The Weekly Review is the integration moment where everything accumulated during the week gets processed, assessed, and set up for the next. Skipping it compounds silently — one missed review is recoverable; three missed reviews means the system has drifted far enough that recovery takes a full session just to get functional again.

The app surfaces stale items automatically to speed up the review:

The Quarterly Review checks the direction of the system — not the daily operation. Weekly Reviews keep things running. The Quarterly Review asks if you're running in the right direction. Three reviews, 20–30 minutes each.