How to Turn Obsidian Into a Personal Operating System That Never Breaks Down

Most productivity systems break down for the same reason.

They are designed for good days.

On a good day you have the time and energy to maintain the system. You file notes correctly. You update project statuses. You review your inbox. You process everything that came in.

On a bad day the system becomes a source of guilt rather than leverage. You have not processed the inbox in four days. Notes are piled in random folders. Project statuses are weeks out of date.

You stop using the system because maintaining it takes more energy than it saves.

The Obsidian personal operating system is designed differently.

It is not designed for good days.

It is designed to survive bad ones.

The architecture maintains itself when you are overwhelmed, produces useful output when you are inconsistent, and compounds intelligently whether you are actively curating it or not.

This guide is the complete build for an Obsidian system that runs your life and never breaks down regardless of what life throws at you.

Why Most Obsidian Systems Break

Before the build you need to understand why the systems most people build do not last.

They break for three reasons.

Manual maintenance burden. The system requires you to update it regularly to stay accurate. Project statuses need manual updates. Dashboards need manual refreshing. Tags need manual application. When life gets busy the maintenance falls behind and the system becomes unreliable. An unreliable system gets abandoned.

Complexity that compounds over time. People start with a simple structure and add complexity every time they encounter a problem the current system does not handle. Six months later they have a baroque architecture that takes 20 minutes to navigate and requires reading documentation they wrote themselves to understand.

No intelligence layer. The vault stores information but does not reason about it. You capture ideas but never find them again. You take meeting notes but never surface the action items when they become relevant. The system is an archive not an intelligence.

The operating system architecture solves all three.

Manual maintenance disappears because Claude Code connected via MCP maintains the system automatically.

Complexity stays controlled because the architecture has a fixed number of components each with a specific function and no component duplicates another.

Intelligence gets added through Claude which reads the vault, makes connections, surfaces relevant information, and generates outputs that the vault alone cannot produce.

The Three-Layer Architecture

The personal operating system has three distinct layers.

Layer 1: The Storage Layer

This is Obsidian itself. Plain text Markdown files organized in a consistent structure. Every piece of information your life generates lives here in a format that is human-readable, machine-readable, and permanent.

Layer 2: The Intelligence Layer

This is Claude Code connected to your vault via the Filesystem MCP. Claude reads your files, makes connections across them, generates outputs from them, and updates them based on what happens in your life.

Layer 3: The Automation Layer

This is N8N running on a $5 server. It schedules workflows, fires triggers, calls the Claude API, and passes information between systems without you initiating anything.

These three layers are what transform a collection of notes into an operating system.

Remove any one layer and you have something less.

Storage without intelligence is an archive.

Storage with intelligence but without automation is a tool you use.

All three together is a system that operates.

The Vault Structure That Never Breaks

The vault structure is the foundation of everything. Get this right and the system stays coherent as it grows. Get it wrong and it becomes a maze.

The structure has eight folders. Every note in your entire vault belongs in exactly one of them. No folder is optional. No folder overlaps with another.

00 - CAPTURE/ [Everything unprocessed lands here]

01 - ACTIVE/ projects/ [project-name]/ overview.md tasks/ notes/ outputs/ areas/ health/ finances/ relationships/ learning/ career/ daily/ [YYYY-MM-DD].md

02 - RESOURCES/ research/ references/ templates/ bookmarks/

03 - SYSTEM/ CLAUDE.md skills/ workflows/ logs/

04 - GENERATED/ briefings/ summaries/ analyses/ drafts/

05 - QUEUE/ [pending tasks for Claude]

06 - CALENDAR/ events/ reviews/

07 - ARCHIVE/ [completed projects and outdated content]

The logic behind every folder:

00 - CAPTURE exists because capture and processing are separate activities. You capture at the speed of thought. You process at the speed of attention. The capture folder absorbs everything without judgment so nothing gets lost because processing was too slow.

01 - ACTIVE contains only what is alive right now. Projects you are working on. Areas of your life you are responsible for. Daily notes. Nothing historical. Nothing aspirational. Only current.

02 - RESOURCES is the reference library. Things you might need someday. Not things you are working on now.

03 - SYSTEM is the operating system itself. CLAUDE.md. Skill files. Workflow definitions. Logs. The infrastructure layer.

04 - GENERATED is where Claude deposits outputs. Never manually edit files here. They are system outputs.

05 - QUEUE is the inbox for Claude tasks. You drop files here describing what you need. Claude processes them. Outputs land in GENERATED.

06 - CALENDAR tracks time-based information. Upcoming events. Periodic reviews. Things organized by when rather than what.

07 - ARCHIVE is where things go when they are complete. Projects you finished. References that are outdated. Never delete. Archive.

The CLAUDE.md That Makes It Intelligent

The CLAUDE.md is the document that tells Claude everything about your life before any workflow runs.

Without it every Claude session starts from zero. With it every session starts from complete context about who you are, what you are working on, and what matters right now.

Personal Operating System — CLAUDE.md

Identity

Name: [YOUR NAME] Role: [YOUR PRIMARY ROLE] Location: [YOUR CITY]

Life Areas and Current Status

Health: [BRIEF STATUS — e.g., “Training for half marathon, running 4x per week”] Finances: [BRIEF STATUS — e.g., “Saving for house deposit, target by December 2026”] Relationships: [BRIEF STATUS — e.g., “Partner: [name]. Key friendships to maintain: [names]”] Learning: [BRIEF STATUS — e.g., “Currently studying: [topic]. Goal: [outcome]”] Career: [BRIEF STATUS — e.g., “Current role: [title]. Working toward: [goal]”]

Active Projects

[PROJECT NAME]: [ONE-SENTENCE DESCRIPTION] | Status: [STATUS] | Next: [SPECIFIC NEXT ACTION] [Repeat for every active project]

Current Priorities

1. [MOST IMPORTANT THING THIS WEEK]
2. [SECOND MOST IMPORTANT]
3. [THIRD MOST IMPORTANT]

Standards for Generated Content

Voice: [HOW YOU WRITE AND COMMUNICATE] Format preferences: [YOUR PREFERENCES] What you never want: [SPECIFIC THINGS TO AVOID]

Operating Rules

• Never delete files. Move to ARCHIVE with timestamp.
• Never send communications without human review.
• Always date-stamp generated files as YYYY-MM-DD.
• Log every significant action in SYSTEM/logs/operations.md.
• When uncertain about placement, use GENERATED and flag.

Update Schedule

This file is reviewed and updated: [YOUR SCHEDULE — e.g., every Monday morning]

Update the Current Priorities section every Monday morning. This is the single most important maintenance habit in the entire system. Five minutes of honest reflection on what actually matters this week dramatically improves the relevance of everything the system generates.

The Five Workflows That Make It an Operating System

Five workflows transform the vault from a storage system into an operating system.

Each one runs automatically. Each one outputs to GENERATED. Each one maintains itself without your manual intervention.

Workflow 1: The Daily Morning Briefing

Every morning at 6AM this workflow reads your vault and generates a briefing.

The Claude prompt:

Read CLAUDE.md for full life context.

Generate a morning briefing covering:

MOST IMPORTANT TODAY: The single highest-leverage action I can take today based on my current priorities.

SCHEDULE: Any events in CALENDAR/events/ dated today. Prepare a one-sentence brief for each one.

OPEN LOOPS: Any items prefixed with OPEN: in yesterday’s daily note.

PROJECT PULSE: For each active project in CLAUDE.md: one sentence on status, one sentence on next action.

WEEKLY FOCUS: If today is Monday, read the previous week’s daily notes and identify the most important thing to accomplish this week.

Format for under 300 words. Start with MOST IMPORTANT TODAY. Save to: GENERATED/briefings/[DATE]-morning.md

This briefing runs before you open your laptop. You read it in three minutes. You know what matters before you see a single notification.

Workflow 2: The Capture Processor

Every evening at 8PM this workflow processes everything in 00 - CAPTURE.

The Claude prompt:

Read all files in the CAPTURE folder created today.

For each captured item:

1. Identify what type it is: TASK: Something that requires action IDEA: Something to develop or research later REFERENCE: Information to store for later use NOTE: Context or observation about something active EVENT: Something time-bound to calendar

2. File it in the correct location: TASK → Create a task note in the relevant project or area IDEA → File in RESOURCES/research/ with the date REFERENCE → File in RESOURCES/references/ by topic NOTE → Append to the relevant project or daily note EVENT → Create an event file in CALENDAR/events/

3. For TASKS: extract the specific action, assign a due date if mentioned, and add to the relevant project task list.

4. After processing: move the original capture file to ARCHIVE.

Log all processing actions in SYSTEM/logs/capture-log.md.

This workflow means 00 - CAPTURE empties itself every evening. Nothing accumulates. Nothing gets lost in the inbox. Every capture ends up exactly where it belongs without you doing the filing.

Workflow 3: The Weekly Review Generator

Every Sunday at 7PM this workflow generates your weekly review.

The Claude prompt:

Read all daily notes from the past 7 days. Read all project notes modified this week. Read CLAUDE.md for current life context and priorities.

Generate the weekly review:

WHAT MOVED FORWARD: Specific wins from the week. What caused each one. Be specific. Name the projects, the actions, the results.

WHAT DID NOT MOVE: Honest assessment of what stalled. The most likely reason for each item that did not progress.

THE WEEK’S PATTERN: One theme or insight that appeared repeatedly. Whether it signals something to change.

NEXT WEEK’S PRIORITIES: Three specific priorities for next week ranked by impact. For each: why it matters, what the specific next action is.

ONE DECISION: The most important decision sitting open right now. What information you have to make it. What the cost of delaying it another week is.

Save to: GENERATED/summaries/[DATE]-weekly-review.md Update CLAUDE.md: Current Priorities section with next week’s top 3.

The weekly review used to take 45 minutes of staring at your notes trying to remember what happened.

Now it takes 10 minutes to read what the system generated and 2 minutes to add anything it missed.

Workflow 4: The Queue Processor

Every 2 hours this workflow checks 05 - QUEUE for any files you dropped there.

The convention is simple. Name the file with a verb and a topic:

RESEARCH-stoic-philosophy-applications.md SUMMARIZE-project-meeting-notes.md
DRAFT-email-to-landlord-about-repairs.md PLAN-trip-to-portugal-october.md DECIDE-whether-to-accept-new-client.md

The workflow reads the filename to understand the task type and the file content for specific instructions.

The Claude prompt:

Check the QUEUE folder for any unprocessed files.

For each file found:

1. Read the filename to identify the task type
2. Read the file content for specific instructions
3. Execute the task using the relevant skill from SYSTEM/skills/ if one exists
4. Save output to GENERATED/[task-type]/[DATE]-[topic].md
5. Move the queue file to ARCHIVE/queue-processed/

Log all queue processing in SYSTEM/logs/queue-log.md.

If the task requires information not available in the vault: Flag in the output as NEEDS HUMAN INPUT: [what is needed]

The queue processor is the most powerful workflow in the system because it handles anything.

You think of something you want at midnight. You drop a file in the queue. It is processed by 2AM. The output is waiting when you wake up.

Workflow 5: The Project Health Monitor

Every Monday at 7AM this workflow checks all active projects.

The Claude prompt:

Read CLAUDE.md for the list of active projects. Read the overview.md file in each active project folder. Read any project files modified in the last 7 days.

For each project generate a health assessment:

STATUS: On track / At risk / Stalled / Blocked

EVIDENCE: What specifically indicates this status. Be concrete. Name files, dates, and specific observations.

NEXT ACTION: The single most important thing this project needs in the next 48 hours.

FLAG: Any project that has had no activity for more than 7 days. These need human attention.

Save health report to: GENERATED/briefings/[DATE]-project-health.md

For any FLAGGED projects: create a file in QUEUE named: REVIEW-[project-name].md with a summary of the situation.

The project health monitor surfaces problems before they become crises. A project that has been stalled for seven days gets flagged on Monday morning rather than discovered in a panic when a deadline arrives.

The Anti-Breakdown Features

The operating system is designed with three specific anti-breakdown mechanisms.

The Capture Safety Net

Everything goes to 00 - CAPTURE first. No decision is required at capture time. You never skip capturing something because you do not know where to file it. The capture folder absorbs everything and the processor files it later.

This means the system survives your busy days intact. On a day when you have no time for anything you still capture to 00 - CAPTURE. The processor handles the rest that evening automatically.

The Archive Never Delete Rule

Nothing in this system ever gets deleted. Completed projects move to ARCHIVE. Outdated references move to ARCHIVE. Processed captures move to ARCHIVE.

This means the system never loses information. You cannot break it by archiving too aggressively. The cost of keeping everything is zero because storage is infinite and the system never requires you to browse the archive for daily operation.

The CLAUDE.md Single Source of Truth

Everything about your life that Claude needs to operate exists in one file. One file to update. One file to review. One file that governs every workflow.

When your priorities change you update CLAUDE.md and every subsequent workflow reflects the new reality automatically. You do not have to update five different documents or re-explain your situation in five different sessions.

The Build Order That Gets You Running in One Weekend

Build the system in this exact order. Resist the urge to build everything simultaneously.

Saturday Morning: Storage Layer

Create the eight folders. Set up the CLAUDE.md with your actual current information. Write one project overview for your most active project with consistent properties.

Time required: 2 hours.

Saturday Afternoon: Intelligence Layer

Install Claude Desktop. Configure the Filesystem MCP. Point it at your vault. Run the first morning briefing manually and verify it produces accurate output based on your CLAUDE.md.

Time required: 1 hour.

Saturday Evening: First Queue Task

Drop one file in your QUEUE folder with a real task. A research topic you have been meaning to explore. A decision you have been postponing. A summary of notes you took this week.

Let Claude process it. Review the output. Note what to improve in your CLAUDE.md.

Time required: 30 minutes.

Sunday Morning: Automation Layer

Set up N8N. Build the morning briefing workflow as a cron job. Let it run at its scheduled time and verify the output appears in GENERATED automatically.

Time required: 2 hours.

Sunday Afternoon: Remaining Workflows

Add the capture processor, weekly review generator, and queue processor as additional N8N workflows.

Time required: 2 hours.

By Sunday evening you have all five workflows running. The operating system is operational.

What Never Breaking Down Actually Looks Like

Three months after building this system you will notice something.

The system has been running the entire time.

Not because you maintained it perfectly. You did not. There were weeks where you barely touched Obsidian. There were days where captures piled up in 00 - CAPTURE for three days before you thought about them.

But the morning briefing kept running every morning. The captures kept getting processed every evening. The weekly review kept generating every Sunday. The project health monitor kept flagging stalled projects every Monday.

The system kept operating whether you were operating it or not.

That is the difference between a productivity tool and an operating system.

A tool requires you to use it.

An operating system runs.

Build the foundation this weekend.

The operating system runs from the first morning it is live.

Follow @cyrilXBT for the exact CLAUDE.md templates, N8N workflow configurations, and Filesystem MCP setup that makes this entire architecture run.