Andrew Dunne

Increasing Iteration Frequency

2026-06-20T00:00:00+00:00

Once we’ve reached a fully-declarative framework, where we only define tickets and create new projects, we are prepared to begin pursuit of Gate 3: Autonomous Development. This concept primarily exists as a mechanism by which to accelerate many forms of iteration.

For example, if we are prototyping an iPhone app, we might add a button in the developer environment which allows us to open a chat dialogue on any given page with an agent. There, we can discuss with a company agent directly what feature’s we’d like to see changed/improved. It will assess the complexity of the request, and only follow-up as much as required.

The agent can then, using a tool like Substrate, invoke downstream agents to take care of the feature-change, using the proper pipeline/task/workflow mechanisms that your project adheres to.

The Three Gates of Agentic Development

2026-06-20T00:00:00+00:00

There are three gates in applied AI when it comes to development:

At The Delegation Phase, you work on tickets, and have an agent dispatch new agents to handle those tickets. I rarely work with an implementing agent, but sometimes do when issues arise.</li>
At The Orchestration Phase, you arrange a pipeline of either skill or agent invocations which are implemented strategically at every phase from ideation -> in production. Each step in this process is managed by an Agent who solicits your input only when needed.</li>
Autonomous Development Phase - By continously analyzing user-data and feedback, agents autonomously deploy client updates all the way to production with zero user-intervention required. At prototyping phase, this may look like developer input in-app via a feedback form which, after gathering any needed decisions, is translated autonomously into changes to an app. In enterprise environments, this may appear, for example, as autonomously-generated A/B tests which are administered and applied with configurable amounts of human-in-the-loop.</li> </ol>

Foundation Work

2026-06-18T00:00:00+00:00

One of the challenges I’ve encountered while attempting to stand up so many different prototypes over the years, is managing their service dependency accounts.
I’ve built games that needed unity, websites that ran on vercel, and cloud-native applications that used everything from cloudflare and AWS. When you factor in even basic foundational elements like version control and secrets management, you wind up with a lot of different accounts managing a lot of different services.
At first, I kept track out these concerns by bundling them all under various aliases within my personal domain at andrewdunne.com.
Today, I discovered ProtonMail offers fantastic pricing for users who have many custom domains - exactly my use case. I spent the day spinning up Codex Computer Control on my machine and had it migrate all my domains over to Route 53 / setup MX/TXT/DKIM records for each domain. Arkship is managed by Cloudflare, but Codex handled that smoothly as well.
That was the main thing to celebrate! Had a lengthy call going over our v1 spec for the newest project: Sift, and with everything in order I think we will make very quick progress to get that out to our first (small) batch of users.
Got a new weekend project in the works with my wife as well that I think will be fun, and got to try out my new massive revamp (courtesy of Fable’s short-lifespan) to my Agent Stack (aplty-named Ark-Agents). So far so good, but we will see more in the coming days.
That’s all for today!