Authority design specifies who may make a decision, what the permission covers, and when someone else must take over. Technical ability alone does not grant authority.
Illustrative example
A booking agent can read a calendar and reserve a meeting room. It can also see an external guest’s details, but inviting that guest requires the organiser’s approval. The rules distinguish access to information from permission to use it.
As software moves from answering questions to taking action, design can no longer focus solely on interfaces. The central challenge becomes agency itself: who may act, under whose authority, within which constraints, and with what accountability.
An operating system to scale design quality in digital products and services — under real constraints, the minimum viable management system to keep decision integrity, delivery speed, and craft consistent across teams, markets, and high‑stakes domains.