Daily + Weekly ritual: how to keep the vault alive

The biggest vault paradox: the more notes we have, the less useful they are — if there’s no ritual keeping the system alive. Tools without ritual = an abandoned warehouse. Ritual without tools — also not a real option, but we already have the tools.

Why everything dies without a ritual

After half a year of active work with a vault and no ritual, the typical pattern looks like this:

• 300+ files in 00_Inbox/ — we keep dumping there, nothing gets sorted.
• 20+ projects in 10_Projects/, of which 15 are dead (long closed or forgotten) but listed as active.
• Daily notes for February, March, April, then — empty. The flame burned out around May.
• Templates we spent four evenings configuring sit unused.

This isn’t an Obsidian problem. It’s the problem of a missing cycle. Any knowledge system needs two things: input (new notes) and hygiene (maintenance). No hygiene — rot.

The good news: hygiene takes very little. 10 min a day + 30 min a week. That’s less than we spend scrolling social feeds.

Daily ritual — 10 minutes

Two 5-minute phases. One in the morning, one in the evening. We can merge them, but I don’t recommend it — they serve different functions.

Morning phase — 5 min (intention)

1. Open today’s daily note. If we’ve set up Templater + Periodic Notes (from the previous articles), it’s already created with the scaffold filled in.
2. Fill the “Intention for the day” section. One or two sentences: what’s the one outcome that will make today a success? Not a list of 10 things — one. This is our anchor.
3. Fill the Top 3. Three concrete tasks that move us toward the result. Not “work on project X” — but “write the draft of chapter 2.”
4. Glance at yesterday’s daily note. What’s still open? Move it into today (if relevant) or into the thought archive (if not).

Done. 5 min, no heroics.

Evening phase — 5 min (closing)

1. Fill the “What got done” section. Quickly, in bullets. Not a literary report — facts. If we did nothing — write why. This isn’t self-punishment, it’s honesty.
2. Fill “Reflection” — 2-3 sentences. What worked? What didn’t? What would be worth doing differently tomorrow?
3. Move everything new from 00_Inbox/ into the right folders. If we dropped notes there during the day — give it a minute and scatter them. Usually 3-5 files, a 60-second operation.

Done. The vault stays under control, daily notes have real value a month later (we can come back and see how we were thinking on a specific day).

Weekly ritual — 30 minutes

Once a week. I do it Friday evening — closes the work week. Some people do Sunday — preparing for the new one. Pick our variant; the main thing is same time every week, otherwise we’ll skip.

Structure (30 min)

Phase 1 — Inbox cleanup (5 min). If anything is still sitting in 00_Inbox/ after a week — finish it. What didn’t find its place over a week is either really not needed (delete) or needs a project (create a project folder).

Phase 2 — Review of 10_Projects/ (10 min). We walk through all active projects. For each we ask:

• Is this still an active project? Or has it closed but I haven’t marked it?
• What’s the next step? Have I added it to Tasks?
• Was there progress this week? Why not?

If a project is dead — move it to 40_Archive/. The vault cleans up.

Phase 3 — Weekly review note (10 min). Create the file Weekly_<year>-W<week>.md (or via Periodic Notes — it’ll do this itself). Fill in the template from the previous article: main events, what got done by category, what didn’t and why, lessons of the week, focus for next week — Top 3.

Phase 4 — Planning the next week (5 min). Look at next week’s calendar. What meetings? What deadlines? What’s the main thing of the week? We can immediately create an empty daily note for Monday with the intention pre-filled.

Done. 30 minutes, and we enter the new week not “however it falls” but with a plan.

Monthly and Quarterly review — optional

Once a month — an hour-long session where we go through all weekly reviews of the month and write a monthly summary. What worked? What didn’t? Any patterns?

Once a quarter — half an hour to revisit our Manifesto / Operating Framework (if we have one — I do, but that’s a separate topic). Are we moving in the right direction? Anything to correct?

This isn’t for everyone. Daily + Weekly is the base. Monthly + Quarterly is bonus tier, add it when daily/weekly becomes automatic.

How not to break the ritual — practical tricks

1. Tie it to an existing habit. Morning daily phase — after the first coffee, before email. Evening — before we close the laptop. Weekly — Friday after the last meeting.

2. Low threshold. If we have an exhausting day and the ritual feels too heavy — do the minimum. Just the intention. Just one line of reflection. Bad is better than nothing. The cycle matters more than the depth.

3. No perfectionism. Daily doesn’t need to be pretty. It needs to exist. Missed a day — don’t try to “catch up.” Just start again from today.

4. Count the percentage. Not “how perfect,” but “how many days out of 30 did I do this?” 25 out of 30 — top tier. 5 out of 30 — the ritual hasn’t taken root, review the reasons.

AI as a helper for the ritual

If we have Claude Code set up with the same vault — AI can speed up the weekly review substantially. A few sample prompts:

Look at all daily notes from this week (from [date] to [date]).
Roll them into one short summary: 3 main events of the week,
what's left open, what patterns I can see in my own
reflections. Draft a weekly review for me.

Check the 10_Projects/ folder. Show me projects where
the last commit or file change is more than 14 days ago.
These are candidates for archiving.

Pull all action items from meeting notes this week
that aren't marked done yet. Group them by stakeholder.

We stay in the role of the one who makes decisions (close a project, move a task). The AI does the rough work — gathering data, grouping, drafts.

Common mistakes

1. Wanting a “perfect” ritual with 20 steps. Simpler is better. 10 min + 30 min. Not 30 min + 2 hours.

2. Skipping weekly review “because there’s nothing to write.” That’s the reverse signal — either the week really was empty (rethink what we’re doing) or we’re just tired. In the second case — do the minimum, let ourselves confirm: this week — at 50%.

3. Daily note as a to-do list. That’s not what it’s for. Daily is the recording of thinking and reflection. Tasks live elsewhere (project Tasks file, separate dashboard). Daily is a leading indicator of our life, not an operational tool.

4. Weekly review without archiving. The point of the review is for things to close. If we’re writing about the same project with the same status for 6 weeks in a row — it’s dead. Archive it.

What’s next — possible continuation

Across 8 posts we’ve walked the path from zero — an empty laptop, fear of “code” — to a working personal knowledge system with an AI helper, internet backup, sync, templates and a ritual.

Now we have:

• A vault with PARA structure and a CLAUDE.md that knows who we are.
• An AI helper that remembers us between sessions (memory).
• A private GitHub backup with auto-commit.
• A clear understanding of what to put in the vault and what not to.
• Sync between laptop and phone.
• 9 working plugins (not 30).
• Templates for daily, meeting, project, weekly.
• A ritual that keeps it all alive.

I’m wrapping the series with this article — but a continuation is possible, depending on your questions and interest. If there’s a topic or scenario I didn’t cover — drop me a line on LinkedIn, and I’ll add the relevant post once I have 3-5 similar requests.

The same approach — outside of work

Vault + PARA + AI isn’t only a work tool. The same scaffold scales to personal life, family, and the people around us.

• Family. A separate folder with plans for the year, budget, kids’ medical data, trips. AI can help prep questions for the doctor or summarize a three-page medical record.
• Personal finances. Utilities, banks, loans, insurance — all documentation in one structure. Once a month — a quick review. Once a year — a review of all subscriptions and “why am I paying for this?”
• Taxes and documents. Scans, invoices, contracts — ordered by year. When we need to find something from 3 years ago — seconds, not hours.
• Shared vault with family. If someone in the family also wants to keep notes — a shared private repo, access only for our own. Shared plans, shopping lists, kids’ schedules.
• Work with colleagues. A separate vault for shared projects — same thing, but team access via private git. Once a week we sync up — the way dev teams have been doing it for 20 years.

So the system covers not just the work aspect. It’s a framework for organizing any important part of life where a lot of information piles up — and it’s worth keeping it under control.

Back to the start

If we want to re-read the series from the beginning — Post 1: Building a Personal Knowledge Base on Obsidian + AI.

If we want to follow what comes next (the upcoming topics are different — not Obsidian) — LinkedIn here.