Summary: There are two routers in this lab. The gateway decides what kind of thing you're asking about. This one sits a layer down, inside the personal-memory service, and decides how to answer onc...
Summary: The previous post produced tidy tables from my daily notes. This one turns them into something searchable - a database for the crisp parts, a vector store for the language, and a nightly r...
Summary: Everything so far has been infrastructure - machines, monitoring, a voice, a router. Useful, and none of it knows anything about me. This post is where that changes: a parser that reads my...
Summary: The previous post left the gateway needing to sort sentences into categories. The good version of that turns out to require no training, no labelled dataset, and no fine-tuning - just an e...
Summary: Sometimes it takes a wall of blinking lights to realize your machines have been trying to talk to you all along. The Higher Brain Monitor is a small, human first, experiment in ambient ph...
Summary: Once the lab could hear me, it had a new problem: it had no idea what I was talking about. "What did I write about last Tuesday" and "what's the capital of Peru" and "turn the office light...
Summary: The previous post ended with a request ID threaded through six services. That's only useful if you can read all six services' logs in one place, which is what this post is about. The desi...
Summary: I've been working through a better way to manage personal and project knowledge in the homelab, with an eye on enterprise use of AI that is precise, cost effective and applicable to automa...
Summary: This is the post the whole lab is really about. Everything up to now - the machines, the monitoring, the lights on the wall - was scaffolding for one thing: being able to say something out...
Summary: The lab has a web interface with about fifteen pages, and exactly one user. That combination produces different design decisions than anything I've built professionally, and the difference...