The Phone Calls Were Always This Model
The responsibilities never changed. The medium did.
Understanding why a responsibility-based architecture matters now requires understanding how business integration has evolved across three generations. Not three generations of technology — three generations of how organisations actually fulfill their responsibilities and connect them to each other.
Generation 1 — Analog Internal
Organisations fulfilled responsibilities through people and manual processes. An order entry clerk entered the order. A loan officer submitted the application. A booking agent made the reservation.
Integration between responsibilities happened over analog channels — interoffice mail, phone calls, physical forms moving between departments, fax transmissions to external partners.
The integration was real and necessary. It just ran on analog infrastructure. The responsibility boundaries were clear. The contracts were implicit — everyone knew what information to pass and what to expect back. The over-the-wall communication was the ecosystem.
The operator's role was execution. They were the human face of the business process.
Generation 2 — Analog to Digital Surface
Consumers began interacting directly with systems. The internet made this possible. Competitive pressure made it necessary.
The system now faced outward — consumers entered their own orders, submitted their own applications, made their own reservations. But the integration between responsibilities remained largely analog. A website collected the application. A batch job moved it somewhere. An email triggered a downstream process. A fax still went to the credit bureau.
The consumer-facing surface went digital. The integration behind it stayed over the wall.
The operator's role shifted to exception management. Routine work moved to the consumer. Humans handled what the system could not.
Generation 3 — Fully Digital Ecosystem
The analog channels are replaced by digital contracts and events. Anyone who honours the contract can participate — a consumer through a mobile app, a partner through an API, an automated system reacting to an event, another organisation integrating your capability into their own process.
The over-the-wall communication becomes published events and explicit contracts. The phone calls become subscriptions. The interoffice mail becomes intent. The fax becomes an API. The responsibilities that were always there now interact through a digital ecosystem that is faster, more reliable, and formally governed.
The operator's role becomes stewardship — setting the rules, managing exceptions, making judgment calls the automation cannot resolve. The routine flows digitally because the contracts govern it.
What This Means
This is not a technology story. It is a business story about how work has always flowed through organisations — and how the medium through which it flows has changed.
The booking agent who called the hotel, confirmed the room, and noted the arrival time was fulfilling a responsibility through an analog contract. The mobile app that does the same thing today is fulfilling the same responsibility through a digital one. The responsibility did not change. The vocabulary did not change. The rules governing the outcome did not change.
What changed is that the contract is now explicit, machine-readable, and formally governed — which means it can be honoured by any participant who agrees to it. A partner. A third-party vendor. An automated process. Another organisation on the other side of the world.
The architecture was always relative to the responsibilities. It just could not be expressed precisely until now.
That is why this matters. Not because distributed systems are new. Not because event-driven architecture is new. Because we now have the tools to express the operating model that was always there — and when it is expressed precisely, it can be evolved without breaking, extended without coupling, and understood by business and engineering equally.
The phone calls and interoffice mail were always this model. They just ran on analog infrastructure. Generation 3 replaces the medium while honouring the same responsibilities that were always there.