Authority boundary
Clarify who can approve high-impact UX patterns, who can block dark patterns, and how exceptions are escalated.
What is Design Authority?
Design authority names the accountable owner who can approve, change, or halt a system’s design.
Glossary anchor
Design Authority
Connect the explainer to the canonical definition for citations and shared language.
Design authority identifies the accountable owner empowered to approve, change, or halt a system’s design. It prevents diffusion of responsibility by naming a steward with decision rights.
Clear design authority ties governance decisions to a person or office that can sign off on risks and remediation.
A platform names a Design Authority for its recommender system and requires that role to sign off on any changes to ranking logic or safety thresholds.
Implementation
Distinct implementation signals
Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.
Common failure pattern
When design authority is symbolic, risky experiments bypass review under growth exceptions; require prelaunch sign-off trails.
Evidence to ship
Store design decision records, rejected-pattern logs, and release gates showing authority exercised before deployment.
Standard
Ethotechnics for Agents
Use the standard to align design authority with oversight, receipt requirements, and human recourse obligations.
Binding
Binding vectors
Translate design authority into procurement and release gate clauses.
Evidence pack
STD-02 evidence pack
Capture ownership proofs and decision logs that show authority in action.
How is design authority different from product ownership?
Product ownership focuses on delivery goals, while design authority carries governance power to approve, halt, or remediate based on ethical risk.
What happens when authority changes?
Update the authority record, issue a receipt for the handoff, and ensure prior decisions remain traceable to the former owner.