New in the Lab: Ghostctl, a command-line tool for managing Ghost instances at scale.
Topic
Taste, tradeoffs, and the human decisions behind good software.
A trace can show what an agent changed and who approved it. It cannot prove that anyone exercised judgment. When nobody reads every line, control depends on evidence, authority, and the power to stop.
An agent cannot respect a decision it cannot find, scope, and test. Architecture must become usable context before it can become an effective control.
As agents drive down the cost of a first draft, the bottleneck moves to deciding what should exist and producing enough evidence to trust the change.
Shift left moved the work earlier and dumped it on developers. Shift down moves the complexity into the platform, so they never have to carry it at all.
For thirty years we built developer platforms for developers. The next ones are built for the agents developers delegate to.
A golden path built for humans is a recommendation. A golden path built for a machine has to be an interface.
A platform team that rules by doctrine gets compliance. A platform team that runs like a product gets adoption. Only one of those is worth anything.
AI will make some teams smaller. It will not make the work lighter.
The next phase of AI-assisted engineering will not be more magical. It will be more explicit.
Agentic engineering is the discipline of making software work explicit enough that machines can safely help with it.
AI-assisted development rewards engineering clarity because faster execution amplifies the quality, ambiguity, and governance of the system around it.
Alfred shows why agentic engineering starts before code: tickets need enough context, constraints, and evidence for machines to help safely.
AI-assisted PR review only works when agents can bring issue context, implementation evidence, and review intent into the same engineering surface.