I've never kept a devlog before, and I'll try my best to keep this up as
development goes on. I've backfilled parts of the journey that I could remember.
I got Claude's help on some of the sequencing. The truth is that I've become a
little obsessed with this project. It's crowded out other hobby pastimes for
now, but it thoroughly integrates quite a few of my interests at once.

This project will be a long-term pursuit of mine, because it's currently running
my home systems, and thus I _must_ continue pursuing it. It also keeps paying
back in utility the more I develop it, which is not true of many of my side
projects. It is how I felt about [Docket](https://docket.lol). That has to be a
good sign.

Taking the day to establish this devlog and renew a commitment to daily writing
feels like a further investment in the project's long-term health as well.

While there's still more iteration and polish to do on the media-operator, I can
already feel the gravity well of a library browser and management system to
rival the venerable [Jellyfin](https://jellyfin.org/). It's just obvious this is where I'm heading to
very soon.

There's also a wildcard detour I could take with [Spotify
Soloist](https://developer.spotify.com/blog/2026-08-13-introducing-spotify-soloist)
to take a swing at music and supplanting [Music Assistant](https://www.music-assistant.io/). I'm not
sure which direction is pulling me more strongly. The wonderful thing about
sitting at this vantage point is that I can see so many places to go: whole home
media library and playback, a `camera-operator` to build a K8s-native NVR
system, or taking a fresh swing at an autonomous agent built directly into the
k3s cluster.