About HAS-D

The framework.

HAS-D, short for Human-Agent-System Design, is a sub-discipline of HCI for the agentic era. It's built for the kind of products that have emerged in the last five years, where humans, agents, and systems are all doing work at the same time, on the same thing, and the design problem isn't just the interface anymore.

The move HAS-D makes is to treat the Human, the Agent, and the System as three co-equal design objects. The Human gets designed. That's HCI's long-running work. The Agent gets designed. That's where most of the current conversation is. The System, the persistent structured layer the other two act on, also gets designed, with the same intention the interface gets designed. Not inherited as substrate. Not left to whatever the engineering team happened to ship.

The shape.

v1.0 of the framework catalogs thirteen concepts, organized into two groups. Seven premises: the load-bearing claims the framework rests on. Six phenomena: the recurring patterns that show up once you start treating the triad as three design objects. The premises explain why the frame holds. The phenomena are what you run into once you're inside it.

Status.

v1.0 is written and internally consistent. That doesn't mean finished. It means ready to meet readers, take pressure, and evolve in public. This blog is the venue. Concepts get unpacked, definitions get tested, prior art gets credited, and the framework gets sharpened against reality, post by post.

Prior art.

HAS-D stands on shoulders, and names them. Actor-network theory on the symmetry between human and non-human actors. Emergence theory on why systems are irreducible to their parts. The neurodiversity movement on the difference between difference and deficit. Kimmerer's reciprocity on what a healthy relationship with a non-human agent actually looks like. The framework document credits each at the door. The blog will too.

Who's building it.

Chad Bercea is a product designer building HAS-D, a sub-discipline of HCI for the age of agents. This site is where the framework gets written, stress-tested, and put to work in public.