DAACBlog · what actually happenedno fixed schedule

Occasional notes on how the work actually goes.

Not a content calendar and not a release feed. When something about what we built, or how it went, is worth telling straight, wrong turns included, it goes here.

The machine room

Nothing gets stranded in the scratchpad

Fifty-two overnight sessions; forty-three held findings nobody else could find. Anything that lives in only one memory, human or agent, is lost to the community: the logging discipline that stops knowledge stranding in private scratchpads.

Building with agents

Getting your system to know you

Occasional moments when the machine assembles the questions it wants a human answer to: premise-checked so every question is genuinely open, executed same-session so every answer moves something.

Markets too small to matter before

Ben's 2026-07-31 positioning statement, and why it extends sector-wise rather than by geography: three conditions define the markets DAAC builds for, not a map. The honest hedge: it is a strong leaning tested against a growing list, not a finished doctrine.

Building with agents

Sunflower seed

A subscription per company, a login per subscription: the shuffle is a symptom of vendors owning the interface. A reflection on one owned interface over every working estate, where sessions are views over durable records and the vendors plug into you.

Building with agents

Turn your solution into a blueprint

One night, three repairs that refused to stay repairs: a hand-edit turned into a tool verb, an improvised mark turned into a ratified convention, a cleanup turned into machinery. A fix nothing inherits is a loss.

Method stories

Even machines disagree

How we turned a human's recorded rejections into six criteria, ran nine models blind against the identical brief on a neutral harness, and let the human score without knowing authorship, bugs, non-convergence and cost included.