AOS Interface Operating System
The Acceleration
Something is accelerating. Not just the speed of tools — the depth of their reach. AI systems are now inside the design process, the writing process, the decision process. Agentic systems are beginning to act on behalf of their users without waiting to be asked.
This changes what it means to work.
The person without a conscious operating system does not disappear — they continue to produce, to publish, to respond. But the logic organizing their work belongs to whoever built the tools they are using. Their attention is allocated by someone else’s priorities. Their output accumulates without orientation. They stay busy and wonder why the work does not compound.
The person with a conscious operating system is in a different position entirely. Not because they work harder or know more — but because they know what they are for. Every new tool, every accelerating capability, every shift in the environment gets evaluated against a stable architecture. What fits gets integrated. What does not gets set aside. The system learns and the person stays the author.
The System
AOS is my operating system. Built from 45 years of interface practice across physical, digital, cultural, and organizational domains. Not a productivity method. Not a framework for sale. A rigorous working architecture for how I recognize, how I design, and what I construct.
It runs everything — the studio practice, the publications, the platforms, the research. It determines what I take on and what I decline. It is the reason the work across very different domains holds together as one body rather than fragmenting into a portfolio of unrelated projects.
AOS is not static. It is updated continuously as the environment changes. The acceleration happening now is not a threat to it — it is exactly the condition it was built for. A personal operating system that cannot engage with agentic tools and AI-augmented practice is already obsolete. One that can is a structural advantage that compounds over time.
A Design Problem
The question the current moment poses to every maker, designer, researcher, and practitioner is not whether to engage with what is coming. That is already decided. The question is whether you engage on your own terms — with a system that knows what it is for — or on the terms of the systems built around you.
That is a design problem. And like every design problem, it has better and worse answers.









