The build log
How each thing was built, written as it happened by Duncan Hyde, including the parts that did not work. New posts are published here and go out on Substack as well.
A website that writes a page for whoever arrives
Cairn is a box on the Hyde Media website: you say what you came for, and a page assembles from the site's own pages, with every section showing where it came from. Here is how I built it, what it got wrong, and what that taught me about my own website.
Fourteen commits, then I handed over the keys
Yesterday I shipped fourteen commits to the personal trainer app I have been building in public. Commit counts mean little on their own, but each of these was a feature or a fix that went live the same day, and the day ended with me sending my design partner her login. This morning she signed in and told me it all looks great. This is what a day like that is actually made of, and what it taught me about the difference between shipping software and handing someone their keys.
I designed my studio with Fable 5. Days later it was switched off.
I used Fable 5 as a design partner to fork two agent systems I already run, my ebikeist Foundry and its agent specs, into a new studio built in Claude Code. Days later the US government had Fable pulled from production, which became the real test of which design choices were durable.
What building two agent studios taught me about trusting machine work
Trusting machine work is knowing when an AI agent's output is good enough to act on. What running two agent studios on real businesses taught Duncan Hyde about it.
How I built a multi-agent studio system to ship my own products
The first entry in Duncan Hyde's build log: the multi-agent system he built to run Hyde Media's studio, why it came before the products, and how it is put together.