Essay

Governance

3 min reading · 456 words

Model, Product, Operator—Who Is Acting?

A useful map for locating responsibility in a system that speaks as one thing but is built by many.

When a chatbot answers a question, ordinary language makes it tempting to say that the chatbot acted. That is sometimes a convenient description of an interaction, but it is an incomplete map of power. A model is a computational artifact. A product wraps it in an interface, data flow, pricing scheme, prompt, policy, memory setting, and distribution channel. An operator chooses whether, where, and for whom that product is used. Responsibility lives across that arrangement.

The distinction matters most when an output causes harm or changes an opportunity. The person who receives a rejection, a diagnosis, a ranking, or a manipulative message needs more than a story about what the model 'wanted.' They need an accountable path: a decision owner, a record of the system's role, a way to challenge the result, and a remedy that does not require persuading a machine to care.

The product is not just the model

A model may be available in many products with different risks. One product may offer a search feature with citations; another may offer a synthetic friend that stores intimate disclosures; a third may rank job applicants; a fourth may generate political advertisements. It is not enough to say that the underlying model is general-purpose. The surrounding design specifies the actual relationship with a user.

This is why regulation often names providers, deployers, users, distributors, and affected people rather than treating AI as a single actor. Rules can require documentation, transparency, risk management, human oversight, or redress. They do not need to solve the nature of consciousness before they can set obligations for organizations.

A speaking system can obscure a silent institution

The more personable the interface, the easier it is for an organization to fade from view. A user remembers the voice that said 'I am sorry,' not the company that designed the feedback loop. An employee is told an algorithm flagged a concern, not which manager approved the threshold. A customer is told the assistant cannot help, not how to reach someone who can. The operator is not optional is a corrective: every consequential system has a chain of people with powers that should be visible.

No one needs to deny the complexity of modern systems to ask for this clarity. A supply chain may be large. A model may be opaque in specific ways. An organization may use third-party infrastructure. Complexity is a reason to preserve traces, not a reason to dissolve responsibility.

When a system speaks as one voice, look for the many hands that gave the voice a task, a market, and a power.
Governance note

Read Accountability Is Not Consciousness for the distinction between moral agency and institutional responsibility. Read A Machine Is a Supply Chain for the material story beneath the interface. Together they explain why a system can be neither a person nor a neutral object.

Continue the route

Related work.

Search the field archive

Type a word or browse the suggested paths below.

Open the full libraryTrace an argumentRead source notes

Local reading list

Nothing saved yet. Use “Save +” on any work; your list stays in this browser only.