Build Logs

The work is not a line

Every delivery process I've ever worked in is shaped like a line — plan, design, build, test, release, operate — and most plans for adopting agents just slot them into it. So I put a meter on three days of real work with my agent: 185 activities, every one classified and plotted. Then I had a second model attack the dataset and a third blind-rate a sample, so what's here survived cross-examination. If you're deciding how agents fit into your ways of working, this is the shape of the thing you're planning for — and it is not a line.

The work before the work

A project that hasn't been built yet, written up anyway. The order I plan in, why the design has to cover running the thing and not just standing it up, and what happens when I hold my own method up against the findings on this site. Four of my habits survive it. Four don't.

Agent observability and performance

Past entries keep saying there's an agent doing the work around here. That's been talk. This is the instrument panel I actually use to watch it: what it costs, what it remembers, what it can do, and how it gets tuned. Real screenshots, sensitive bits blurred, everything else as I see it.

Hands last

The control panel was the goal from day one, and it was the last thing built. Three weeks of read-only discovery came first, on purpose. The machines being wired up were the ones that couldn't be replaced.