Files
agent-estate-wiki/systems/obsidian.md
T

2.3 KiB

title, type, status, created, updated, verified_on, confidence, tags
title type status created updated verified_on confidence tags
Obsidian Vault systems active 2026-07-26 2026-10-20 2026-10-20 high
obsidian
notes
vault
homelab

Obsidian Vault

Purpose

Personal knowledge base — notes, research, projects, and agent documentation.

Details

  • Location: /home/hermes/wiki/ (on CT460)
  • Git repo: Gitea (Anthony/obsidian-vault)
  • Structure: NUMBERED folders (00-99)
  • Sync: Git-based (manual or cron-triggered)

Re-verified 2026-10-20 — the "NUMBERED folders (00-99)" description is no longer accurate. On disk there are now only two vault-shaped directories on CT460:

  • /home/hermes/obsidian-vault/ — contains 50 - Research/ (with Restaurants and Cafes/) and Cron Outputs/ (with Weekend Adventure/). No 00 - Home, no 10 - Inbox, no 20 - Agent Notes. This directory is not a git repo (git -C → "not a git repository").
  • /home/hermes/wiki/ — a local-only git repo (no remote configured) whose tracked content is the agent-estate-wiki/ mirror plus reports/uber-eats/. Its .obsidian/ dir is under wiki/agent-estate-wiki/.obsidian.

So the numbered-folder tree described below is largely absent, and the vault that is mirrored to Gitea is the agent-estate-wiki repo (Anthony/agent-estate-wiki), not Anthony/obsidian-vault. Treat the folder table as historical. Separately, an Obsidian LiveSync service runs on CT100 (obsidian-livesync) on the m93p host (/opt/obsidian-livesync/, holds only a .env). Full folder table, left for reference:

Folder Structure

Folder Purpose
00 - Home Dashboard and entry points
10 - Inbox New/unprocessed notes
20 - Agent Notes Notes from AI agents
30 - Projects Active project documentation
50 - Research Research and investigations
60 - Resources Reference materials
70 - Reference Quick lookup
90 - Archive Completed/old material
99 - Templates Note templates

Conventions

  • Numbered folders preferred (Anthony corrected twice)
  • Check Mnemosyne before vault work
  • Don't impose structure changes without understanding usage