I built a research pipeline to help me pick a Dutch e-commerce niche to launch into. Version 1 pointed me at one. I launched a webshop on it, made a sale, and shut the shop down for reasons the pipeline had no way to see. Version 2 was built with more rigor and I trusted it less, because by then I had learned which layer of the problem a pipeline like this doesn't touch.
Most agent frameworks default to call the model again. This post is about a personal agent built around the opposite default — do we actually need to call the model this time? — and the four pieces (main loop, scheduler, provider layer, setup flow) that fall out of taking that question seriously. The project is currently shelved; the parts that survive into the next iteration are the scheduler, the preprocessor pattern, and the provider abstraction.
This is the first post on the site, so it is the one place where I explain the thing rather than doing the thing. Future posts will go straight into the problem at hand — a production system misbehaving, a research run that came back with something interesting, or an independent project that needs an honest write-up. This post is the index: who's writing, what I'm working on, and what the blog will cover once topical posts start landing.
