technology

Together, then taken apart

October 8, 2026

Here is the thing we want. A ticket gets a label and, some minutes later, a draft pull request is waiting for you. Three separate pieces made it: one decided what to run and when, one set the rules an

Next notch

The factory remembers, and memory never decides

October 8, 2026

Here is the thing we want. A factory works through a pile of tickets overnight and some of them fail. In the morning you do not want a count. You want an answer: what failed, with which exit code, wha

Next notch

The factory drives the harness

October 8, 2026

The question I used to ask was whether the agent could be talked into something. It can. Anything that reads text can be talked into something, and a ticket is text written by whoever can open an issu

Next notch

The factory decides

October 8, 2026

Here is the thing we want. Someone labels a ticket, and a little later there is a draft pull request for it. Nobody typed a command. Every decision on the way is written down where you can read it bac

Next notch

The memory remembers

October 8, 2026

Here is the thing we want. An agent finishes a task, and what it learned does not vanish with the session. The next session, on my machine or a colleague's, starts knowing that the tests need a clock

Next notch

The harness guides

October 8, 2026

Here is the thing we want. You hand a coding agent a task, and before it starts you already know three things: what "done" means, how much it is allowed to spend getting there, and what it cannot do n

Next notch

Three layers, three refusals

October 8, 2026

I asked a coding agent to remember my name. It wrote the fact into its own memory directory. Not the memory I had just installed for it. Its own.That one line of behaviour cost me an archit

Next notch

Technology

Together, then taken apart

The factory remembers, and memory never decides

The factory drives the harness

The factory decides

The memory remembers

The harness guides

Three layers, three refusals