Knowledge / Assistant / Operations
One vault of notes, and an assistant that reads it.
Everything I write goes into one vault of notes. An assistant on a small server reads it, answers me on Telegram and writes a summary of the day every evening.
The assistant is OpenClaw in Docker on a rented server. The notes are indexed for semantic search, so a question finds notes by meaning and the answer quotes them.
My workI set it up and run it: the server, the scheduled jobs, the vault’s structure and its search index.
SinceMarch 2026
Routine / Scheduled jobs
The assistant’s day.
- 03:30 UTCThe vault is committed to git, as every night.
- MorningThe day’s priorities.
- 08:00–22:00A check-in once an hour.
- 21:00The summary of the day, written into the vault.
Every night the vault is committed to git, so each night’s saved version of every note can be recovered.
In the morning the assistant sets out the day’s priorities, it is scheduled to check in once an hour during the day, and in the evening it writes the summary of the day into the vault.
Decision / Search
Search covers a list of folders.
I list the folders included in semantic search.
A new top-level folder needs adding to the list; notes inside an included folder are indexed automatically. A folder left off the list stays out of search. That is a choice about search, not an access control.
- Assistant
- OpenClaw · Docker on a rented server · Telegram
- Search
- The vault indexed with text embeddings
- Graph
- Computed from the vault’s links with a force layout in Python
Sources: the vault itself (its links, nightly snapshots and daily logs) and the assistant’s operations notes; none is public. The graph is computed from the links only: no title or text is in it. Its counts are from 6 October 2026.