fndry.sh> Read the Architecture Philosophy

Architecture for Agentic Work

Essays on designing systems in which people set direction, agents do substantial work, and accountability survives the handoff.

What changes when software stops waiting for every click and starts doing real work on our behalf? The answer cannot simply be “add AI” to the architecture we already have. We have to rethink who may act, where truth lives, how intent survives execution, which decisions still need a person, and how anyone is supposed to understand the system without becoming its full-time operator.

That is what this series is about. Not AI architecture as a new collection of boxes, but architecture for a world in which people set direction, agents do substantial work, and accountability still has to survive the handoff. Information architecture and system architecture become one discipline. Constraints become useful design material. Outcomes matter more than supervised activity. And the system, not another layer of human ceremony, carries the burden of governance.

The essays are meant to stand on their own, but together they follow a progression from authority to operation:

  1. Architecture Is the Design of Authority
  2. Information Architecture Is System Architecture
  3. Constraints Create Better Systems
  4. Agent Governance Is Not Human Supervision
  5. Outcomes Are the New Unit of Software Development
  6. Architecture Is the Design of Handoffs
  7. Hide Ceremony, Not Substance
  8. Start Small, Build a Platform
  9. Adoption Is an Architectural Concern
  10. The Moment You Choose It, It’s Legacy
  11. If the Name Changes, Did the History Change?
  12. From Intent to Operated Software

The Agentic Software Economy

If agents make useful software dramatically easier to reproduce, the change will not stop with development. It will alter how software reaches people, what platforms control, what buyers are willing to pay for, and which responsibilities still justify a vendor's margin. These essays examine that economic layer without pretending every application should become local or every SaaS company is about to disappear.

  1. What If We Distributed the Instructions Instead of the Software?
  2. Software Is Competing with the Cost of Building It Yourself