Everything in one place

not accepted

Everything is plain files, easy to look at from one place — for example Obsidian; symlinks back to the project repos keep it together.

On this page

Author

owner

Created

14 October 2026

Updated

14 October 2026

Review

not shown

kind

value

Everything is plain files, easy to look at from one place — for example Obsidian; symlinks back to the project repos keep it together.

In practice§

Markdown and YAML in git; project specs are reachable from the user's home through symlinks.

Trade-off§

No database queries and no concurrent writes.

Referenced by§

ADRs

• Specs are a core feature in three tiers adr/0001 accepted via Serves values
• A plan is a directory whose index.md is both plan and run artifact adr/0009 accepted via Serves values
• The task tracker is a best-effort mirror of the vault adr/0019 accepted via Serves values
• Each project publishes its specs site on GitLab Pages, under one index adr/0029 accepted via Serves values
• The owner reviews specs on the site and hands the review to an agent adr/0032 accepted via Serves values
• Journal entries are vault files built from existing primitives adr/0037 accepted via Serves values

Rules

• Vault artefacts are plain markdown with YAML frontmatter rule/0028 accepted via Follows from
• Private sources stay in vault/notes rule/0033 accepted via Follows from