Vault Structure

LogMark stores everything as markdown files in a folder you choose. This page explains where entries go and how files are organized.

Top-Level Layout

your-vault/
  logmark/
    _diary/              # Log entries (no type prefix)
    _tasks/              # Unrouted tasks
    _ideas/              # Unrouted ideas
    _blocks/             # Unrouted blocks
    _decisions/          # Unrouted decisions
    projects/            # Project routes
      backend/
        _tasks/
        _ideas/
        ...
    domains/             # Domain routes
      photography/
        _ideas/
        ...
    _system/             # LogMark internals
      log.md             # Capture history
      routes.md          # Route definitions
      config.md          # Settings
      assets/            # Pasted images

Everything lives under a logmark/ folder inside your vault. If you point LogMark at an existing Obsidian vault, your other vault content is untouched.

Yearly Files

Entries are appended to yearly files, one per type per location:

logmark/_tasks/2026.md # All unrouted tasks for 2026
logmark/_ideas/2026.md # All unrouted ideas for 2026
logmark/_diary/2026.md # All log entries for 2026

A new file is created automatically on January 1st. No configuration needed.

Entry Format

Each entry is appended with a timestamp header and optional context footer:

---

## 2026-02-04 14:32

cache invalidation might fix the flaky test #performance

context: VS Code, parser.ts
  • --- separator between entries
  • ## YYYY-MM-DD HH:mm timestamp header
  • Entry content with tags preserved
  • context: footer with application and window title

The format is standard markdown. Open these files in Obsidian, VS Code, or any text editor.

Routed Entries

When you use +project or +domain notation, entries go to the route's folder:

+backend t: fix the memory leak
Saved to: logmark/projects/backend/_tasks/2026.md
+photography i: try bracketing for HDR
Saved to: logmark/domains/photography/_ideas/2026.md

Two-Level Routes

+backend/auth t: add rate limiting
Saved to: logmark/projects/backend/auth/_tasks/2026.md

On-Demand Creation

Folders and files are created when first needed. You don't pre-create structure - LogMark builds it as you capture.

Type Mapping

Entry typeFolderExamples
task: / t:_tasks/Actionable items with optional deadlines
idea: / i:_ideas/Thoughts worth preserving
block: / b:_blocks/Where you're stuck
decision: / d:_decisions/Choices made
(no prefix)_diary/Free-form log entries

System Files

logmark/_system/ contains LogMark's own files:

log.md - Chronological history of all captures with Obsidian wikilinks:

2026-02-04 14:32 - Saved task to [[logmark/_tasks/2026|tasks]]: "fix the memory leak"
2026-02-04 14:35 - Routed idea to [[logmark/projects/backend/_ideas/2026|backend ideas]]: "cache scores"

Used by the /recent command for fast chronological browsing. Each line links to the entry location.

routes.md - Route definitions (projects and domains).

config.md - LogMark settings stored in your vault.

assets/ - Pasted images saved here, referenced from entries as [image] placeholders.

Subpages

Long pastes and HTML content create subpages:

logmark/projects/backend/_tasks/pages/2026-02-04-fix-memory-leak.md

The main entry contains a wikilink to the subpage with a preview. The subpage contains the full pasted content.

Obsidian Compatibility

The vault format is designed for Obsidian:

  • Standard markdown with frontmatter
  • Wikilinks in system log ([[path|display]])
  • Tags preserved as-is (#performance, #urgent)
  • Folder structure browsable in Obsidian's file explorer
  • Graph view, backlinks, and search all work on LogMark entries

LogMark captures. Obsidian explores. They share the same vault without conflicts.

Multiple Vaults

Switch between vaults from the system tray menu. Each vault is independent with its own routes, settings, and entries. Use separate vaults for work/personal, per-client, or per-project.

The active vault path is stored in %APPDATA%\LogMark\bootstrap.json.

Next
Overview