Human-facing vault interface for Markdown notes, links, and durable context.
Software
The daily software layer behind Viggo Meesters’ workflow: Obsidian, Hermes, GitHub, Vercel, Telegram, and delivery tools.
Agent runtime and command bus around tools, sessions, scheduled tasks, and skill routing.
Public repos and static deployments for demos, website pages, and project artifacts.
Fastest interface for commands, capture, steering, and delivery.
Software is the working environment around the vault, repos, browser, documents, and communication channels.
It matters when a daily app or service becomes important enough that readers need it to understand the workflow.
Skip incidental utilities and one-off experiments.
Group tools by job: writing, communication, storage, browsing, planning, and review.
Software belongs here when it is a stable part of the work loop: writing, communication, knowledge management, design, or project delivery.
A software entry earns its place when removing it would change how work is captured, reviewed, published, or resumed.
It matters when a daily app becomes the default for writing, planning, communication, vault work, or publishing; remove tools that are only historical preferences.
Obsidian is listed because it is the human-facing editor for the vault, while the vault schema and validation logic belong to the Personal Knowledge System pages.
Mention durable workflow roles, not account details, private workspaces, personal data locations, or app-specific configuration that would become stale or sensitive.