Systems & tools

Build a life OS in Obsidian

The same plain-files build, plus the one thing files alone cannot do: links that let an area's history assemble itself. The vault structure, the weekly template, the two plugins that matter, and the restraint that keeps a vault from becoming a hobby.

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

The short answer

To build a life OS in Obsidian, create a vault with a small folder tree (inbox, areas, weeks), set up a weekly note template with the core Templates plugin, and link each week to the areas it touches, so every area's history assembles itself in backlinks. Then run the rhythm: capture all week, write the weekly note each Sunday. Start with two plugins, not twenty.

Steps

  1. 1

    Create the vault from the standard tree

    An Obsidian vault is just a folder of markdown files, so the plain-files structure transfers unchanged: inbox.md, an areas folder, a weeks folder, grown later with quarters, reference and archive. If you already run the plain build, open the folder as a vault and you are migrated; nothing converts because nothing needs to.

  2. 2

    Set up the weekly template

    Turn on the core Templates plugin, point it at a templates folder, and make one file: the weekly note (noticed, this week's plan, learned), using the built-in date variable for the title. Sunday becomes: new note, insert template, fill it in. One hotkey removes the only friction the rhythm has.

  3. 3

    Link the week to the areas it touches

    As you write the weekly note, link area names where they appear naturally. That single habit is the whole connection layer: open any area note and its backlinks list every week that touched it, in order, without you maintaining anything. The area's history assembles itself as a byproduct of planning.

  4. 4

    Give capture the same one door

    All captures land in inbox.md, on desktop via a hotkey and on the phone via Obsidian's mobile app pointed at the same vault. Keep the capture rule: one place, no sorting in the moment. The inbox gets read once a week, on Sunday, and that is its entire lifecycle.

  5. 5

    Run the Sunday half hour, then stop building

    The rhythm is identical to the plain build: read the inbox, look four weeks ahead, write the weekly note, and close the week with one learned line. Everything Obsidian adds is in service of that half hour. When the session runs weekly, the vault is finished, whatever the plugin gallery says.

What Obsidian actually adds

Start with what it does not change: an Obsidian vault is a local folder of plain markdown, so everything that makes the plain-files build durable survives intact. Your notes open in any editor, sync over any file-sync service, and would outlive the app itself, which is precisely why this is the natural second home for a life OS: you trade none of the ownership for the upgrades.

The upgrade that matters is links. In plain files, connection is a convention you maintain; in Obsidian it is a first-class object the app maintains for you. Write the week with area links in it and the assembling happens in the background: the health note accumulates every week that mentioned health, the backlinks panel turns a year of weekly notes into an area's readable history, and a thread (how did the money situation develop since spring?) becomes a click-through rather than an archaeology session. The second, smaller upgrade is the Templates plugin: the weekly page stamps itself, dated, from one hotkey.

The build, in Obsidian terms

The tree is the standard one, so take it from the template rather than inventing: inbox.md at the root, areas with one charter per part of life that has earned one, weeks holding one note each, quarters, reference and archive appearing under pressure. Obsidian needs nothing configured to respect this; folders are folders.

Two settings do the heavy lifting. First, the core Templates plugin: give it a templates folder, put the weekly note and the area charter in it, and learn the insert-template hotkey. The built-in date and title variables stamp the week header for you. Second, default new notes into the inbox, so a stray thought captured mid-task lands where Sunday will find it. That is the entire required configuration; everything else in settings can stay exactly as installed.

The restraint that keeps a vault working

Obsidian's plugin ecosystem is genuinely excellent and the single biggest threat to your system, because configuring a vault feels exactly like improving your life while replacing the part where you run it. The working rule: core Templates plus, if you want automated weekly notes, the community Periodic Notes plugin, and then an eight-week freeze. Every plugin after that must name the real pile it solves. Dataview deserves its own honest sentence: it can query your notes like a database and some builders love it, but it adds a query language to maintain and moves your notes toward depending on machinery again. Adopt it when hand-curated lists genuinely stop scaling, not before.

The graph view deserves one too: it is a lovely picture and it is not your system. A vault can look like a galaxy and hold no runnable week. Judge the build on one question only, the pillar's test: if you stopped, would anything happen next Sunday? The template hotkey and the standing half hour are what make that answer yes.

The ways Obsidian builds fall apart

The vault rarely fails as software. It fails as a system in recognisable ways:

  • The plugin spiral: a week of setup, no weekly notes. Configuring feels like progress and is not. Two plugins, eight-week freeze, then review
  • The graph gazing: judging the vault by how the constellation looks. The graph is a byproduct. The weekly note is the product
  • The daily-note drift: daily notes without a weekly layer, so the vault remembers everything and decides nothing. The week is where deciding lives
  • The collector's vault: clippings and highlights in, plans never out. That is a second brain, a fine thing that is not this thing. The weekly note is what makes it run
  • The sync improvisation: two devices, two sync services, one conflicted vault. Pick one sync mechanism for the whole vault and let it be boring

Where a built tool honestly beats this

A well-run vault holds and connects everything, and the backlinks make its history genuinely explorable. What it still does not do is read the week for you: the links assemble the past, but nothing looks across your areas on a Wednesday and says the deadline moved, the birthday is three weeks out, health has gone quiet since the month turned. In Obsidian, noticing remains a manual discipline spent from the same attention your week is short of. That is the honest boundary: asambl runs the same loop with the noticing done deterministically and a drafted week proposed for you to judge, and it happily coexists with a vault, which keeps the long-form thinking asambl does not want to own.

If the Sunday half hour is reliably yours, the vault plus this structure is a complete and honourable life OS. Plenty of people should stop here.

Sources

checked 26 July 2026

Obsidian feature descriptions checked against the official help documentation, accessed 26 July 2026.

  • Obsidian Help, Templates core plugin: template folder, insert command, and the date and title variables used by the weekly note.
  • Obsidian's vault model (a local folder of markdown files) as documented across obsidian.md; the ownership argument in this guide rests on it.
← All guides