---
title: "Discussion on \"Stop Choosing an Obsidian Template. Engineer a Vault Architecture.\" | Hashnode"
description: "Discussion on \"Stop Choosing an Obsidian Template. Engineer a Vault Architecture.\". A practical comparison of Ideaverse, PARA, kepano, and Zettelkasten - with YAML, folder trees, workflows, and a maintainable hybrid for real engineering work."
url: "https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop Choosing an Obsidian Template. Engineer a Vault Architecture.](https://daisuke.masuda.tokyo/article-2026-10-26-0519?utm_source=hashnode&utm_medium=feed)

A practical comparison of Ideaverse, PARA, kepano, and Zettelkasten - with YAML, folder trees, workflows, and a maintainable hybrid for real engineering work.

Oct 25 · 19 min read · daisuke.masuda.tokyo  
Read the article

-   [#obsidian](https://hashnode.com/tag/obsidian)
-   [#personal-knowledge-management](https://hashnode.com/tag/personal-knowledge-management)
-   [#note-taking](https://hashnode.com/tag/note-taking)
-   [#productivity](https://hashnode.com/tag/productivity)
-   [#documentation](https://hashnode.com/tag/documentation)

## Written by

[Daisuke Masuda](https://hashnode.com/@x5gtrn)

@x5gtrn · Hyogo, Japan

  
[View profile](https://hashnode.com/@x5gtrn)

DJ Ekusi, SAEKIKAZUMI

Daisuke Masuda (born January 1982), also known as x5gtrn, SAEKIKAZUMI, or DJ Ekusi, is a Japanese software developer who aspires to gain recognition as a DJ. I balance programming and DJing as my lifelong pursuits and am a devoted enthusiast of both music and literature. I am a passionate admirer of Richie Hawtin, Sven Väth, Ryuichi Sakamoto, Ryu Murakami, Kenji Eno, and THA BLUE HERB. I draw inspiration from their creativity and vision.

## Responses 4

Markdown supported · ⌘↵ to post

[Crownforge](https://hashnode.com/@thecrownforge)

[Oct 27](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28/comment/6ae0789987f3dfa3c6294f41)

When an ADR is superseded, how do you flag the runbooks and knowledge notes that still depend on it? Keeping the old decision is useful, but I would want the current instructions to show that they need another review

[Daisuke Masuda](https://hashnode.com/@x5gtrn)

[Oct 27](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28/comment/6ae0789987f3dfa3c6294f41#reply-6ae08370432ab635a1b322cc)

Yes—that is an important distinction. I would keep the superseded ADR as historical evidence, but change its metadata to something like `status: superseded` and `superseded_by: ADR-0042`.

For runbooks and knowledge notes, I use an explicit field such as `depends_on: [ADR-0017]` or a direct link to the ADR. A review query can then surface every current note that still depends on a superseded decision. I would not automatically mark those notes as wrong—the operational guidance may still be valid—but I would flag them as `review_required` until someone verifies them against the replacement ADR.

That preserves the decision trail while making the possible blast radius visible. It is also a good example of why queries should be treated as views: the durable truth is the explicit dependency recorded in each note, while the query simply shows which dependencies now require attention.

[Indie Ship Log](https://hashnode.com/@indieshiplog)

[Oct 26](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28/comment/6adf01be526d33fbe6c6e9f4)

I bounced between PARA and a zettel-style pile for a year, and the vault got slower to trust than a plain notes folder. The line that landed is that queries are views, not truth. A small folder contract plus a couple of YAML fields made retrieval calmer without adopting a famous template. The Spring Boot latency walkthrough is what makes the hybrid feel like real work.

[Daisuke Masuda](https://hashnode.com/@x5gtrn)

[Oct 26](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28/comment/6adf01be526d33fbe6c6e9f4#reply-6adf98aea80e040568ca2c29)

That’s exactly the failure mode I wanted to address: once the vault’s structure becomes harder to trust than a plain folder of notes, the system is working against you. Treating queries as disposable views—and keeping truth in a small, explicit folder and metadata contract—makes hybrid approaches much less fragile.

I’m especially glad the Spring Boot latency walkthrough helped. I wanted the architecture discussion to survive contact with real engineering work, where one incident can involve logs, hypotheses, source material, decisions, and reusable knowledge without all of them becoming the same kind of note. Thanks for articulating this so clearly.
